Portfolio Critical Chain: Theory of Constraints in Project Management

PMBOK v8 Definition

The Theory of Constraints (TOC) is a body of knowledge focused on improving system-level performance of an organization, end-to-end process, project portfolio, or project. The TOC application to a project or project portfolio is critical chain project management (CCPM). CCPM is a set of techniques used to promote fast execution and high due-date performance by aggregating task-level (or sprint-level) variability to a project buffer, and then allocating the project buffer only when and where needed to protect the project due date.

Why It Matters for the Exam

Portfolio Critical Chain appears frequently in PMI exam questions about schedule management and resource optimization. It is tested primarily in situational questions where you must identify the correct approach for managing multiple projects with shared resources, buffer management, and protecting project due dates against uncertainty.

Key Points to Remember (for the exam)

• Core Concept: CCPM aggregates task-level variability into a project buffer rather than adding buffers to individual tasks
• Key Difference: A critical chain buffer is in lieu of task-level or sprint-level buffers, not in addition to them
• Scheduling Logic: CCPM uses nearly identical logic as the Critical Path Method (CPM), both based on critical path analysis
• Resource Consideration: CCPM calls for a resource-loaded and resource-leveled critical path (RLCP)
• Critical Chain Definition: When identifying the longest path or chain of tasks, "the RLCP" is synonymous with "the critical chain"
• Primary Objective: Promotes fast execution and high due-date performance
• Application Scope: Applies to projects, project portfolios, and end-to-end processes

Typical PMI Exam Example

A project manager is managing three concurrent projects that share a specialized engineering team. Task-level buffers have been causing extended timelines. The PM decides to implement CCPM by removing individual task buffers and creating a single project buffer at the end of each project schedule. This approach aggregates variability and protects the overall project due dates.

PMI Exam Traps

• Trap: Confusing project buffer with task-level contingency reserves

  • Reality: CCPM buffers replace task-level buffers, while traditional contingency reserves are added in addition to task buffers

• Trap: Thinking CCPM and CPM are completely different methods

  • Reality: CCPM uses nearly identical scheduling logic as CPM; both are based on critical path analysis

• Trap: Assuming CCPM only applies to single projects

  • Reality: CCPM applies to portfolios, end-to-end processes, and organizational system-level performance

• Trap: Confusing CCPM buffers with management reserve

  • Reality: CCPM buffers are planned and allocated based on aggregated task variability, not unknown unknowns

Important PMI Connections

Quick Review Questions

1. What is the primary difference between a critical chain buffer and traditional contingency reserves?

2. When CCPM is used, where is variability aggregated to protect the project due date?

3. What does "RLCP" stand for, and how does it relate to the critical chain?

4. In CCPM, are task-level buffers kept in addition to the project buffer, or are they replaced?

5. Can CCPM be applied to project portfolios, or is it limited to individual projects?

PMBOK v8 Reference

Section 5 – Tools and Techniques (pages 159-160) Critical chain project management (CCPM) - Theory of Constraints application to projects and portfolios