In what scenarios would a fast-tracking vs crashing technique be preferable

Question

When a project is behind schedule, I’ve heard that fast-tracking and crashing can help speed things up. In what situations is one better than the other, and what risks should I watch out for?

Answer 1

Two schedule acceleration techniques, each serving different purposes:

• Fast-Tracking (Rearrange Work to Save Time)

  • Overlaps tasks that were originally sequential.

  • Best for projects with a fixed scope but a flexible schedule.

  • Example: Running electrical and plumbing tasks in parallel instead of sequentially.

  • Risk: Increased coordination challenges, potential rework.

• Crashing (Increase Resources to Speed Up Work)

  • Adds more resources to speed up task completion.

  • Works when budget allows for extra resources, but time is the constraint.

  • Example: Hiring extra developers to accelerate software delivery.

  • Risk: Increased costs, potential burnout, diminishing returns.

• Choosing the Right Approach

  • To save time → Fast-Tracking

  • To speed up work → Crashing

  • Some projects may require a combination of both.