Skip to content
PMPCAPM

Crashing

Crashing is a schedule compression technique in which additional resources are added to critical path activities to reduce their duration at the least additional cost.

Share:

Explanation

Crashing is one of two primary schedule compression techniques. It involves adding resources to activities on the critical path to reduce the project duration. Typical crashing strategies include assigning additional team members to an activity, authorizing overtime, paying for expedited delivery of materials, or using more experienced (and more expensive) resources.

The key principle of crashing is to achieve the maximum schedule compression for the minimum incremental cost. To do this, the project manager analyzes the critical path activities, determines the crash cost per unit of time saved for each activity, and then crashes the activities in order of lowest cost per unit of time saved. Crashing continues until the desired schedule reduction is achieved, no more crashing is possible, or the cost of further crashing exceeds the benefit.

Crashing does not always work. Some activities cannot be shortened by adding resources due to the nature of the work (for example, a task that requires sequential drying or curing time). Adding too many resources can also create diminishing returns or negative effects due to coordination overhead. Crashing always increases cost and may also introduce additional risk.

Key Points

  • Adds resources to critical path activities to reduce duration
  • Always increases project cost
  • Applied to activities with the lowest crash cost per time unit saved first
  • Not all activities can be effectively crashed

Exam Tip

On the exam, crash the critical path activity with the lowest crash cost per unit of time saved first. If the critical path changes after crashing, recalculate.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Resource Leveling

Resource leveling is a resource optimization technique in which adjustments are made to the project schedule to keep resource usage at or below a defined limit, often resulting in a longer project duration.

Resource Smoothing

Resource smoothing is a resource optimization technique that adjusts activities within their available float so that resource requirements do not exceed predefined limits, without changing the project end date.

Burndown Chart

A Burndown Chart is a graphical representation of work remaining versus time in a Sprint or release, showing whether the team is on track to complete the planned work.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Stakeholder Mapping

Stakeholder mapping is the visual representation of stakeholder relationships, influence, interest, or other attributes using grids, matrices, or diagrams to support analysis and engagement planning.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Cost Performance Index (CPI)

Cost Performance Index (CPI) is an EVM efficiency metric that measures cost performance as the ratio of earned value to actual cost: CPI = EV / AC.

Schedule Performance Index (SPI)

Schedule Performance Index (SPI) is an EVM efficiency metric that measures schedule performance as the ratio of earned value to planned value: SPI = EV / PV.

Earned Value Management (EVM)

Earned Value Management (EVM) is a methodology that integrates scope, schedule, and cost data to assess project performance and progress objectively.

Part of

Schedule Management

Study full domain →

Test your knowledge

Practice scenario-based questions on this topic with detailed explanations.