Schedule Compression Techniques Guide
Why Schedule Compression Techniques are Important
Schedule compression techniques are critical in project management as they help teams meet project deadlines when the initial schedule shows completion later than required. These techniques are essential tools when:
• Projects face unexpected delays
• Stakeholders request earlier delivery dates
• Market conditions demand faster time-to-market
• Resource constraints change during project execution
• Regulatory or contractual deadlines must be met
Understanding these techniques is vital for PMI-SP certification and practical project management, as compressing schedules effectively can save projects from failure while managing impacts on cost, scope, and quality.
What are Schedule Compression Techniques?
Schedule compression techniques are methodologies used to shorten the project schedule duration while minimizing impact on project scope. The PMBOK Guide identifies two primary techniques:
1. Crashing: Adding resources to critical path activities to reduce duration, typically increasing costs.
2. Fast Tracking: Performing activities in parallel that would normally be done in sequence, increasing risk but not necessarily cost.
Additional techniques that may be covered include:
3. Scope Reduction: Removing or simplifying deliverables to meet deadlines.
4. Resource Optimization: Reallocating resources from non-critical to critical activities.
5. Calendar Adjustments: Adding shifts, extending work hours, or removing non-working periods.
How Schedule Compression Works
Crashing:
• Focuses on critical path activities that will impact the project end date
• Requires analyzing the cost-time tradeoff for each activity
• Implements the most cost-effective options first
• Example: Adding experienced developers to a coding task
Fast Tracking:
• Identifies activities that can overlap instead of being performed sequentially
• Increases communication requirements and coordination
• Elevates risk of rework if dependencies are violated
• Example: Starting software testing while final modules are still being developed
Implementation Process:
1. Identify the need for schedule compression
2. Analyze the current critical path
3. Evaluate compression options and their impacts
4. Select and implement optimal techniques
5. Monitor performance and adjust as needed
Comparing Crashing and Fast Tracking:
| Aspect | Crashing | Fast Tracking |
|---|
| Cost Impact | Typically increases costs | May not increase direct costs |
| Risk Level | Moderate risk | Higher risk |
| Resource Impact | Requires additional resources | Requires existing resources to work in parallel |
| When to Use | When budget allows for additional resources | When activities can safely overlap |
Exam Tips: Answering Questions on Schedule Compression Techniques1. Know the Key Differences• Be able to clearly distinguish between crashing and fast tracking
• Understand that crashing adds resources and increases costs
• Remember that fast tracking increases risks but may not affect costs
2. Apply Critical Path Analysis• Compression only works meaningfully when applied to critical path activities
• Recognize that compressing non-critical activities only increases float
• Identify when new critical paths emerge after compression
3. Calculate Compression Metrics• Be prepared to calculate crash cost per time unit
• Know how to determine the optimal compression sequence
• Understand diminishing returns in schedule compression
4. Recognize Scenario Applications• Practice identifying which technique is most appropriate for different scenarios
• Consider constraints on time, cost, resources, and risk tolerance
• Look for clues in the question that point to a specific technique
5. Remember the Limitations• Acknowledge that there is always a practical limit to compression
• Understand the quality implications of aggressive compression
• Recognize when compression may be counterproductive
Common Exam Question Types:
• Scenario-based questions asking which technique to apply
• Calculation questions on crash costs and durations
• Questions on the impacts of each technique on project constraints
• Sequence questions on the proper implementation steps
• Analysis questions on how compression affects the network diagram
Sample Question and Analysis:
Question: A project manager needs to reduce the schedule by 2 weeks. Activity A can be crashed at $1,000 per day, saving 5 days. Activity B can be crashed at $1,500 per day, saving 10 days. Both are on the critical path. Which approach is most cost-effective?Analysis:• Activity A: $1,000 × 5 days = $5,000 for 5 days saved = $1,000 per day saved
• Activity B: $1,500 × 10 days = $15,000 for 10 days saved = $1,500 per day saved
• Most cost-effective: Crash Activity A first ($1,000 per day saved) then crash B as needed
By mastering these techniques and practicing with sample questions, you'll be well-prepared to handle schedule compression questions on your PMI-SP exam.