What is Project Crashing?

In project management, "crashing" is a technique used to shorten the total project duration with the least amount of incremental cost. It involves adding additional resources (such as overtime, extra equipment, or more staff) to critical path activities. By understanding the relationship between cost and time, project managers can make informed decisions on which activities to speed up to meet tight deadlines.

How to Use the Project Crashing Calculator

Our calculator simplifies the complex mathematics behind Crashing Slopes. To get started, list your project activities. For each activity, you need four key data points: the Normal Time and Cost, and the Crash Time and Cost. Once you input these, the tool calculates the "Cost Slope" for each activity. The cost slope represents how much it will cost to reduce the activity duration by one unit of time (usually one day).

Understanding the Crash Slope Formula

The core of crashing analysis is the following formula:
Cost Slope = (Crash Cost - Normal Cost) / (Normal Time - Crash Time)

When you have multiple activities on the critical path, you should always crash the activity with the lowest cost slope first. This ensures you are reducing the project timeline at the minimum possible expense. Our calculator automatically identifies these slopes to help you prioritize your budget effectively.

FAQs

Is crashing always beneficial? No. Crashing should only be applied to activities on the Critical Path. Shortening non-critical activities will increase your costs without reducing the project end date.

What is the difference between Crashing and Fast-Tracking? Crashing adds resources to activities to reduce time, which usually increases costs. Fast-tracking involves performing activities in parallel that were originally planned in sequence, which increases risk rather than cost.