Efficiently finding "next" Critical Path

[Dann]

I need to do some "what if" analysis on my plan. The plan is well designed
for CP, that is everything is linked, no summary tasks are linked, etc. Right
now, the project is about two-week's behind where we would like it to be. I
can identify the tasks that are driving the schedule...because they are on
the critical path. (Imagine that!) I also know that one of the larger tasks,
application development, is currently driving change from week-to-week status
updates. But, cutting development by two weeks will not "automatically" bring
the end date in two weeks.

My question this: What is the most efficient way to determine what will be
on the critical path if I remove the current constraint, the development
time. Of course, I could make changes to the plan to see what happens, but
I'm hoping there is a more structured approach. I've also looked at Total
Slack, thinking that will tell me which tasks are likely to end up on the
critical path if the development time shortens. Is that a valid assumption on
my part? Is there some other way to determine what will go critical if
current critical tasks are shortened?

 

[Jan De Messemaeker]

Hi,

IMHO you indeed need total slack.
Auto Filter is an efficient way.
HTH

 

[Dann]

Thanks for your reply...

Just to make certain I understand how to use Total Slack correctly in this
instance, let me try an example. If I have a task that has three days total
slack, this means two things 1) If this task is delayed more than three days
it will begin driving the schedule. 2) Assuming no other complications, If I
shorten the duration of the develoment actitivities by, say, five days, I
will only see (about) a two day improvement in the end date because it is now
driven by the task that had three days total slack, but now has none.
--
Regards,
Dann

Hi,

IMHO you indeed need total slack.
Auto Filter is an efficient way.
HTH

 

[JackD]

That is correct. Just watch out for any constraints in the schedule.

--
-Jack ... For Microsoft Project information and macro examples visit
http://masamiki.com/project
or http://zo-d.com/blog/index.html
..

Thanks for your reply...

Just to make certain I understand how to use Total Slack correctly in this
instance, let me try an example. If I have a task that has three days total
slack, this means two things 1) If this task is delayed more than three days
it will begin driving the schedule. 2) Assuming no other complications, If I
shorten the duration of the develoment actitivities by, say, five days, I
will only see (about) a two day improvement in the end date because it is now
driven by the task that had three days total slack, but now has none.

 

[Jan De Messemaeker]

HI,

I am under the impression you will win 3 days not 2.
HTH

--
Jan De Messemaeker, Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/
For FAQs: http://www.mvps.org/project/faqs.htm

Thanks for your reply...

Just to make certain I understand how to use Total Slack correctly in this
instance, let me try an example. If I have a task that has three days total
slack, this means two things 1) If this task is delayed more than three days
it will begin driving the schedule. 2) Assuming no other complications, If I
shorten the duration of the develoment actitivities by, say, five days, I
will only see (about) a two day improvement in the end date because it is now
driven by the task that had three days total slack, but now has none.