Crashing

Crashing – A schedule compression technique used to shorten the project schedule duration for the least additional cost by adding resources to critical path activities. Crashing involves analyzing cost and schedule trade-offs to determine the most cost-effective way to reduce project duration.

Key Characteristics:

• Schedule compression: Reduces project duration by accelerating critical activities
• Resource addition: Involves adding more resources (people, equipment, shifts) to activities
• Cost-time trade-off: Balances schedule reduction against increased costs
• Critical path focus: Targets activities on the critical path for maximum impact
• Selective application: Applied only where cost-effective compression is possible

Crashing Process:

1. Critical Path Analysis:

• Identify critical path: Determine longest sequence of activities determining project duration
• Activity analysis: Examine each critical path activity for crashing potential
• Float assessment: Verify activities have zero float and impact project completion
• Dependency review: Understand activity relationships and constraints
• Resource evaluation: Assess current resource allocation and availability

2. Crash Cost Analysis:

• Normal duration/cost: Baseline activity duration and associated cost
• Crash duration/cost: Minimum possible duration and associated higher cost
• Crash cost calculation: Additional cost required to achieve crash duration
• Cost slope: Cost per unit of time saved (crash cost – normal cost)/(normal time – crash time)
• Feasibility assessment: Determine if activities can actually be crashed

3. Optimization Selection:

• Cost-effectiveness ranking: Order activities by lowest cost per time unit saved
• Sequential crashing: Apply crashing to most cost-effective activities first
• Critical path monitoring: Track changes to critical path as activities are crashed
• Diminishing returns: Recognize when additional crashing becomes uneconomical
• Resource constraints: Consider availability of additional resources needed

Crashing Methods:

Resource Addition:

• Additional personnel: Adding more team members to parallel work streams
• Overtime work: Extending work hours to complete activities faster
• Multiple shifts: Operating around the clock to accelerate progress
• Specialized resources: Bringing in experts or high-skill resources
• Equipment augmentation: Adding machinery or tools to increase capacity

Work Method Changes:

• Process improvement: Implementing more efficient work methods
• Technology enhancement: Using better tools or automation
• Parallel processing: Converting sequential activities to concurrent execution
• Skill upgrading: Training team members for higher productivity
• Workflow optimization: Eliminating bottlenecks and inefficiencies

External Resources:

• Subcontracting: Outsourcing work to external specialists
• Vendor acceleration: Paying suppliers for expedited delivery
• Consultant engagement: Bringing in external expertise
• Equipment rental: Obtaining additional equipment temporarily
• Service providers: Engaging specialized service companies

Crash Cost Calculation:

Basic Formula:

Example Calculation:

• Normal Duration: 10 days, Normal Cost: $50,000
• Crash Duration: 7 days, Crash Cost: $65,000
• Crash Cost per Day = ($65,000 – $50,000) ÷ (10 – 7) = $5,000 per day saved

Cost-Benefit Analysis:

• Time value: Benefit of completing project earlier
• Penalty avoidance: Cost savings from avoiding late delivery penalties
• Opportunity cost: Value of earlier project completion and benefits realization
• Market advantage: Competitive benefits of early completion
• Resource optimization: Better resource utilization across multiple projects

Crashing Limitations:

Technical Constraints:

• Minimum duration limits: Some activities cannot be compressed beyond certain points
• Resource availability: Limited availability of additional qualified resources
• Physical constraints: Space, equipment, or facility limitations
• Quality requirements: Compression may compromise quality standards
• Safety considerations: Accelerated work may increase safety risks

Economic Constraints:

• Budget limitations: Insufficient funds for additional resources
• Cost-effectiveness thresholds: Point where crashing becomes uneconomical
• Resource cost escalation: Exponentially increasing costs for additional resources
• Opportunity costs: Alternative uses for additional budget allocation
• Return on investment: Diminishing returns from schedule compression

Organizational Constraints:

• Team capacity: Limits on team ability to absorb additional resources
• Management bandwidth: Constraints on supervision and coordination capacity
• Communication complexity: Increased coordination challenges with more resources
• Cultural factors: Organizational resistance to intensive work schedules
• Skill requirements: Availability of appropriately skilled additional resources

Crashing vs. Fast Tracking:

Crashing Characteristics:

• Resource addition: Adds more resources to reduce activity duration
• Cost increase: Always results in higher project costs
• Activity focus: Compresses individual activities on critical path
• Risk profile: May increase resource-related risks but maintains activity sequence
• Quality impact: Potential quality risks from accelerated work

Fast Tracking Characteristics:

• Sequence change: Overlaps activities normally done in sequence
• Cost neutral: May not increase direct costs significantly
• Relationship focus: Changes activity dependencies and relationships
• Risk increase: Significantly increases project risk due to rework potential
• Coordination complexity: Requires more complex project coordination

When to Use Each:

• Crashing: When budget allows and activities can be effectively compressed
• Fast tracking: When schedule is critical and rework risks are manageable
• Combined approach: Using both techniques for maximum schedule compression
• Risk tolerance: Choice depends on organization’s risk appetite
• Resource availability: Decision influenced by resource constraints and costs

Crashing Implementation:

Planning Phase:

• Activity assessment: Evaluate all critical path activities for crash potential
• Resource planning: Identify and secure additional resources needed
• Cost budgeting: Allocate additional budget for crashing activities
• Risk assessment: Identify and plan for risks associated with crashing
• Stakeholder communication: Inform stakeholders of crashing plans and implications

Execution Phase:

• Resource deployment: Add resources to selected activities systematically
• Progress monitoring: Track acceleration progress and effectiveness
• Quality control: Maintain quality standards despite accelerated pace
• Coordination management: Manage increased complexity from additional resources
• Performance measurement: Monitor cost and schedule performance continuously

Control Phase:

• Effectiveness evaluation: Assess whether crashing is achieving desired results
• Cost tracking: Monitor actual crash costs against estimates
• Critical path updates: Adjust plans as critical path changes due to crashing
• Resource optimization: Reallocate resources as activities complete
• Lessons learned: Document crashing effectiveness for future projects

Common Crashing Applications:

Construction Projects:

• Additional crews: Adding construction teams to work different areas simultaneously
• Extended hours: Working overtime or multiple shifts
• Equipment augmentation: Bringing in additional heavy equipment
• Subcontractor acceleration: Paying subcontractors for expedited work
• Material expediting: Paying for faster material delivery

Software Development:

• Team expansion: Adding developers to coding activities
• Parallel development: Having multiple teams work on different modules
• Overtime programming: Extended work hours for development team
• External resources: Contracting additional developers or specialists
• Tool enhancement: Investing in better development tools and environments

Manufacturing Projects:

• Production line addition: Setting up additional manufacturing lines
• Shift expansion: Operating additional shifts or extended hours
• Automation investment: Adding automated equipment to increase throughput
• Supplier acceleration: Paying suppliers for expedited component delivery
• Quality team expansion: Adding quality control resources to prevent delays

Best Practices:

Analysis and Planning:

• Thorough assessment: Carefully analyze all critical path activities for crash potential
• Cost-benefit evaluation: Ensure crashing provides positive return on investment
• Resource verification: Confirm availability of additional resources before committing
• Risk consideration: Evaluate and plan for risks associated with crashing
• Stakeholder alignment: Ensure stakeholder support for additional costs

Implementation:

• Phased approach: Implement crashing incrementally to monitor effectiveness
• Quality maintenance: Maintain quality standards despite accelerated schedule
• Communication enhancement: Increase communication frequency with larger teams
• Performance monitoring: Track both cost and schedule performance closely
• Flexibility: Be prepared to adjust crashing approach based on results

Common Pitfalls:

• Indiscriminate crashing: Crashing activities without proper cost-benefit analysis
• Quality compromise: Sacrificing quality for speed leading to rework
• Resource overload: Adding too many resources causing coordination problems
• Inadequate planning: Insufficient preparation for resource integration
• Ignoring constraints: Not considering technical or organizational limitations

Related Terms:

• Fast Tracking: Schedule compression by overlapping sequential activities
• Critical Path: Longest sequence of activities determining project duration
• Schedule Compression: Techniques to reduce project duration
• Resource Leveling: Adjusting resource usage to optimize allocation
• Float: Amount of time an activity can be delayed without affecting project completion
• Critical Path Method (CPM): Scheduling technique for identifying critical activities
• Earned Value Management: Performance measurement integrating cost and schedule
• Resource Optimization: Techniques for efficient resource utilization
• Schedule Baseline: Approved project schedule used for performance measurement
• What-If Analysis: Scenario planning for different schedule compression options

Metrics and Measurement:

• Schedule compression achieved: Actual time saved through crashing
• Cost per time unit: Actual cost for each unit of time saved
• Resource utilization: Efficiency of additional resources deployed
• Quality impact: Effect of crashing on deliverable quality
• Stakeholder satisfaction: Feedback on crashing outcomes and process