Schedule Compression Techniques — Crashing and Fast Tracking on Critical Path
A project manager is developing the project schedule using a predictive approach. The project involves multiple dependencies and a critical path that has been identified. Which TWO of the following are valid techniques for schedule compression that can be applied to activities on the critical path?
Quick Answer
The answer is fast-tracking and crashing, as these are the two primary schedule compression techniques applied to activities on the critical path. Fast-tracking works by performing critical path activities in parallel that were originally sequential, which compresses the schedule without adding resources but increases risk due to rework potential. Crashing, on the other hand, adds resources—such as extra staff or overtime—to critical path tasks to reduce their duration, directly shortening the project end date at an increased cost. On the CAPM exam, this question tests your understanding that only critical path activities yield schedule compression; compressing non-critical path work does not affect the project finish date. A common trap is confusing fast-tracking with crashing—remember that fast-tracking changes logic (parallel vs. sequential) while crashing changes resources (more people or money). A useful memory tip: “Fast-track flips the order, crashing costs more.”
⚠ Common exam trap
PMI often tests the distinction between schedule compression techniques (crashing and fast-tracking) and resource optimization or risk analysis techniques, leading candidates to confuse resource leveling or Monte Carlo simulation as compression methods.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Crashing - adding resources to critical path activities to reduce duration.
Crashing and fast-tracking are both schedule compression techniques that focus on the critical path. Crashing reduces duration by adding resources to critical path activities, while fast-tracking performs critical path activities in parallel that were originally sequential, thereby shortening the overall schedule. Both are valid because they directly target the critical path, where any reduction directly impacts the project completion date.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Crashing - adding resources to critical path activities to reduce duration.
Why this is correct
Crashing shortens the critical path by adding resources, directly targeting the schedule constraint the stem identifies. Because only critical path activities govern total project duration, compressing them yields immediate schedule reduction, though it typically increases cost and risk. This satisfies the stem's requirement for a valid compression technique applicable to critical path activities.
- ✗
Resource leveling - adjusting start and finish dates based on resource constraints.
Why it's wrong here
Resource leveling adjusts dates to resolve resource overallocation, which typically extends the schedule rather than compressing it. It tempts teams addressing resource constraints, but leveling is the correct choice when smoothing demand within fixed availability, not when shortening critical-path duration through crashing or fast-tracking.
- ✓
Fast-tracking - performing critical path activities in parallel that were originally sequential.
Why this is correct
Fast-tracking compresses the schedule by overlapping critical path activities that were originally sequential, directly shortening the longest path. It satisfies the stem's constraint of applying compression only to critical path activities, since parallelising non-critical work yields no duration benefit. The trade-off is increased rework risk from dependencies.
- ✗
Monte Carlo simulation - analyzing probable schedule outcomes.
Why it's wrong here
Monte Carlo simulation models probabilistic schedule outcomes for risk analysis; it does not shorten critical-path duration, which is what compression requires. It tempts teams quantifying schedule uncertainty, but simulation is the correct choice when forecasting completion confidence, not when crashing or fast-tracking activities to meet a deadline.
- ✗
Critical chain method - adding buffers to protect the schedule.
Why it's wrong here
Critical chain method inserts buffers and removes safety padding, protecting the schedule rather than compressing critical-path activities. It tempts teams seeking schedule protection, but critical chain is the correct choice when managing buffer consumption across a resource-constrained network, not when crashing or fast-tracking to reduce duration.
Go deeper
Related to this question
About these practice questions
This CAPM question is part of Courseiva's 451-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on CAPM
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A software development project is using a predictive approach with a detailed project schedule based on the critical path method (CPM). The project is currently in the execution phase. The team reports that a critical task (Task X) is two weeks behind schedule. Task X has a total float of 0 and has two immediate successors: Task Y and Task Z, both of which are also on the critical path. The project manager has the ability to add resources to overlapping tasks. The project sponsor is concerned about the schedule delay and wants a recovery plan. The project manager needs to determine the best course of action to get the project back on track without impacting quality or budget excessively.
medium- A.Reduce the scope of Task X to meet the original deadline.
- B.Re-baseline the schedule to reflect the delay and inform the sponsor.
- ✓ C.Crash Task X by adding more resources to complete it faster.
- D.Fast-track the successors by starting them as soon as possible even if the predecessor is incomplete.
Why C: Task X is on the critical path with zero total float, meaning any delay directly impacts the project end date. Crashing involves adding resources to critical path tasks to shorten their duration, which is a schedule compression technique. Since the project manager can add resources to overlapping tasks, crashing Task X is the most direct way to recover the schedule without changing scope or re-baselining.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This CAPM practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CAPM exam.