How to examine critical path selectively?

[michael.franke]

Hi

I have a large, complex project in which I'd like to do some critical
path analysis. Unfortunately, the project contains a couple of tasks
that are "blanket" tasks to cover management resources (like me) --
they span the entire project, from start to finish. Consequently,
these tasks end up being the critical path, by definition.

I can view multiple critical paths, but for this project that ends up
being overwhelming.

I'd like to selectively "hide" certain tasks from the critical path
analysis, so that I can do some "what if" scenarios.

I've done this by cutting those tasks out of the project temporarily,
and pasting them into a scratch project. But this makes me nervous.

Any way to do what I want to do?

Mike

 

[Darrell]

I would just enter some slack for those tasks versus removing them. If they
end on the project finish date change the finish date to end one or two days
earlier than the project. Once you finish your analysis you can set the
finish dates back, if you want too.

Darrell

 

[Jim Aksel]

Long tasks do tend to obscure the critical path. Even breaking them to
smaller tasks and linking them does not help much.

We maintain a separate Level of Effort schedule for folks like program
managers, etc. who are loaded from Day 1 until death do we part. The discrete
(measureable) schedule then shows a nice critical path. You can always
create a total rollup using a master schedule with two subprojects: LOE and
Discrete.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

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

 

[michael.franke]

Jim,

Thanks so much for your response. I'd already done what you said, but
it's great to get confirmation that I'm doing things "right."

Mike