Critical Chain Project Management
Critical Chain Project Management (CCPM) applies TOC to projects. The critical chain is the longest sequence of dependent tasks and dependent resource assignments — the resource-constrained generalization of the critical path. Safety time is stripped from individual task estimates and aggregated into a shared project buffer at the end of the critical chain, with feeding buffers protecting each junction where non-critical-chain work joins the chain. A resource buffer is a notification mechanism — not a time reserve — that warns the critical-chain resource in advance when their work is approaching. The fever chart plots buffer consumption against critical-chain completion and replaces task-level percent-complete reporting with a system-level signal that is harder to game.
The entries here cover the Critical Chain itself and its distinction from the critical path; the Project Buffer, Feeding Buffer, and Resource Buffer as the three distinct CCPM mechanisms (each easy to confuse with the others until the function is named); the Fever Chart as the operational feedback loop; Student Syndrome as the empirical tendency to delay starting until the embedded safety is consumed; Bad Multitasking as the antipattern of forcing context-switching under management pressure; Pipeline Management and Pipeline Planning as the multi-project release-control layer; and Agile CCPM as Ujigawa & Updegrove’s 2016 reformulation for software development teams.
Three antipatterns live inline here next to the mechanisms designed to address them. Parkinson’s Law in Projects is the tendency for work to expand to fill the time allotted — the partner antipattern to Student Syndrome. Padding Without Aggregating is the project-management failure mode that CCPM’s entire architecture is the systematic response to: adding safety to every individual task instead of stripping individual safety and aggregating it into a shared buffer. The Multi-Tasking Cascade is the systemic organizational form of bad multitasking — a policy constraint, not an individual behavior problem, and the right response is to sequence project starts rather than run all projects simultaneously.
A practical reading path starts with the Critical Chain entry for the conceptual advance over critical path, then the Project Buffer, Feeding Buffer, and Resource Buffer for the three distinct mechanisms, then the Fever Chart for the operational feedback loop, then the four behavioral antipatterns (Student Syndrome, Parkinson’s Law, Padding Without Aggregating, Multi-Tasking Cascade) to recognize what CCPM is built to address. Pipeline Management and Pipeline Planning carries the multi-project release rule; Agile CCPM closes the section for software teams adopting CCPM in sprint-based environments.