Critical chain project management

Critical chain project management (CCPM) is a method of planning and managing projects that puts the main emphasis on the resources required to execute project tasks. It was 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.



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

From numerous studies by Standish Group and others 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.[citation needed]

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,[1] in their meta-analysis of seventy-eight published case studies, 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%.[not in citation given (See discussion.)]


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.[2]

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:

  1. 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.
  2. Lack of search for an optimum solution. This means that a "good enough" solution is enough because:
    1. As far as is known, there is no analytical method of finding an absolute optimum (i.e. having the overall shortest critical chain).
    2. The inherent uncertainty in estimates is much greater than the difference between the optimum and near-optimum ("good enough" solutions).
  3. The identification and insertion of buffers:
    • project buffer
    • feeding buffers
    • resource buffers. (Most of the time it is observed that companies are reluctant to give more resources)
  4. Monitoring project progress and health by monitoring the consumption rate of the buffers rather than individual task performance to schedule.

CCPM planning aggregates the large amounts of safety time added to tasks within a project into the buffers in order to protect due-date performance, and to avoid wasting this safety time through bad multitasking, student syndrome, Parkinson's Law and poorly synchronized 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.


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.

A duration is assigned to each task. Some software implementations add a second duration: one a "best guess," or 50% probability duration, and a second "safe" duration, which should have higher probability of completion (perhaps 90% or 95%, depending on the amount of risk that the organization can accept). Other software implementations go through the duration estimate of every task and remove a fixed percentage to be aggregated into the buffers.

Resources are assigned to each task, and the plan is resource leveled, using the aggressive durations. 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 monitor 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. It is the date at the end of the project buffer that is communicated to external stakeholders as the delivery date.

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

An alternate duration-estimation methodology uses probability-based quantification of duration using Monte Carlo simulation. In 1999, a researcher[who?] applied simulation to assess the impact of risks associated with each component of project work breakdown structure on project duration, cost and performance. Using Monte Carlo simulation, the project manager can apply different probabilities for various risk factors that affect a project component. The probability of occurrence can vary from 0% to 100% chance of occurrence. The impact of risk is entered into the simulation model along with the probability of occurrence. The Monte Carlo simulation runs over 10,000 iterations and provides a density graph illustrating the overall probability of risk impact on project outcome.


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 are encouraged to focus on the task at hand to complete it and hand it off to the next person or group. The object here is to eliminate bad multitasking, and this is done by providing priority information to all resources. An analogy is drawn in the literature with a relay race. Each element on the project is encouraged to move as quickly as they can: 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. The CCPM literature contrasts this with "traditional" project management that monitors task start and completion dates. CCPM encourages people to move as quickly as possible, regardless of dates.

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 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.

Underpinnings of CCPM

History and discussion of the underlying principles behind CCPM.

Critical sequence was originally identified in the 1960s.[citation needed]

See also

Further reading


  1. ^ Mabin, Vicky; Steven Balderstone (1998), "A Review of Goldratt's Theory of Constraints - Lessons from the International Literature", Operational Research Society of New Zealand 33rd Annual Conference, Auckland, pp. 205–214 
  2. ^ Harvey Maylor, Project Management

External links

Wikimedia Foundation. 2010.

Look at other dictionaries:

  • 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… …   Wikipedia

  • Project management — is the discipline of planning, organizing, securing, and managing resources to achieve specific goals. A project is a temporary endeavor with a defined beginning and end (usually time constrained, and often constrained by funding or deliverables) …   Wikipedia

  • Critical Chain (novel) — Critical Chain   …   Wikipedia

  • Critical Chain Management — Critical Chain Projektmanagement (CCPM), teilweise auch Critical Chain Management (CCM), ist eine Projektmanagementmethode. Sie basiert im Wesentlichen darauf, Zeitreserven nicht aktivitätsbezogen einzuplanen, sondern eine einzige explizit… …   Deutsch Wikipedia

  • Critical Chain-Projektmanagement — (CCPM), teilweise auch Critical Chain Management (CCM), ist eine Projektmanagementmethode. Sie basiert im Wesentlichen darauf, Zeitreserven nicht aktivitätsbezogen einzuplanen, sondern eine einzige explizit ausgewiesene Zeitreserve am Ende des… …   Deutsch Wikipedia

  • Critical Chain Projektmanagement — (CCPM), teilweise auch Critical Chain Management (CCM), ist eine Projektmanagementmethode. Sie basiert im Wesentlichen darauf, Zeitreserven nicht aktivitätsbezogen einzuplanen, sondern eine einzige explizit ausgewiesene Zeitreserve am Ende des… …   Deutsch Wikipedia

  • Critical-Chain-Projektmanagement — (CCPM), teilweise auch Critical Chain Multiprojektmanagement oder selten auch Critical Chain Management (CCM), ist eine Projektmanagementmethode basierend auf den Ideen Eliyahu M. Goldratts. CCPM erweitert das klassische Projektmanagement um die… …   Deutsch Wikipedia

  • Timeline of project management — * 2570 BC Great pyramid of Giza completed. Some records remain of how the work was managed: e.g. there were managers of each of the four faces of the pyramid, responsible for their completion (subproject managers). * 208 BC The first major… …   Wikipedia

  • Dependency (project management) — This article is about project management dependency. For other uses, see Dependency (disambiguation). In a project network, a dependency is a link amongst a project s terminal elements. There are four kinds of dependencies with respect to… …   Wikipedia

  • Duration (project management) — Duration of a project s terminal element is the number of calendar periods it takes from the time the execution of element starts to the moment it is completed. Do not confuse duration with work. E.g. it takes three days for a snail mail letter… …   Wikipedia

Share the article and excerpts

Direct link
Do a right-click on the link above
and select “Copy Link”

We are using cookies for the best presentation of our site. Continuing to use this site, you agree with this.