Critical Chain Project Management

Critical Chain Project Management (CCPM) is a method of planning and managing projects that puts more emphasis on the resources required to execute project tasks developed by Eliyahu M. Goldratt. This is in contrast to the more traditional Critical Path and PERT methods, which emphasize task order and rigid scheduling. A Critical Chain project network will tend to keep the resources levelly loaded, but will require them to be flexible in their start times and to quickly switch between tasks and task chains to keep the whole project on schedule.

Origins

Developed by Eliyahu M. Goldratt, Critical Chain Project Management is based on methods and algorithms derived from his Theory of Constraints. The idea of CCPM was introduced in 1997 in his book, "Critical Chain". Application of CCPM has been credited with achieving projects 10% to 50% faster and/or cheaper than the traditional methods (ie. CPM, PERT, Gantt, etc.) developed from 1910 to 1950's.

From numerous studies by Standish Group and others ^{[http://www.pqa.net/ProdServices/ccpm/W05002001.html ref]} as of 1998 for traditional project management methods, only 44% of projects typically finish on time, projects usually complete at 222% of the duration originally planned, 189% of the original budgeted cost, 70% of projects fall short of their planned scope (technical content delivered), and 30% are cancelled before completion.

These traditional statistics are mostly avoided through CCPM. Typically, CCPM case studies report 95% on-time and on-budget completion when CCPM is applied correctly. Mabin and Balderstone Citation| first=Vicky | last=Mabin| coauthors=Steven Balderstone| contribution=A Review of Goldratt's Theory of Constraints - Lessons from the International Literature| title=Operational Research Society of New Zealand 33rd Annual Conference| editor-first=| editor-last=| coeditors=| publisher=| place=Auckland| pages=205-214| date=| year=1998| contribution-url=http://www.orsnz.org.nz/conf33/abstracts.html| format=| accessdate=2007-11-06 ] , performed a meta-analysis of seventy-eight published case studies taken from the manufacturing and operational literature. They found that implementing Critical Chain resulted in mean reduction in lead-times of 69%, mean reduction of cycle-times of 66%, mean improvement in due date performance of 60%, mean reduction in inventory levels of 50% and mean increases in revenue / throughput of 68%. While these statistics may not entirely apply to the project management venue, they could be an indication to the magnitude of improvements possible when applying the same techniques to the project world.

Details

With traditional project management methods, 30% of the lost time and resources are typically consumed by wasteful techniques such as bad multi-tasking, Student syndrome, In-box delays, and lack of prioritization.Fact|date=June 2008

In project management, the critical chain is the sequence of both precedence- and resource-dependent terminal elements that prevents a project from being completed in a shorter time, given finite resources. If resources are always available in unlimited quantities, then a project's critical chain is identical to its critical path.

Critical chain is used as an alternative to critical path analysis. The main features that distinguish the critical chain from the critical path are:
# "The use of (often implicit) resource dependencies". Implicit means that they are not included in the project network but have to be identified by looking at the resource requirements.
# "Lack of search for an optimum solution". This means that a "good enough" solution is enough because:
## As far as is known, there is no analytical method of finding an absolute optimum ("i.e." having the overall shortest critical chain).
## The inherent uncertainty in estimates is much greater than the difference between the optimum and near-optimum ("good enough" solutions).
# "The identification and insertion of buffers":
#* project buffer
#* feeding buffers
#* resource buffers.
# Monitoring project progress and health by monitoring the consumption rate of the buffers rather than individual task performance to schedule.

CCPM aggregates the large amounts of safety time added to many subprojects in project buffers to protect due-date performance, and to avoid wasting this safety time through bad multitasking, student syndrome, Parkinson's Law and poorly synchronised integration.

Critical chain project management uses buffer management instead of earned value management to assess the performance of a project. Some project managers feel that the earned value management technique is misleading, because it does not distinguish progress on the project constraint ("i.e." on the critical chain) from progress on non-constraints ("i.e." on other paths). Event chain methodology can be used to determine a size of project, feeding, and resource buffers.

Methodology

Planning

A project plan is created in much the same fashion as with critical path. The plan is worked backward from a completion date with each task starting as late as possible. Two durations are entered for each task: a "best guess," or 50% probability duration, and a "safe" duration, which should have higher probability of completion (perhaps 90% or 95%, depending on the amount of risk that the organization can accept).

Resources are then assigned to each task, and the plan is resource leveled using the 50% estimates. The longest sequence of resource-leveled tasks that lead from beginning to end of the project is then identified as the critical chain. The justification for using the 50% estimates is that half of the tasks will finish early and half will finish late, so that the variance over the course of the project should be zero.

Recognizing that tasks are more likely to take more rather than less time due to Parkinson's law, Student syndrome, or other reasons, "buffers" are used to establish dates for deliverables and for monitoring project schedule and financial performance. The "extra" duration of each task on the critical chain—the difference between the "safe" durations and the 50% durations—is gathered together in a buffer at the end of the project. In the same way, buffers are gathered at the end of each sequence of tasks that feed into the critical chain.

Finally, a baseline is established, which enables financial monitoring of the project.

Execution

When the plan is complete and the project ready to kick off, the project network is fixed and the buffers size is "locked" (i.e. their planned duration may not be altered during the project), because they are used to monitor project schedule and financial performance.

With no slack in the duration of individual tasks, the resources on the critical chain are exploited by ensuring that they work on the critical chain task and nothing else; bad multitasking is eliminated. An analogy is drawn in the literature with a relay race. The critical chain is the race, and the resources on the critical chain are the runners. When they are running their "leg" of the project, they should be focused on completing the assigned task as quickly as possible, with no distractions or multitasking. In some case studies, actual batons are reportedly hung by the desks of people when they are working on critical chain tasks so that others know not to interrupt. The goal, here, is to overcome the tendency to delay work or to do extra work when there seems to be time.

Because task durations have been planned at the 50% probability duration, there is pressure on the resources to complete critical chain tasks as quickly as possible, overcoming student's syndrome and Parkinson's Law.

Monitoring

Monitoring is, in some ways, the greatest advantage of the Critical Chain method. Because individual tasks will vary in duration from the 50% estimate, there is no point in trying to force every task to complete "on time;" estimates can never be perfect. Instead, we monitor the buffers that were created during the planning stage. A fever chart or similar graph can be easily created and posted to show the consumption of buffer as a function of project completion. If the rate of buffer consumption is low, the project is on target. If the rate of consumption is such that there is likely to be little or no buffer at the end of the project, then corrective actions or recovery plans must be developed to recover the loss. When the buffer consumption rate exceeds some critical value (roughly: the rate where all of the buffer may be expected to be consumed "before" the end of the project, resulting in late completion), then those alternative plans need to be implemented.

See also

* List of project management software
* Theory of Constraints
* Event chain methodology

Further reading

* "Critical Chain", ISBN 0-88427-153-6
* "Project Management In the Fast Lane", ISBN 1-57444-195-7
* "Critical Chain Project Management", ISBN 1-58053-074-5
* "Projects in Less Time: A Synopsis of Critical Chain", ISBN 1419620533
* " [http://www.allbusiness.com/management/951030-1.html| A critical look at critical chain project management] "

References

External links