Your project is behind schedule, and you need to compress the schedule. The critical path has been identified. What is the BEST schedule compression technique to use if you have additional budget available?
Crashing adds resources to critical path activities to shorten duration, and it directly consumes the additional budget the stem makes available. Unlike fast tracking, it introduces no added rework risk from parallel activities, making it the best fit for this constraint.
Why this answer
Crashing is the correct technique because it involves adding resources (e.g., overtime, additional staff, or expedited shipping) to critical path activities to compress the schedule, and the question explicitly states additional budget is available. Unlike fast tracking, crashing does not increase risk but does increase cost, making it the best choice when budget is not a constraint.
Exam trap
The trap here is that candidates often confuse fast tracking with crashing, thinking both compress the schedule, but fast tracking increases risk while crashing increases cost—and the question explicitly provides additional budget, making crashing the clear choice.
How to eliminate wrong answers
Option A is wrong because fast tracking involves performing critical path activities in parallel that were originally sequential, which increases risk and rework potential without requiring additional budget; it does not directly use extra funds. Option C is wrong because resource smoothing is a technique to adjust resource usage within the float constraints to avoid peaks and troughs, not to compress the schedule; it does not shorten the critical path. Option D is wrong because resource leveling is used to resolve resource over-allocation by delaying tasks, which often increases the project duration, the opposite of schedule compression.