Critical Chain Project Management

Also known as: CCPM

framework · project management · organizing-schema

Goldratt's application of Theory of Constraints to project management, replacing task-level safety with project-level buffers.

Critical Chain Project Management (CCPM) is Eliyahu Goldratt's application of the Theory of Constraints to project scheduling, articulated principally in Goldratt's 1997 business novel Critical Chain. CCPM's central insight is that task-level safety estimates (added to individual task durations to absorb variability) are systematically wasted through Parkinson's Law, the Student Syndrome (delaying start because there's time), and resource multitasking across projects, while project-level safety would allow shared buffering across the chain of tasks. CCPM accordingly removes task-level safety, concentrates protection in project, feeding, and resource buffers, and schedules to the critical chain (the longest dependency-and-resource-constrained sequence) rather than the resource-unconstrained critical path. Implementation requires substantial cultural change: removing date-based task commitments, monitoring buffer consumption rather than task milestones, and reducing multitasking across projects.

Originators

Eliyahu M. Goldratt (1997 Critical Chain); intellectual antecedents in TOC, Drum-Buffer-Rope production scheduling, and Goldratt's earlier work on bottleneck-based operations management high

Year / Decade

1997 (Critical Chain published); subsequent practitioner development through Goldratt Institute and others high

Primary sources

Goldratt, E.M. (1997). Critical Chain, Leach, L.P. (2014). Critical Chain Project Management, Third Edition, Steyn, H. (2002). 'Project management applications of the theory of constraints beyond critical chain scheduling', International Journal of Project Management high

Core components

Removal of task-level safety from individual duration estimates
Critical chain identification (longest dependency-and-resource-constrained sequence, distinct from resource-unconstrained critical path)
Project buffer at end of project
Feeding buffers at points where non-critical-chain tasks merge into critical chain
Resource buffers (alerts for resources approaching critical chain tasks)
Buffer management as primary monitoring mechanism (consumption versus completion percentage)
Multi-project CCPM (drum resource pacing across project portfolio)
Integration with Theory of Constraints Five Focusing Steps

Primary use case

Project scheduling and execution monitoring in TOC-implementing organizations; alternative to PMBOK / PRINCE2 critical-path-method scheduling for complex projects; particularly applied in product development, capital projects, and IT delivery; input to PMO scheduling-and-control frameworks; pedagogical reference in TOC, project-management, and operations-research curricula.

Common criticisms

CCPM's empirical evidence is contested — Trietsch, Hopp, Spearman, and Steyn have published critiques arguing CCPM's claimed performance improvements are not supported by rigorous studies and that the buffer-sizing heuristics (50% of removed safety, the 'cut-and-paste' method) lack theoretical foundation
the assumption that task estimates contain substantial padding that can be safely removed is empirically variable across organizations
multi-project CCPM's drum-resource-pacing assumption of a single binding constraint is often violated
behavioral implementation is difficult — removing task-level commitments is culturally disruptive in organizations where dates are governance and contractual artifacts
integration with PMBOK and PRINCE2 produces awkward hybrid implementations that lose CCPM's coherence
software-tooling support is limited to specialty CCPM products rather than mainstream PM tools
the Goldratt-Institute case-study evidence base has known selection bias
practical adoption has been concentrated in specific industries (engineering, construction, defense) rather than general
the framework's behavioral premises (Student Syndrome, Parkinson's Law) have empirical support but their relative magnitudes vary by context.

Lineage

Child of: Theory of Constraints
Siblings: PMBOK Guide, Earned Value Management
Derived from: Theory of Constraints