A predictive project is running late and the sponsor has directed the team to shorten the remaining schedule. The activities on the critical path have mandatory finish-to-start dependencies and cannot be performed in parallel, but the sponsor has approved additional budget and additional staff. Which schedule compression approach best fits these constraints?
- AFast track by overlapping the critical path activities so they run concurrently.
- BCrash a non-critical activity that has spare total float to reduce cost.
- CCrash the critical path activities by adding the approved resources. Correct
- DReduce the project scope and re-baseline the schedule to the new end date.
Why A is wrong: Fast tracking overlaps activities normally done in sequence, but these activities have mandatory finish-to-start dependencies and physically cannot overlap, so fast tracking is not available here.
Why B is wrong: Crashing a floated, non-critical activity spends money without shortening the project, because only the critical path drives the finish date and float elsewhere does not affect it.
Why C is correct: Crashing adds resources to critical path activities to shorten their duration, which fits a case where extra budget and staff are available and the mandatory dependencies rule out fast tracking.
Why D is wrong: Cutting scope changes what the project delivers rather than compressing the existing work, and re-baselining to a later date does not pull the finish in, so it is not a compression technique.