Critical Path Analysis

[NH Ralph]

We work with large, complex networks. Does anyone know of a tool or
technique which will allow you to efficiently analyze and crash the critical
path? i.e. If we wish to reduce our schedule duration, we can use total
slack, but it does not necessarily tell you the impact reducing an activity
duration may have on the total schedule. So if I have a 25 day task
currently on the critical path, reducing the duration to 10 days may only
yield a total schedule duration reduction of 5 days. But a similar reduction
on a 15 day task on the critical path may yield a greater total schedule
savings. Any suggestions to efficiently capture the high impact activities?

 

[Jack Dahlgren MVP]

One simple way is to go to the project menu, select group by ... create a
new group and have it group on Total slack.
This will show your critical path, then your near critical path etc.

With a bit of code you could figure out which tasks have the greatest
potential -

-Jack

 

[Jim Aksel]

After giving it a little thought, there is an add-on by www.Deltek.com called
Risk+
Although the program does MonteCarlo simulation, there are options for
sensitivity analysis.

Performing the sensitivity analysis will give you a list of critical path
tasks most frequently on the critical path. The list is in decreasing order.
So, pick a few of those tasks and crash them as it will give you more bang
for your buck.

The product runs a couple hundred dollars. I have one other solution,
PERTMASTER, but than runs about $10K.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

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

 

[davegb]

We work with large, complex networks. Does anyone know of a tool or
technique which will allow you to efficiently analyze and crash the critical
path? i.e. If we wish to reduce our schedule duration, we can use total
slack, but it does not necessarily tell you the impact reducing an activity
duration may have on the total schedule. So if I have a 25 day task
currently on the critical path, reducing the duration to 10 days may only
yield a total schedule duration reduction of 5 days. But a similar reduction
on a 15 day task on the critical path may yield a greater total schedule
savings. Any suggestions to efficiently capture the high impact activities?

Others here have provided good answers to your query. I would suggest that
you're missing many alternatives in crashing the CP. Shortening durations
of the tasks on that path is the most commonly known/used method, but it is
only the start. The rest is part of the "Lost Art of Scheduling". For
example, lowering quality is another alternative (the default one, though
usually not a desireable one). There are a number of others.

Hope this helps in your world.