The schedule has exactly one critical path. If you turn on "calculate
multiple critical paths" it will only give you additional paths of the same
duration through the network.
Always remember, there is only one critical path and it is a property of the
entire schedule. There is no such thing as "The software critical path" and
"the hardware critical path" within the same schedule. the critical path may
involve tasks from both these chains, or only one.
What you can do is show the critical path and then filter the schedule to
show only certain other properties. Using a spare flag field, say Flag1, set
this to "Yes" for any and all possible tasks that you may want to show in
your final result. For example, you could flag all tasks that are software
development or just the tasks related to a specific piece of hardware
development.
Now apply the "Critical" filter from the filter drop down. This shows you
the critical path. Then, using the autofilter, apply the next filter as
well: Flag1="Yes". It is possible the screen will be blank -- that would
indicate there are no "software development" tasks on the critical path.
Otherwise, you will see those critical tasks that are also SW Development.
Additional filters may also be applied such as the date range filter.
Any other scenario is not a critical path. This is how development efforts
get off track. In many instances the "software" and "hardware" are contained
in different schedules. True, each *stand alone* schedule would have its own
critical path and people tend to work those paths. The problem is, this is
not generally the program critical path and it causes people to place
emphasis on the incorrect task sequence. If the separate schedule contains
links to other schedules, then the critcal path calculation must include
those external schedules as well (from a master schedule).
--
If this post was helpful, please consider rating it.
Jim Aksel, MVP
Check out my blog for more information:
http://www.msprojectblog.com