top of page
Center of Applied PM official logo

Crash, Float, and the Delhi Metro: A Beginner's Guide to Scheduling

  • 14 hours ago
  • 2 min read

A project runs late. A senior member addresses the issue with: "Add more people. Finish it faster." So you do. And somehow, the project gets more delayed.


This isn't bad luck. It's what happens when you schedule without understanding two ideas: crash and float.


Let's fix that using one of India's proudest infrastructure stories.


New Delhi Station Airport Express Line - Image Credits NDTV
New Delhi Station Airport Express Line - Image Credits NDTV

The Delhi Metro: A Lesson Hidden in Plain Sight

One of the infrastructure projects that really shone through in India was the Delhi Metro Project under E. Sreedharan and the DMRC. Phase I of the Delhi Metro finished nearly three years ahead of schedule. E. Sreedharan used disciplined scheduling and deliberate resource allocation to pull off what most thought impossible in the public sector.


Two concepts sat at the heart of that precision: float and crashing.


What Is Float?

Float, also called slack, is the breathing room in a schedule. It's how long a task can slip without pushing back the final deadline.


Say laying electrical cables can start on Day 10 or Day 14 without affecting anything downstream. That task has four days of float.


But not every task has it. Tasks with zero float sit on the critical path; the sequence that directly decides when the project ends. Delay one of those, and the whole project moves.

The critical path, once identified, determined the project timeline. The team at DMRC understood this. They identified the critical activities required for completing the project: tunnel boring, station structures, and track laying. And they guarded those timelines fiercely.


Everything else was sequenced around them.


What Is Crashing?

Crashing means deliberately shortening a task by adding resources; more workers, more shifts, more equipment at an extra cost.


The keyword is deliberate.


Crashing without analysing the critical path is just burning money. You might be rushing a task that has three weeks of float. The deadline doesn't move. Your budget does.


If done right, crashing targets critical-path activities, weighs the cost against the time saved, and treats the decision as a trade-off and not a reflex.


Why This Matters for You

With the help of these project management frameworks and terms, you can schedule your project with accurate estimation. Float tells you where you have flexibility. Crashing tells you where to spend when you don't.


If you've ever watched a project speed up in the wrong direction after adding people, you've seen unplanned crashing in action.


That's not theory. That's how a metro gets built ahead of schedule.


There's far more to scheduling than these few terms, and the deeper you go, the more useful it gets.


Schedule your Projects better with the help of our Project Manager's Toolkit

bottom of page