Vact The Critical Path Method: Scheduling Projects with Dependencies
The Critical Path Method (CPM) is a project scheduling technique that identifies the longest sequence of dependent tasks, which determines the shortest possible project duration. Any delay on the critical path delays the entire project. CPM has been a foundational tool in project management since its development at DuPont in the 1950s and remains essential for managing complex projects with many interdependent activities.
The Critical Path Method: Scheduling Projects with Dependencies
How CPM Works
CPM involves four steps: list all tasks, identify dependencies, estimate durations, and calculate the critical path.
Step 1: List All Activities
Break the project into individual activities with defined start and end points. Each activity should be small enough to estimate accurately — typically one to ten days of work. For a well-scoped project, this list comes directly from the work breakdown structure.
Step 2: Identify Dependencies
For each activity, determine which other activities must be completed before it can start. Dependencies fall into four types:
- Finish-to-Start (FS): Task B cannot start until Task A finishes. This is the most common dependency type.
- Start-to-Start (SS): Task B cannot start until Task A starts. Both tasks can run in parallel after that point.
- Finish-to-Finish (FF): Task B cannot finish until Task A finishes.
- Start-to-Finish (SF): Task B cannot finish until Task A starts. This is rare in practice.
Step 3: Estimate Durations
Assign a duration estimate to each activity. Use historical data, expert judgment, or estimation techniques. For uncertain estimates, the Program Evaluation and Review Technique (PERT) uses three estimates — optimistic, most likely, and pessimistic — to calculate an expected duration.
Step 4: Calculate the Critical Path
Build a network diagram showing all activities and their dependencies. Perform a forward pass to calculate the earliest start and finish times for each activity. Then perform a backward pass to calculate the latest start and finish times. The difference between earliest and latest times is the float (or slack) for each activity.
The critical path is the sequence of activities with zero float — any delay in these activities directly delays the project end date.
Reading the Network Diagram
Each activity node in a CPM network contains:
| Field | Description |
|---|---|
| ES (Early Start) | Earliest the activity can begin |
| EF (Early Finish) | ES + Duration |
| LS (Late Start) | Latest the activity can begin without delaying the project |
| LF (Late Finish) | Latest the activity can end without delaying the project |
| Float | LS - ES (or LF - EF) |
Activities with zero float are on the critical path. Activities with positive float have scheduling flexibility — they can be delayed by up to their float without affecting the project end date.
Practical Applications
Resource Leveling
CPM reveals which activities have float, allowing project managers to shift non-critical activities to balance resource utilization. If two activities need the same resource but one has float, the one with float can be rescheduled.
Schedule Compression
When the calculated project duration exceeds the deadline, CPM helps identify where to apply schedule compression techniques:
Crashing. Add resources to critical path activities to reduce their duration. Crashing increases cost but reduces schedule.
Fast-tracking. Run critical path activities in parallel instead of sequentially. Fast-tracking increases risk because dependent activities overlap.
Both techniques focus on the critical path because compressing non-critical activities does not shorten the project.
Risk Identification
Activities on the critical path represent the highest schedule risk. Risk management strategies should prioritize these activities. A delay in any critical path activity is a project delay.
CPM in Modern Project Management
CPM was designed for waterfall projects with well-defined activities and dependencies. Modern tools like Microsoft Project, Primavera, and Smartsheet automate CPM calculations and display critical paths on Gantt charts.
In agile environments, CPM is less commonly used at the task level because sprints operate on a fixed cadence rather than a dependency-driven schedule. However, CPM remains valuable for release planning, multi-team coordination, and projects with hardware or infrastructure dependencies.
CPM for Release Planning
Even agile teams face dependencies at the release level. A mobile app release might depend on API changes, database migrations, and app store review processes. Mapping these dependencies with CPM helps identify the critical path to release and highlights which work streams need to complete first.
Common Mistakes
Forgetting to update the schedule. CPM is not a one-time exercise. As activities complete (faster or slower than estimated) and new dependencies emerge, the critical path may shift. Regular updates keep the schedule accurate.
Ignoring near-critical paths. A path with only one day of float is nearly as risky as the critical path. Monitor near-critical paths because small delays can push them onto the critical path.
Over-relying on software. Tools calculate the critical path automatically, but the output is only as good as the input. Inaccurate duration estimates and missed dependencies produce misleading critical paths. Validate the tool’s output with the team.
Not communicating the critical path. Everyone on the project should know which activities are on the critical path and understand the implications of delays. Make the critical path visible in project dashboards and status reports.