Fast-Tracking vs Crashing
People think fast-tracking and crashing are the same trick. Both shorten the critical path. Fast-tracking runs tasks at the same time that were planned one after another, which adds risk. Crashing adds people or money to a task so it ends sooner, which adds cost.
Fast-Tracking
Doing tasks at the same time. Usually they would go one after the other.
Fast-tracking shortens a schedule by doing tasks at the same time that would normally go one after another. For example, building can start before the whole design is done. It costs no extra money at first. But it adds risk, because a late change in one task can force rework in the other. It only works where the link between the tasks is a choice, not a hard rule.
Crashing
Adding people or money to the key tasks. Then they finish sooner.
Crashing shortens a schedule by adding people, money or tools to tasks on the critical path. It keeps the order of the tasks the same. Each day saved costs extra, so you crash the cheapest tasks first. At some point more people stop helping and only add cost. It works best on tasks that can be split between many hands.
In one line
- Fast-Tracking
- Doing tasks at the same time. Usually they would go one after the other.
- Crashing
- Adding people or money to the key tasks. Then they finish sooner.