What is waterfall project management?
Waterfall is the oldest way of running a project and still the most common in the physical world. You define everything first, then design it, then build it, then test it, then hand it over, and each stage flows into the next like water down a series of ledges. Nothing goes back up. The requirements are frozen before design starts, the design is frozen before production starts, and changing your mind late is expensive by design, because the whole point is that the expensive decisions were made early and cheaply.
The name came from software in the 1970s, where it was described partly as a warning, and it has since become shorthand for any sequential, gated process. Construction, manufacturing and film production have always worked this way under other names. Pre-production, production and post are a waterfall. So is a building. So is a book.
Why it matters
Why waterfall project management matters
It matters because some projects genuinely cannot be iterated. You cannot ship a bridge at eighty percent and patch it. You cannot shoot a film, see what the client thinks and reshoot it every two weeks; the location is gone and the talent is on another job. For work with real, non-reversible costs at the production stage, waterfall is not a legacy habit. It is the only responsible way to spend the money, because it forces the thinking to happen while thinking is cheap.
It also gives clients something they value: a fixed scope, a fixed price and a fixed date, with sign-offs they can see. For a brand running a launch with a date the market already knows, a process that says "approved, locked, in production" is reassuring in a way that "we will see what the sprint produces" is not.
In practice
How waterfall project management works in practice
- 01
The phases are defined up front with deliverables and approvals at each gate. In creative production that looks like: brief and scope agreed, concept presented and approved, pre-production (script, boards, casting, locations, schedule, budget) approved, shoot, offline edit approved, finishing (grade, sound, graphics) approved, delivery. Each gate is a document somebody signs, and each signature is a promise not to reopen what it covers.
- 02
The project manager's job is to protect the sequence. That means getting every stakeholder into the early phases, when a change costs an email, so that nobody appears in the late phases, when a change costs a reshoot. It means documenting decisions so that the person who approved the board is the person who sees the edit. And it means a change-control process for the cases where something really must move, with the cost and the schedule impact made visible before the decision.
- 03
Most agencies run a hybrid in practice. The strategy and concept phases can be loose and iterative, with ideas tested and thrown away; the moment the shoot is booked the project becomes a waterfall, because from there every change has a hard cost. Knowing where that line sits is most of the skill.
- 04
A gate is only a gate if the approval is specific. The sign-off names the exact artifact (the board version, the script draft, the budget revision) and attaches it, so there is no later debate about which one was approved. It names who had authority to sign, and it lists what is now locked. Silence is never approval. Before each gate, a short look-ahead confirms the next phase can actually open: crew held, locations confirmed, the client's calendar cleared for the review.
At RIOT
Waterfall project management at RIOT
Film production is a waterfall whether anyone calls it that, and as a creative agency and production studio we run it as one: concept approved, boards approved, shoot, edit, finish. We built Krova, our production software, around that sequence, because the tools made for software sprints never quite fit a process where a shoot day cannot be repeated.
Watch out
What people get wrong about waterfall project management
Treating it as the opposite of agile, as if one were modern and the other obsolete. They solve different problems: agile for work that can be released and improved in small pieces, waterfall for work with an irreversible production step. The other mistake is running waterfall without real gates. A process where the client approves the storyboard and then rewrites the script after the shoot is not waterfall; it is chaos with a Gantt chart.
