Schedule Compression

last edited by: Malcolm Leith on Nov 21, 2016 10:42 AM login/register to edit this page

1 Fast tracking
2 Crashing
3 Differences
4 Reference

Fast tracking and Crashing is use when the project is late and there is a need to bring it back on track, or when you need to shorthen the duration of the project.


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

Fast tracking

After reviewing only the Critical Path to identify what sequential tasks can be done in parallel, be careful with other paths that have tasks that can become critical path too, dealing with two or more critical paths is risky. Fast tracking does not need more budget but it increases the risks and may end up doing rework.


In this technique we add extra resources to the project to deliver earlier, be careful with the creation of more critical paths. Some examples are giving extra time, adding more resources, motivation with rewards. Not all task can be crash, there is a need for a well done analysis. There is a minor risk with getting unskilled resources, it takes sometime for them to settle down in the project. The cost benefits of this activity have to be explored in order to make it a useful technique.


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: Malcolm Leith on Nov 21, 2016 10:42 AM login/register to edit this page

Comments (1)

Login/join to subscribe

"Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats."

- Howard Aiken



Vendor Events

See all Vendor Events