Schedule Compression: Crashing vs. Fast-Tracking Tradeoffs
Shorten project schedules without altering total scope using cost vs. risk trade-offs.
📌 Direct Answer / Executive Definition
Schedule Compression is a schedule optimization technique used to shorten the total project duration without changing the overall project scope. The two primary methods are Crashing (adding resources or paid overtime to critical path tasks, which increases cost) and Fast-Tracking (reconfiguring sequential critical path activities to run in parallel, which increases project risk and rework).
Why Trade-Off Analysis in Schedule Compression Matters for Project Delivery
Project managers faced with schedule delays or fixed market launch deadlines must evaluate whether spending budget (crashing) or accepting overlap risk (fast-tracking) is the optimal path forward.
Standard Syntax, Derivation & Framework Pattern
/* Schedule Compression Decision Framework */
Target: Shorten project schedule by 3 weeks
Method 1: Crashing
- Action: Add 2 senior developers to critical path module.
- Impact: Budget increases by $15,000.
- Risk: Low to moderate.
Method 2: Fast-Tracking
- Action: Start software testing in parallel with backend build.
- Impact: Budget impact $0.
- Risk: High risk of rework if backend APIs change.
Rule: Apply compression ONLY to activities on the Critical Path!Core Rules & Certification Takeaways
- Crashing always increases financial cost (overtime pay, contractor resources, expedited shipping).
- Fast-tracking always increases operational risk and potential rework.
- Schedule compression must only be performed on critical path activities; compressing non-critical tasks only generates excess float.
- Always evaluate the crash cost slope (Crash Cost - Normal Cost) / (Normal Time - Crash Time) to crash least expensive tasks first.
🔗 Related Architectural Concepts & Next Steps
Deepen your mastery with connected topics across our curriculum and knowledge hubs.
Frequently Asked Questions (FAQ)
Why is compressing non-critical path activities ineffective?
Non-critical activities have float; shortening them does not reduce the total duration of the project because the project completion is dictated solely by the critical path.
What is the main downside of fast-tracking?
Fast-tracking increases the risk of rework, mistakes, and coordination overhead because dependent activities are performed in parallel before predecessor deliverables are verified.
Want complete video breakdowns & exercises?
Explore full step-by-step masterclass training in Project Management Fundamentals.