Schedule Compression: Crashing and Fast-Tracking

Schedule Compression: Crashing and Fast-Tracking – A Complete PMP Exam Guide

Why Schedule Compression Matters

In the real world—and on the PMP exam—projects frequently face pressure to finish earlier than planned. Stakeholders may demand an accelerated delivery date, a critical milestone may be at risk, or a delay on the critical path may threaten the entire project timeline. Schedule compression techniques allow project managers to shorten the project schedule without reducing project scope. Understanding these techniques is essential for any project manager and is a heavily tested topic on the PMP exam aligned with PMBOK 8 and earlier editions.

What Is Schedule Compression?

Schedule compression is the umbrella term for techniques used to shorten the project schedule duration without cutting scope. The two primary methods are:

1. Crashing
2. Fast-Tracking

Both are applied to activities on the critical path because compressing non-critical-path activities will not shorten the overall project duration. This is a key concept the exam will test.

---

1. Crashing

Definition: Crashing involves adding extra resources to critical path activities in order to reduce their duration. This always increases cost.

How It Works:
- Identify activities on the critical path.
- Determine which activities can be shortened by adding resources (e.g., additional team members, overtime, premium equipment).
- Calculate the crash cost per unit of time saved for each activity: Crash Cost per Time Unit = (Crash Cost – Normal Cost) / (Normal Duration – Crash Duration).
- Select the activity with the lowest crash cost per unit of time first. This gives the greatest schedule reduction for the least additional cost.
- Continue crashing activities in order of cost-effectiveness until the desired schedule reduction is achieved or further crashing is no longer feasible.

Key Characteristics of Crashing:
- Always increases cost. This is the most important thing to remember.
- Does not always work; some activities cannot be shortened regardless of resources added (due to the law of diminishing returns or the nature of the task).
- Can create new critical paths. As you shorten one critical path, a previously non-critical path may become the new longest path.
- Only applied to critical path activities.
- May introduce new risks (e.g., quality issues from rushed work, coordination complexity).

Example:
Activity A: Normal Duration = 10 days, Normal Cost = $5,000, Crash Duration = 7 days, Crash Cost = $8,000
Crash Cost per Day = ($8,000 – $5,000) / (10 – 7) = $3,000 / 3 = $1,000 per day

Activity B: Normal Duration = 8 days, Normal Cost = $4,000, Crash Duration = 6 days, Crash Cost = $7,000
Crash Cost per Day = ($7,000 – $4,000) / (8 – 6) = $3,000 / 2 = $1,500 per day

You would crash Activity A first because it has the lower crash cost per day ($1,000 vs. $1,500).

---

2. Fast-Tracking

Definition: Fast-tracking involves performing activities in parallel (or with overlap) that were originally planned to be done sequentially.

How It Works:
- Review the critical path for activities with finish-to-start (FS) relationships.
- Identify which of those activities can logically overlap or be done concurrently.
- Modify the schedule to run those activities in parallel, either fully or partially.

Key Characteristics of Fast-Tracking:
- Always increases risk. This is the most important thing to remember. Performing activities in parallel that were planned sequentially means work may need to be redone if earlier activities produce results that affect later ones.
- Does not necessarily increase cost (at least not directly—though rework can add cost).
- Can only be applied to activities that can logically be overlapped. Some activities have mandatory dependencies (hard logic) that cannot be fast-tracked.
- Only effective on critical path activities.
- Often results in rework, which is a key risk.

Example:
Design and Build phases are planned sequentially: Design (Weeks 1–4), then Build (Weeks 5–10). By fast-tracking, you start Build in Week 3 while Design is still finishing. This saves 2 weeks but introduces the risk that design changes in Weeks 3–4 will force rework on Build activities already started.

---

Crashing vs. Fast-Tracking: Side-by-Side Comparison

Crashing:
- Adds resources to shorten duration
- Increases cost
- Risk increase is moderate
- Applied to critical path activities
- Not all activities can be crashed

Fast-Tracking:
- Overlaps sequential activities
- Cost may not increase directly
- Increases risk significantly (especially rework risk)
- Applied to critical path activities
- Only works with activities that can logically overlap

---

When to Use Each Technique

- Use crashing when budget is available but the schedule must be shortened, and risk tolerance is lower.
- Use fast-tracking when budget is tight but the organization can tolerate higher risk, or when crashing is not feasible.
- In practice (and on the exam), project managers often try fast-tracking first because it does not directly increase cost. If that is insufficient, crashing is applied.
- Sometimes both techniques are used together.

---

Important Concepts for the PMP Exam

1. Only compress critical path activities. Compressing non-critical activities does not reduce the overall project duration.

2. Watch for new critical paths. As you crash or fast-track activities on the original critical path, near-critical paths may become the new critical path. You may need to compress those as well.

3. Crashing = More Cost; Fast-Tracking = More Risk. If a question asks which technique increases cost, the answer is crashing. If it asks which increases risk, the answer is fast-tracking.

4. Neither technique reduces scope. If a question suggests reducing features to meet a deadline, that is scope reduction, not schedule compression.

5. Resource leveling is NOT schedule compression. Resource leveling adjusts the schedule to address resource constraints and usually extends the schedule. Do not confuse it with crashing or fast-tracking.

6. Mandatory dependencies cannot be fast-tracked. Only discretionary (soft logic) or external dependencies that permit overlap can be fast-tracked.

7. Crash cost calculations may appear on the exam. Know the formula: Crash Cost per Time Period = (Crash Cost – Normal Cost) / (Normal Duration – Crash Duration). Always select the activity with the lowest crash cost per unit of time.

---

Exam Tips: Answering Questions on Schedule Compression

Tip 1: Identify the Technique Being Described
If the question describes adding overtime, hiring more people, or spending more money to finish sooner, the answer involves crashing. If the question describes overlapping phases or doing activities in parallel, the answer involves fast-tracking.

Tip 2: Know the Trade-offs Cold
Crashing → increased cost. Fast-tracking → increased risk. This simple association will help you answer many questions correctly.

Tip 3: Critical Path Is Key
If a question asks how to shorten the schedule, always think about the critical path. Compressing any activity not on the critical path is a distractor and will not reduce the project end date.

Tip 4: Watch for 'Without Increasing Cost' or 'Without Increasing Risk'
If the question says the project manager needs to shorten the schedule without increasing cost, the best answer is fast-tracking. If it says without increasing risk, the better option is crashing (though crashing increases cost, it is generally less risky than fast-tracking).

Tip 5: Beware of Distractors
Options like 'reduce scope,' 'remove activities,' or 'lower quality standards' are not schedule compression techniques. Eliminate them.

Tip 6: Perform Crash Calculations Step by Step
For calculation questions: (1) Identify all critical path activities. (2) Compute crash cost per time unit for each. (3) Crash the cheapest one first. (4) Check if a new critical path has formed. (5) Repeat if needed.

Tip 7: In Agile/Hybrid Contexts
In PMBOK 8 and modern PMP exam questions, schedule compression concepts still apply. In agile environments, the equivalent might be reducing the number of stories in an iteration (which is scope adjustment, not compression) or adding team members (similar to crashing). Be aware that adding people to an agile team has diminishing returns and can slow things down initially (per Brooks' Law). The exam may test this nuance.

Tip 8: Remember the Order of Preference
On the exam, the typical preference when schedule compression is needed is: (1) Fast-track first (no direct cost increase), then (2) Crash (if fast-tracking alone is insufficient). This order reflects cost-conscious decision-making.

Tip 9: Link to Earned Value
If a question provides SPI (Schedule Performance Index) < 1.0 and asks what the PM should do, schedule compression techniques are likely part of the correct answer. This connects schedule compression to performance monitoring.

Tip 10: Practice Scenario-Based Questions
The PMP exam favors situational questions. You may see scenarios where a project is behind schedule and you must choose the best course of action. Apply the logic above: identify the critical path, consider cost and risk constraints, and select the appropriate technique.

---

Summary

Schedule compression is a vital tool in the project manager's toolkit. Crashing trades money for time by adding resources. Fast-tracking trades risk for time by overlapping activities. Both are applied exclusively to the critical path and neither reduces project scope. For the PMP exam, remember the cost-risk trade-offs, know how to calculate crash costs, and always focus on the critical path when determining where to apply compression. Mastering these concepts will help you answer a significant number of exam questions with confidence.