Website Upgrade Incoming - we're working on a new look (and speed!) standby while we deliver the project

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Critical Path Challenge. Criticality of the last activity.

No replies
Alex Lyaschenko
User offline. Last seen 10 weeks 3 days ago. Offline
Joined: 15 Aug 2011
Posts: 59
Groups: None

Based on the Critical Path Method, the last task in a project is always critical.

However, practically we know that the day when the project is going to be completed is never really critical. Instead, we care about Go live, Release, Practical Completion, ect. date.

This specific the CPM method may cause the incorrect calculations of Total Float.

Example:
Assume the deadline for 'Go live' milestone is 20 days after the current forecast. The schedule has one "Post Go Live' activity (without a deadline date) after the Milestone.

Practically TOTAL FLOAT for the 'Go live' milestone is 20 days. However, ALL CPM tools show that Total Float (Total Slack) = ZERO.

Even if the last activity has a deadline that is after the forecast date, the deadline will be ignored and TF will not that activities have Float. 

It is a methodological gap :( 

When the CPM method was invented, no one used it for the whole project. It just wasn't possible due to the limited power of the computers. So, the gap wasn't critical at that time. 

Technically, it is a correct calculation, but practically, the TF Metric could be misleading.

8473
cpm_last_task.png

Patrick Weaver
User offline. Last seen 6 days 13 hours ago. Offline
Joined: 18 Jan 2001
Posts: 384
Groups: None

The critical path is not, and never has been defined by Float.  Float is a computation affected by both calendars and imposed constraints. 

The definition included in ISO 21500 Guide to Project Management, is: Critical Path: sequence of activities that determine the earliest possible completion date for the project or phase.  See: https://www.mosaicprojects.com.au/WhitePapers/WP1043_Critical_Path.pdf

One 'phase' in your scenario is achieving 'go live' (or handover, or practical completion); the end of the final phase is project completion (ie, no more work to do).  The work up to 'go live' will have float (positive or negative) based on the constrained date for this activity, or if the date does not matter the rest of the work to actually finish the project which again may, or may not have a constrained date.   The critical path is not necessarily aligned with important requirements - one of the many anomalies in the CPM method.

For more on this important subject see The Critical Path and Float at: https://mosaicprojects.com.au/PMKI-SCH-012.php#Process5