The complete guide, from the team that built Concerto with Goldratt.
Critical Chain Project Management (CCPM) is a method for planning and running projects around the longest chain of dependent tasks once resource limits are taken into account. Eliyahu Goldratt introduced it in his 1997 book Critical Chain, building on his Theory of Constraints. CCPM removes the safety padding from individual tasks and pools it into shared buffers that protect the finish date. Teams then manage by buffer consumption instead of task deadlines or earned value. In multi-project organizations, CCPM also limits how many projects run at once, so work flows instead of piling up. Realization's customers using the method report 25 to 50% shorter project timelines and 20 to 30% more throughput.
Critical chain project management is a scheduling method that plans a project around its scarcest resources, not just the order of its tasks.
Every project plan has a sequence of tasks that depend on each other. The critical path method stops there and assumes the right people will be free when each task is due. CCPM doesn't make that assumption. If the same engineer is needed for two tasks, those tasks can't happen at the same time, and that changes the schedule. The longest chain of tasks, once both task dependencies and resource dependencies count, is the critical chain.
CCPM rests on three ideas:
1. Plan with focused estimates. Each task gets the time it needs when someone works on it without interruptions, not a padded "safe" estimate.
2. Protect the project, not the task. The safety time removed from tasks goes into buffers that protect the delivery date.
3. Manage by buffers. Instead of asking "is this task on time?", managers ask "how much buffer has this project used, compared with how much work is done?"
The short version: stop protecting every task, and start protecting the promise to the customer.
Eliyahu Goldratt was an Israeli physicist who wrote business books as novels. The Goal (1984) introduced the Theory of Constraints: every system has one constraint that limits its output, so you get more done by managing everything around that constraint. It sold over seven million copies.
In 1997 Goldratt applied the same thinking to projects in Critical Chain. In a project, the constraint is the critical chain, and the biggest enemy is the way people protect themselves with safety time that never gets used well.
Realization's story is tied to that book. Our founder, Sanjeev Gupta, had used the ideas in The Goal to turn around a bottlenecked Xerox plant. Goldratt sent him the galleys of Critical Chain, and the two discussed how software could make the method work. When an aerospace and defense company asked Goldratt to implement Critical Chain, he called Sanjeev. That project became Concerto, project scheduling software built for many projects at once. In 1999 Realization became the first company to bring multi-project, web-based scheduling to projects, and the US Patent Office later granted Realization a patent for multi-project management using the Critical Chain methodology.
See ConcertoMost project plans already contain plenty of safety. Projects still finish late. Goldratt pointed to four behaviors that eat the safety:
Behavior
What happens
The result
Student syndrome
People start a task as late as they safely can, because the estimate has padding
The padding is gone before the work begins
Parkinson's law
Work expands to fill the time available
Early finishes are rare, so gains never pass on
Bad multitasking
People switch between several projects at once
Every task takes longer, on every project
Hidden resource conflicts
Two tasks need the same person at the same time
One of them waits, and the plan didn't show it
The result is a pattern most managers know well: delays pass down the line, but early finishes never do. CCPM is designed to break that pattern.
Traditional estimates often include enough safety to finish 90% of the time. CCPM plans each task with a focused duration, the time the work takes without interruptions. Teams commonly start by cutting estimates roughly in half. The point isn't to make people work faster. It's to move the safety somewhere it can actually protect the project.
Next, the plan is leveled so no person or piece of equipment is booked twice at the same time. The longest chain of dependent tasks after leveling is the critical chain. It often crosses between branches of the plan, because a shared resource connects them.
The safety removed from tasks goes back in as buffers, placed where they protect the finish date.
Once a task on the critical chain starts, the person works on it until it's done and hands it over immediately, like a relay runner passing the baton. The next person is ready because resource buffers warned them in advance.
Every project reports two numbers: how much of the critical chain is complete, and how much of the project buffer is used. Plotted together, they show whether the project is in the green, yellow or red zone. Managers act only on projects in trouble, and they act early.
Buffer
Where it goes
What it protects
Project buffer
At the end of the critical chain
The delivery date of the whole project
Feeding buffer
Where a non-critical branch joins the critical chain
The critical chain from delays on side branches
Resource buffer
Before a critical task, as an early warning
That the right person is ready when the critical task arrives
The project buffer is the one that matters most. One shared buffer is much smaller than the sum of all the task padding it replaces, because not every task runs late. That's how CCPM shortens projects without asking anyone to rush.
The critical path method (CPM) and CCPM both look for the longest chain of tasks. The difference is what they count.
Question
Critical path method
Critical chain project management
What sets the schedule
Task dependencies
Task dependencies and resource availability
Where safety sits
Inside every task estimate
In shared buffers
How progress is tracked
Task deadlines, earned value
Buffer consumption against work completed
Multitasking
Allowed, often encouraged
Discouraged; finish one task before starting the next
Many projects at once
Each project planned on its own
Projects staggered around the shared constraint
CPM is still useful for understanding task logic. CCPM adds what CPM leaves out: people can't be in two places at once.
Most organizations don't run one project. They run dozens or hundreds that share the same engineers, mechanics, test cells and hangar bays. This is where CCPM makes the biggest difference, and where most CCPM implementations either succeed or fail.
Multi-project CCPM adds two rules:
1. Limit work in process. Release a new project only when there is capacity to work on it. Starting everything early feels productive, but it spreads people thin and slows every project down.
2. Stagger projects around the constraint. Pick the resource that limits the whole organization and schedule project starts around its capacity. This is often called pipelining.
To solve traffic jams, you don't add more cars to the road. You find ways to reduce their number. That's the logic behind Realization's Focus & Finish approach: fewer projects in progress at any moment, each one finishing faster.
Running this by hand for more than a few projects is close to impossible, because every delay changes the schedule for everyone else. That's why we built Concerto as multi-project CCPM software from the start.
How Concerto schedules many projects at onceThese are results Realization customers reported after adopting critical chain scheduling, in their own words and figures.
Organization
Industry
Before
After
US Navy, Fleet Readiness Center Southeast (F-18)
Aircraft maintenance
6 aircraft a year, 36 aircraft in work
11 aircraft a year (+81%), 17 in work
Airbus Defence and Space
Satellite engineering
24 drawings a week, 41% engineering cost overrun
32 drawings a week, 6% overrun
Emesa
Rail station construction
5 months late with 6 months left
Completed 11 months of work in 6 months; €5M penalty avoided
"The results have been substantial. A 35% reduction in flow days. 44% reduction in WIP."
Bill Best, Director, Warner Robins Air Logistics Center
"We were able to see an 18% reduction in our cycle time. From a projected 17-month effort to finishing in 14 months."
Steven Pryor, Director, Spirit AeroSystems
See all customer resultsCCPM is a change in how people work, not just a new schedule. The rollouts that stick usually follow the same path:
1. Find the constraint. Map current projects, shared resources and where work waits the longest.
2. Cut work in process. Freeze or delay some projects so the rest can move. This step is uncomfortable, and it delivers the fastest gains.
3. Rebuild the plans. Focused durations, the critical chain and buffers, project by project.
4. Change the daily routine. Teams work from task priorities; managers review buffer status, not task dates.
5. Sustain it. Weekly buffer reviews and coaching until the behavior is a habit.
Most Realization customers see results within 90 days.
How we run CCPM implementation with clientsCCPM stands for Critical Chain Project Management, the method Eliyahu Goldratt described in his 1997 book Critical Chain. In project work it doesn't refer to the clinical or construction certifications that share the same letters.
The Critical Path Method (CPM) finds the longest chain of dependent tasks and assumes resources are available. CCPM adds resource dependencies to find the critical chain, removes task padding and protects the finish date with buffers that teams watch every day.
Student syndrome is the habit of starting a task as late as possible because the estimate includes safety time. CCPM counters it by using focused estimates and a shared project buffer, so there's no private padding to wait out.
CCPM and agile solve different problems. Agile manages changing requirements inside a team. CCPM manages time and shared resources across tasks and projects. Some organizations use both: agile within a team's work, CCPM for the delivery date and the portfolio.
Yes. Realization's Concerto is multi-project CCPM software, built with Goldratt's input in the late 1990s. It schedules all projects against shared resources and tracks buffer status for every project.
If you can live with small incremental improvements, you don't need us. If you want your projects to finish far faster, let's talk.
Sources: Goldratt, E. M. (1997), Critical Chain, North River Press. Goldratt, E. M. (1984), The Goal. Customer figures and quotes as published by Realization.