Help: Lag time is being added when not called for

[Dab]

Help:

Sorry, I have another dumb question....

When I add a 'finish to start' dependency between two items, project is
adding a days' delay between the two items, even though the dependency has a
0 duration lag. What gives?

Thanks for any help.

 

[JulieS]

Hi Dab,

Is this occurring on all tasks or just one?

Check your calendar (Tools --> Change Working Time) to see if there is
non-working time in the calendar causing the delay of the start of the
successor task.

If you are assigning resources, Check Tools --> Resource Leveing and see if
automatic leveling is on.

Hope this helps. Let us know how you get along.

Julie

 

[Steve House [MVP]]

The FS link says when the earliest the sucessor can start, barring lead
times, but it could start later. One cause is that it has to wait until the
next working time - the predecessor finishes Friday at 5 and the successor
can't start until Monday because that's the next working time according the
the project calendar. Another cause might be that the calendar of the
resource assigned to the sucessor has him unavailable until some period of
time after the predecessor ends. Or it could be that leveling is set to
automatic and the resource on the sucessor is already assigned to another
task at that time slot so the task in question has to move until he's free.
There may be other ways the successor would end up starting later than the
link would otherwise have it but those are some of the most common.
--
Steve House [MVP]
MS Project Trainer/Consultant
Visit http://www.mvps.org/project/faqs.htm for the FAQs

..