Moving a start date without using a hard contraint

[KD]

In project, if I have two tasks and the first one is 100% complete, and the
second one needs to be moved out from the start date set up by the link, how
can I move it without deleting the link or entering a hard constraint?

Logic tells me I should enter in a task which shows the reason for the
delay, however this does not always seem approprioate in every schedule for
every circumstance.

Am I missing the logic here?

Thank you

 

[Jim Aksel]

I see these possible solutions.
1. Start the subsequent task, you have no reason not to (Probably not what
you wanted to hear).
2. If the resource assigned to the subsequent task is overloaded, use
Priority and Resource Leveling to move the task out.
3. Use a start date constaint and explain the reason in the Notes. This is
not a good practice as you said.
4. Add a ficticious task that explains it away. For example "Procurement
Lead Time" or "Wait for paint to dry" (You already said this one too)
5. Add a lag as part of the predecessor between the two tasks.
6. Establish another predecessor link from a different task that is actually
driving your start date.

The easiest way to produce lag is Window/Split. In the bottom pane, key the
lag time (as days) in the lag column. The problem I have with Lag is
remembering why
it is there. It is easier to create a 20 day task "Procurment Lead Time"
than to have a FS+20days as a predecessor. Tomorrow someone will ask "What
is the lag for?" and I can't remember....
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com

 

[John]

In project, if I have two tasks and the first one is 100% complete, and the
second one needs to be moved out from the start date set up by the link, how
can I move it without deleting the link or entering a hard constraint?

Logic tells me I should enter in a task which shows the reason for the
delay, however this does not always seem approprioate in every schedule for
every circumstance.

Am I missing the logic here?

Thank you

KD,
No, you're not missing any logic. The only reason links are added
between tasks is to emulate a true dependency. For example, task B
cannot start until task A finishes (e.g. the prototype can't be built
until the design is complete, or the taping and finishing can't be
applied until the sheetrock is up). However for various reasons although
task B may be dependent on task A, task B may not start immediately.
Maybe there is a delay waiting for parts to arrive, or maybe its a
funding availability issue, or any number of other things. If the delay
is known it can be included the link. For example, if task B can't start
until 5 working days after task A completes, then the predecessor for
task B might be: FS+5d. If another specific task is the reason for the
delay (e.g. task A finished but an approval cycle is required before
task B can start), then that delaying task should be included in the
plan as an additional task.

Every plan requires careful thought to develop. Every task must have a
successor, even if its just the final completion milestone. If tasks
should be logically linked then link them, but don't link tasks just for
the sake of having a continuous flow of logic. But remember, plans are
always dynamic. The plan you start with will most certainly need to be
modified as it unfolds in the real world. That includes reviewing all
the schedule logic and making adjustments as necessary.

Hope this helps.

John
Project MVP

 

[vanita]

Hi

Let us assume the situation is that Task B starts after Task A. When you are
updating the schedule, Task A is 100% complete and upto your Status date Task
B has not started due to some issue and you want it to start after Status
date.

Go to Tools > Tracking > Update project and check the option 'Reschedule
uncompleted work to start after' and select your Status date. Now Task B and
other incomplete works would be started after that date. You may give a note
with Task B what caused this delay.

OR else add a delay task between Task A and Task B for the appropriate
duration.

I hope it helps.
Vanita

 

[Jim Aksel]

Just an additional note, rescheduling the work creates a "Start No Earlier
Than" constraint type.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com