Rishekesh Ramesh's Key Ideas from Critical Chain
by Eliyahu M. Goldratt

This truism suggests that most people do not fully apply themselves to activities until at least half the time allocated has elapsed. This idea of planned procrastination has been backed by research and appears to be entirely normal behavior. But it does mean that any margin for error is removed, resulting in a tendency for work to be completed late, no matter how much time has been allocated.

When several workstreams on a project come together into a single dependent activity, that dependent activity cannot start until all of the preceding workstreams have been completed. This means that if you have five workstreams all coming together for (for example) an end-to-end system test phase, then even if 4 of the 5 streams finished early, the testing will still start late if the fifth stream is delayed.

Attributed to C. Northcote Parkinson, Parkinson’s Law on the pursuit of progress states that work expands to fill the time available for its completion.

Given what we know of Student Syndrome and Parkinson’s law, adding contingency to tasks on a project simply results in the project delivering later. Often, contingency is mentally factored in by people working on the project, they will start fully applying later than normal when there is an understanding that contingency exists. This can end up with situations where adding contingency not only makes delivery later, but the contingency is actually over-run, and projects get even later. For this reason, CCPM usually requires specialist software to calculate and keep track of the time buffer.

When using the CCPM, we avoid focusing on milestones for delivery. Instead, we focus on encouraging and rewarding behaviors that lead to the delivery of critical activities as fast as possible. This requires a change of reporting and a change in mindset. To avoid Parkinson’s law, we focus on delivering as fast as possible, rather than focus on milestone dates. Rather than getting updates in terms of percentage complete, we ask for estimates of ‘Remaining Duration’. Reporting in this way provides a more realistic picture of when activity is likely to complete and prevents late-emerging issues

The Critical Chain model introduces Feed Buffers for the noncritical chain. Feed buffers are not included in the overall Project Buffer but are used as a way of insulating the critical path of the project from non-critical workstream elements. By building in Feed Buffers, CCPM reduces the risk of projects overrunning due to dependencies.

CCPM introduces a new type of chart to track projects, The Fever Chart

The fever chart plots the percentage of the Project Buffer that has been consumed against the percentage of the critical chain that has been completed. Progress is plotted as a line graph, giving a running commentary of how the project is performing. This can be applied in program and portfolio levels as well, as a diagnostic tool.

CCPM is very clear on its views on multitasking. It advocates for strict discipline where no one working on a critical path activity should be working on anything else at the same time. Eliminating multitasking can have a significant impact on productivity.