Project Management

Schedule Compression

last edited by: Keith Emery on Apr 10, 2017 7:14 PM login/register to edit this page

1 Fast tracking
2 Crashing
3 Differences
4 Reference

Fast Tracking and Crashing are used when the project is late and there is a need to bring it back on track, or when you need to shorten the duration of the project.

Reasons for schedule compression

  • Unrealistic schedule plan.
  • Resources were not delivered on time.
  • Unforeseen risks
  • Force Majeure
  • Client changes delivery date
  • Business opportunity or advantage

Fast tracking

After reviewing the Critical Path to identify sequential tasks can be done in parallel, ensure that another path has not become the critical path. Dealing with multiple critical paths increases risk, as it increases the opportunities for delays to creep into the schedule.

Fast tracking does not incur greater expense, in theory, but it does increase the risk of rework, particularly if it means monitoring efforts must be split among several branches.


In this technique, extra resources are allocated to the project in order to deliver earlier. This technique may alter the critical path (or create others). Examples of Crashing include: expanding work schedules, the addition of limiting resources and motivational techniques. A critical path analysis is performed to determine the relative cost and benefit of crashing each activity. Resource allocations are increased for activities with the most efficient schedule compression. Potential risks associated with Crashing are ramp-up times if new workers are on-boarded, fatigue-related mistakes and insufficient monitoring.


Fast tracking vs Crashing

  • Re-planned vs Adding resources
  • No extra cost vs Extra cost
  • Increase risks vs No significant increase in risks



last edited by: Keith Emery on Apr 10, 2017 7:14 PM login/register to edit this page

Reviews (2)

Login/join to subscribe

"If life was fair, Elvis would be alive and all the impersonators would be dead."

- Johnny Carson