Perform Critical Path Analysis: PMP Learning Guide
Process learning · Perform Critical Path Analysis
Introduction
Performing Critical Path Analysis (CPA) is the core quantitative project scheduling and schedule controls discipline of analyzing the sequence, durations, and logical dependencies of all project activities to determine the longest sequence of dependent tasks (the Critical Path), calculating the shortest possible project completion duration, and evaluating activity float.
In project delivery, attempting to manage a complex schedule without Critical Path Analysis is like navigating blindfolded. Project managers waste time expediting non-critical tasks that have weeks of schedule float while ignoring delayed critical path activities, leading to inevitable project completion failures. Furthermore, when near-critical paths (paths with low total float, e.g., 1-2 days) are unmonitored, unexpected minor delays cause them to surpass the original critical path, causing unexpected project delays.
Project managers master Critical Path Analysis by executing mathematical Two-Pass Algorithms (Forward Pass and Backward Pass), calculating Total Float and Free Float for every activity, monitoring near-critical path vulnerabilities, and executing targeted Schedule Compression (Crashing and Fast-Tracking) strictly on critical path activities to recover delayed project baselines.
Why it matters
Failing to perform critical path analysis leads to inaccurate milestone commitments, wasted resources crashing non-critical tasks, unexpected project delays, and severe contractual late penalties.
Conversely, rigorous Critical Path Analysis provides absolute schedule control. Project managers pinpoint exactly which activities dictate project completion, allocate premium resources to critical tasks, and compress timelines with mathematical precision.
Furthermore, dynamic critical path models empower project leaders to defend schedule baselines with objective data during executive reviews and client change negotiations.
Practical framework
The 5-Step Critical Path Analysis Framework
1. Verify schedule network diagram logic and activity durations
Ensure all WBS work packages are decomposed into discrete activities with single-point or three-point duration estimates and valid PDM dependencies.
2. Execute the Forward Pass (Early Dates Calculation)
Calculate Early Start (ES) and Early Finish (EF) from project start to finish: $EF = ES + ext{Duration} - 1$. At merge points, $ES = \max(EF_{ ext{Predecessors}}) + 1$.
3. Execute the Backward Pass (Late Dates Calculation)
Calculate Late Finish (LF) and Late Start (LS) from project finish to start: $LS = LF - ext{Duration} + 1$. At burst points, $LF = \min(LS_{ ext{Successors}}) - 1$.
4. Compute Total Float, Free Float, and identify the Critical Path
Calculate $ ext{Total Float} = LS - ES$. Identify all activities with $ ext{Total Float} = 0$: the resulting continuous path is the Critical Path.
5. Monitor near-critical paths and execute targeted compression
Track activities with low float ($\le 3 ext{ days}$). If project delay occurs, crash or fast-track only activities on the critical path to recover the baseline.
Worked project scenario
An engineering and construction corporation was executing a $15M automated logistics distribution warehouse expansion project with 120 work packages. At Month 4, the project was 14 days behind schedule due to unexpected bedrock rock-drilling delays during foundation excavation. The project sponsor demanded that the project manager compress the schedule immediately. The assistant project coordinator proposed spending $80,000 in overtime to crash Activity 42 ('Fabricate Internal Office Partition Walls'), claiming it was a large 30-day task that could easily be accelerated.
The senior project controls manager conducted a formal Critical Path Analysis:
1. Executed a complete Two-Pass CPM calculation across the entire schedule network:
- Discovered that Activity 42 (Office Walls) had +22 days of Total Float; spending $80,000 to accelerate it would produce exactly zero days of project schedule compression.
- Identified the true Critical Path: Foundation Pours $
ightarrow$ Conveyor Steel Superstructure $
ightarrow$ High-Voltage Power Drop $
ightarrow$ SCADA System Commissioning (Total Duration: 240 days; Total Float $= -14 ext{ days}$).
- Identified a Near-Critical Path: Automated Sprinkler System Installation (Total Float $= +2 ext{ days}$).
2. Designed a targeted schedule compression strategy:
- Fast-tracked Conveyor Steel Superstructure by starting electrical conduit wiring in parallel ($SS + 4 ext{d}$ lead).
- Crashed High-Voltage Power Drop by adding a certified second technician crew at a cost of $25,000, recovering 14 days of delay.
3. Actively monitored the near-critical sprinkler path to ensure it did not become critical.
The targeted critical path intervention recovered 100% of the 14-day schedule delay, saved $55,000 in misallocated overtime, and delivered the warehouse on time.
Professional guidance
When answering PMP exam questions regarding schedule delays, finding the critical path, calculating float, or applying schedule compression (crashing/fast-tracking), remember that the Critical Path is the longest path with zero (or negative) total float.
Be cautious of distractors that advise crashing non-critical activities (which wastes budget and provides zero time savings), assuming the critical path is the path with the fewest tasks, or ignoring near-critical paths when calculating schedule risk.
The candidate must recognize that Critical Path Analysis is the mathematical heart of schedule management; any acceleration or compression must target the critical path to be effective.
Key takeaway
Critical Path Analysis provides the mathematical foundation of schedule control. By identifying critical path drivers, governing total float, and executing targeted compression, project managers ensure reliable, on-time project completion.
Key points
- The Critical Path is the longest sequence of dependent activities through the schedule network, dictating project duration.
- Activities on the Critical Path have Total Float $\le 0$; any delay on a critical activity directly delays project completion.
- Execute the Forward Pass to determine Early Start (ES) and Early Finish (EF); Backward Pass to determine Late Start (LS) and Late Finish (LF).
- Calculate Total Float ($ ext{TF} = LS - ES = LF - EF$) and Free Float ($ ext{FF} = ES_{ ext{Successor}} - EF - 1$).
- Monitor 'Near-Critical Paths' (paths with float $<5 ext{ days}$) to prevent secondary paths from unexpectedly delaying the project.
Critical Path Method (CPM) Two-Pass Mathematical Model
| Calculation Dimension | Mathematical Formula | Schedule Rule / Principle | |||||||
|---|---|---|---|---|---|---|---|---|---|
| Early Finish (EF) | $EF = ES + ext{Duration} - 1$ | Earliest possible calendar date the activity can complete | |||||||
| Early Start Merge Rule | $ES_{ ext{Successor}} = \max(EF_{ ext{Predecessors}}) + 1$ | When multiple paths merge, successor cannot start until the latest predecessor completes | |||||||
| Late Start (LS) | $LS = LF - ext{Duration} + 1$ | Latest calendar date the activity can start without delaying project end date | |||||||
| Late Finish Burst Rule | $LF_{ ext{Predecessor}} = \min(LS_{ ext{Successors}}) - 1$ | Predecessor must finish before the earliest successor late start date | |||||||
| Total Float (TF) | $ ext{Total Float} = LS - ES = LF - EF$ | Total scheduling flexibility before project completion date is breached ($ ext{TF} \le 0 | |||||||
| Free Float (FF) | $ ext{Free Float} = \min(ES_{ ext{Successors}}) - EF_{ ext{Activity}} - 1$ | Scheduling flexibility before the immediate successor activity's early start date is delayed | |||||||
| Activity ID | Task Description | Duration | Predecessor | ES | EF | LS | LF | Total Float | Critical Path? |
| Task A | Soil Excavation & Site Prep | 5 Days | None | Day 1 | Day 5 | Day 1 | Day 5 | 0 Days | Yes (Critical) |
| Task B | Poured Concrete Slab Foundation | 12 Days | Task A | Day 6 | Day 17 | Day 6 | Day 17 | 0 Days | Yes (Critical) |
| Task C | Prefabricated Conveyor Delivery | 8 Days | Task A | Day 6 | Day 13 | Day 10 | Day 17 | +4 Days | No (Float = 4d) |
| Task D | Structural Steel Framing | 10 Days | Task B, Task C | Day 18 | Day 27 | Day 18 | Day 27 | 0 Days | Yes (Critical) |
| Task E | Final Electrical Commissioning | 6 Days | Task D | Day 28 | Day 33 | Day 28 | Day 33 | 0 Days | Yes (Critical - Total: 33d) |
Frequently asked questions
What is the Critical Path in a schedule network?
The Critical Path is the sequence of dependent activities that represents the longest path through the project network diagram, determining the shortest possible duration to complete the project, with Total Float equal to zero (or negative).
What happens if an activity with 5 days of Total Float is delayed by 8 days?
The first 5 days of delay consume the available float; the additional 3 days of delay directly extend the overall project completion date by 3 days and convert that activity onto the new Critical Path.
Why should schedule crashing only be applied to critical path activities?
Because crashing non-critical activities shortens tasks that already have excess float, spending money without shortening the overall project duration; only compressing critical path tasks accelerates project completion.
What is a 'Near-Critical Path'?
A Near-Critical Path is a sequence of activities whose total float is very low (e.g., 1-3 days); if any minor delay occurs on a near-critical path, it easily becomes the new critical path.