Jul 06 2022 07:12 PM
Jul 06 2022 07:12 PM
I have a detailed program schedule with following hierarchy
Sub Work packages,
There are about 15 work package and the structure repeats for every work package.
One of the last work packages has a Go-Live milestone.
WBS Tasks are linked across different work packages to create a path from start to Go-Live
Now if I plot the critical path, I get a huge list of small WBS tasks. This is good for actioning, but for reporting to executives, this is of little value.
Executives want to see critical path at Work Package level, Sub-Work Package level and milestones level.
Is there a way to select which tasks would be included / excluded into critical path calculation ?
It's important to note that predecessors are identified at WBS task levels, not at sub-work package or work package level.
If I exclude, WBS list from critical path calculation (I am assuming, I can), how does the linkages precipitate up to summary tasks ?
Jul 06 2022 08:29 PM - edited Jul 06 2022 08:31 PM
To your explicit questions:
- Is there a way to select which tasks would be included / excluded into critical path calculation? Yes. (Setting aside the key difference between the collection of Critical-flagged tasks and the logic-defined "Critical path,") MS Project allows you to define the "Critical" flag according to a Total Slack threshold. Unfortunately you can only move that threshold upwards from zero. Any zero or negative-TS tasks will always be flagged as critical. This is likely not useful.
- ...how does the linkages precipitate up to summary tasks ?
They don't (and should not). Logical restraints exist between specific low-level tasks (your WBS tasks), and these restraints are used to calculate early dates, late dates, and total slack for the tasks. With fully automatic calculations, summary tasks inherit early and late dates from their sub-tasks, and the resulting total slack for these summary tasks is only rarely meaningful. Avoid the temptation to make summary CP reports from summary tasks. You typically end up with a bunch of parallel summary-task bars that are meaningless.
If your executives demand, then it may be most useful to make a summary-level critical path report using a specially filtered and formatted view that includes key WBS tasks and adds specially constructed "hammock" tasks to represent extended chains of critical WBS tasks.
Good luck, tom