Task Completes way after

[jp]

Hi,

I have a task ( say task1) out of four tasks that need to be completed one
after the other (F-S). However, task1 doesn't complete until a bunch of days
after. This task completion doesn't affect the project in a technical way
because it is simply a meeting ie. kick-off. One question though. How does
it affect the project from any perspective (reporting, etc...)

 

[John]

Hi,

I have a task ( say task1) out of four tasks that need to be completed one
after the other (F-S). However, task1 doesn't complete until a bunch of days
after. This task completion doesn't affect the project in a technical way
because it is simply a meeting ie. kick-off. One question though. How does
it affect the project from any perspective (reporting, etc...)

jp,
You say task1 doesn't affect the project yet it sounds like tasks 2 thru
4 can't get started until the kick-off meeting completes. It sounds to
me like task1 DOES affect the project, however it might not be on a
critical path so it's hard to tell.

The answer to your question is, "I have no idea", since there isn't
enough information. You are the only one that can really determine how a
delay in one or more tasks will affect the overall project.

John
Project MVP

 

[Jan De Messemaeker]

Hi

I'm afraid I don't follow you.
A)
four tasks that need to be completed one after the other (F-S).
Or B)
This task completion doesn't affect the project in a technical way

Can task 2 start before task 1 ends or not?

Greetings,
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf

 

[jp]

Hi John,

Thank you for your answer. Here is the clarification. Even if task1
completes way after its original date, other wask that are supposed to be
linked (f-s) complete. The tasks are getting completed even if the kick-off
meeting isn't complete. In other words, the work (technical stuff) continues.

-jp

 

[Jan De Messemaeker]

So the truth is, there is no link between tasks 1 and 2.
Task 1 doesn't seem to affect anything.
Better eliminate the link then!

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf

 

[jp]

Yes, the other tasks have been in progress while task1 was not completed.
The thought was that every task was going to be completed one after the other.
Now, after much 7 weeks we finally finished that task (task1). So from
"best practice" in PM how should this task have been disigned? In hindsight,
I would have probably not linked this task to anything. However, after the
fact, I now have to learn and apply "best practice" and ask how this may
affect the reports or anything else in the project or in the PM itself?

-jp

 

[Jan De Messemaeker]

Hi,

Once you have entered the actual values links etc. no longer influence
anything, so for reporting this is not of grreat importance. Actual values
take over the plan!

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf

 

[John]

Hi John,

Thank you for your answer. Here is the clarification. Even if task1
completes way after its original date, other wask that are supposed to be
linked (f-s) complete. The tasks are getting completed even if the kick-off
meeting isn't complete. In other words, the work (technical stuff)
continues.

-jp

jp,
I think Jan pretty much covered it. It's interesting that you had a kick
off meeting that didn't "kick off" anything - the effort was already in
progress. In my view if a task doesn't have a successor then it is a
meaningless task and doesn't belong in the plan.

John
Project MVP

 

[Dave]

jp,
I think Jan pretty much covered it. It's interesting that you had a kick
off meeting that didn't "kick off" anything - the effort was already in
progress. In my view if a task doesn't have a successor then it is a
meaningless task and doesn't belong in the plan.

I can't see how that is generally true. It would be enough that it was
a deliverable for it to be in the Plan. For example, I may have a
complex software development which results in a complex network diagram.
The customer might also want a printer so they can print out their log
files. The printer is quite likely not to have a predecessor or
successor as it can be procured at any point during the project.

 

[Jan De Messemaeker]

Agree. Still, you wouldn't link the printer istallation to the developemnt
effort if there is no true dependency would you?
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf

 

[Dave]

Agree. Still, you wouldn't link the printer istallation to the developemnt
effort if there is no true dependency would you?

No, I wouldn't link it to the development but it would be an item that
had neither a real successor or predecessor yet still needed to be
shipped. I dare say that more interesting examples can be conjured up.

 

[John]

jp,
I think Jan pretty much covered it. It's interesting that you had a kick
off meeting that didn't "kick off" anything - the effort was already in
progress. In my view if a task doesn't have a successor then it is a
meaningless task and doesn't belong in the plan.

I can't see how that is generally true. It would be enough that it was
a deliverable for it to be in the Plan. For example, I may have a
complex software development which results in a complex network diagram.
The customer might also want a printer so they can print out their log
files. The printer is quite likely not to have a predecessor or
successor as it can be procured at any point during the project.[/QUOTE]

Dave,
ALL tasks must have a successor, otherwise they don't belong in the
plan. Everything in the plan must contribute to the project finish
milestone, otherwise, why is the task being done? Note, a deliverable is
not a task, it is a milestone.

A deliverable may be the final milestone or it may be an intermediate
milestone. A deliverable is an end item and it most likely will not
have a successor, (unless it is intermediate and drives more tasks), but
it must have a predecessor.

WIth regard to your example of procuring a printer. Is the printer
required in order to complete the project? If so, then the successor may
be the final milestone. If not, then the printer procurement does not
belong in the plan - it is an independent item.

John
Project MVP

 

[Dave]

Hi John,

Thank you for your answer. Here is the clarification. Even if task1
completes way after its original date, other wask that are supposed to be
linked (f-s) complete. The tasks are getting completed even if the
kick-off
meeting isn't complete. In other words, the work (technical stuff)
continues.

-jp
jp,
I think Jan pretty much covered it. It's interesting that you had a kick
off meeting that didn't "kick off" anything - the effort was already in
progress. In my view if a task doesn't have a successor then it is a
meaningless task and doesn't belong in the plan.

I can't see how that is generally true. It would be enough that it was
a deliverable for it to be in the Plan. For example, I may have a
complex software development which results in a complex network diagram.
The customer might also want a printer so they can print out their log
files. The printer is quite likely not to have a predecessor or
successor as it can be procured at any point during the project.

Dave,
ALL tasks must have a successor, otherwise they don't belong in the
plan. Everything in the plan must contribute to the project finish
milestone, otherwise, why is the task being done? Note, a deliverable is
not a task, it is a milestone.

A deliverable may be the final milestone or it may be an intermediate
milestone. A deliverable is an end item and it most likely will not
have a successor, (unless it is intermediate and drives more tasks), but
it must have a predecessor.

WIth regard to your example of procuring a printer. Is the printer
required in order to complete the project? If so, then the successor may
be the final milestone. If not, then the printer procurement does not
belong in the plan - it is an independent item.

John
Project MVP[/QUOTE]

I think that we're down to the definitions of terminology. It seemed to
me that in the context of the original question, you were saying that
the 'kick-off meeting' shouldn't have been in the plan because other
work proceeded before its completion (I agree it seems strange that the
work proceeded before its completion).

In my terminology, a deliverable is most definitely a task (because that
is the thing that has to be produced) and the delivery is the milestone
but that is semantics.

Ultimately we are saying the same thing.

 

[John]

Dave,
ALL tasks must have a successor, otherwise they don't belong in the
plan. Everything in the plan must contribute to the project finish
milestone, otherwise, why is the task being done? Note, a deliverable is
not a task, it is a milestone.

A deliverable may be the final milestone or it may be an intermediate
milestone. A deliverable is an end item and it most likely will not
have a successor, (unless it is intermediate and drives more tasks), but
it must have a predecessor.

WIth regard to your example of procuring a printer. Is the printer
required in order to complete the project? If so, then the successor may
be the final milestone. If not, then the printer procurement does not
belong in the plan - it is an independent item.

John
Project MVP

I think that we're down to the definitions of terminology. It seemed to
me that in the context of the original question, you were saying that
the 'kick-off meeting' shouldn't have been in the plan because other
work proceeded before its completion (I agree it seems strange that the
work proceeded before its completion).

In my terminology, a deliverable is most definitely a task (because that
is the thing that has to be produced) and the delivery is the milestone
but that is semantics.

Ultimately we are saying the same thing.[/QUOTE]

Dave,
I think we agree. Yes, it is the actual delivery that is the milestone.
The activities, (i.e. creating the deliverable), are very definitely
tasks.

John
Project MVP