Critical Chain¶
Goldratt, E. M. (1997). Critical Chain. North River Press.
Cited by¶
3 citations across 3 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Parkinson's Law
- In project and time management, two-week tasks given six weeks consume six, and entire scheduling disciplines exist to protect against the effect.
This sourceIntroduces critical-chain project management and buffer aggregation as a discipline to counter task-level padding and the fill-the-time effect (student syndrome / Parkinson's Law).
- In project and time management, two-week tasks given six weeks consume six, and entire scheduling disciplines exist to protect against the effect.
- Sequencing
- Sequencing reframes overwhelming complexity (hundreds of interdependent tasks) into a tractable optimization problem: identify tasks and dependencies, choose an ordering criterion (minimize time, minimize cost, maximize learning, respect causality), and execute, an approach Goldratt (1997) extends in his Critical Chain method by recasting project complexity as a sequencing problem under resource and behavioral constraints.
This sourceRecasts project complexity as a sequencing problem dominated by the resource-constrained chain rather than the dependency-only critical path; integrates behavioral effects (student syndrome, multitasking) into sequencing design.
- Sequencing reframes overwhelming complexity (hundreds of interdependent tasks) into a tractable optimization problem: identify tasks and dependencies, choose an ordering criterion (minimize time, minimize cost, maximize learning, respect causality), and execute, an approach Goldratt (1997) extends in his Critical Chain method by recasting project complexity as a sequencing problem under resource and behavioral constraints.
Mechanisms¶
- Schedule Float Stack Review
- Managing float as a shared, positioned buffer rather than private per-task slack is the core insight of critical-chain scheduling.
This sourceTreats project and feeding buffers as shared, positioned protection created by removing safety from individual task estimates.
- Managing float as a shared, positioned buffer rather than private per-task slack is the core insight of critical-chain scheduling.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 1 other way.
Registry ID ref:fecc665446fc · see in the full table