Modules 4-6: Structural Architecture of Safety

Module 4: Critical Path vs. Critical Chain

Redefining the longest chain of dependencies.

• Core Concept: The "Critical Path" ignores resource contention. The "Critical Chain" identifies the longest sequence of steps considering both task and resource dependencies.
• Key Principles: When a department is needed for multiple paths, it creates a "Resource Bottleneck" that becomes the true constraint.
• System Insight: "Early Starts" for non-critical tasks are dangerous; they pull resources away from the constraint. "Late Starts" are equally dangerous.
• Practical Application: Build your project schedule by identifying the bottleneck and scheduling all other tasks around its availability.

Module 5: Buffer Management (Core Concept)

Protecting the whole instead of the parts.

• Core Concept: Aggregating safety into a centralized "Project Buffer."
• Key Principles: Use median (50% probability) task estimates. Take the safety "pad" removed from tasks and move exactly 50% of it into the Project Buffer.
• System Insight: Buffer Penetration is the only metric of project health. If the Critical Chain is 20% done but the Buffer is 50% consumed, the project is in the "Red Zone."
• Practical Application: Abolish local deadlines. Measure performance by the rate of Project Buffer consumption relative to Critical Chain completion.

Module 6: Types of Buffers

Strategic placement of safety to ensure synchronization.

• Project Buffer: Placed after the final task to protect the delivery date.
• Feeding Buffer: Placed wherever a non-critical path merges with the Critical Chain. This prevents "path merges" from delaying the constraint.
• Resource Buffer: A "wake-up call" signal sent to a bottleneck resource to ensure they are ready to begin exactly when needed.