Waterfall: great for oversight in theory but that certainty is often just an illusion

Planning upfront, with no surprises, and finishing one thing before moving forward sounds reassuring. That certainty is what most businesses demand of their projects.

But here’s the rub – life isn’t always as predictable as we’d like it to be.

Change is inevitable: needs evolve, markets shift, and new information can emerge that alters your project's landscape.

Which is where the Waterfall model can turn from being supportive to being out-right restrictive. It’s built for a world where the future is clear and change is minimal. Adapting to change is difficult, and expensive.

Structure over speed

The Waterfall model’s strict sequential approach also means that testing, quality assurance and market validation only occur towards the end of the project, when it’s too late to change tack if something is ‘off’. One of Waterfall’s strengths, it’s focus on knowing and documenting everything upfront, is also its weakness. You have to invest a lot of time and effort into that documentation, effort that distracts the project from delivering its end product.

Short predictable projects work well under Agile

Now, you may be thinking, “What if my project is straightforward, predictable, and I know exactly what needs to be done?” Well, in that case, the Waterfall model could be a pretty good fit. If you have small, repeatable projects with limited or predictable change, then Waterfall is great.

Heavy on governance, control and documentation

The Waterfall model provides a clear structure, making it easy to understand and manage while things go to plan. It allows for detailed documentation at every stage, which can be great for historical reference and accountability.

Reassuringly expensive

The Waterfall model, with its structure and predictability, can provide a reassuring framework for managing projects. It’s particularly effective for projects where the requirements are well-known and change is minimal. But, like the lager in the old advert (I’m showing my age here!), that reassurance comes at a price: Waterfall projects tend to take longer and cost more.

Structure or straitjacket?

Waterfall’s structure can become a millstone around your neck when faced with unexpected changes or new information, often leading to increased costs or delays. So, while it might offer the allure certainty, that comes at the cost of being able to adapt to change and requires patience, as the fruits of the project are delivered only at the end.

Next steps - check whether your project is a good fit for Waterfall

Still not sure whether Waterfall is or isn’t the right fit for your project? These nine questions will help you decide.

more insights

TGIF: Think of a Good Idea for the Friday retro

TGIF Or in my world: that moment of panic when you have to quickly Think of a Good Idea for the Friday retro. I have a love/hate relationship with looking back.It’s a constant thing in IT: you hold a retrospective every sprint.But so many teams use it as a moaning shop, whinging but doing nowt about

Read more >

The dark side of Amazon search

I hate Amazon search.It just doesn’t work. You search for a specific thing.And it brings you back related, but unhelpful, other stuff.You can’t even exclude things from the search, like you can on proper search tools. If I need a screen cover for a certain phone, I don’t want to see covers for other phones.If I search

Read more >

Undocumented tomato feature

PSA: reading this post may make you immediately go and check your tomatoes for a little-known feature I’m about to reveal… In hindsight, I was always destined to be a problem-solver.An untangler of knotty problems.A niggler at complex issues. Even when that problem is as commonplace as a tomato. Many moons ago when I was waiting for my

Read more >
Scroll to Top