A lingering question in many of our minds- When do I follow Waterfall and When do I take the Agile path?
Well, there is no one-size-fits-all – what fits my needs might not fit yours! The traditional Waterfall methodology can still be fit for some programs depending on their conditions.
Now let us look at this with an example.
Say, we are renovating a kitchen. Let us see when we adopt Waterfall versus when we take the Agile path.
When do we go the Waterfall way?
Here are the parameters:
- I know exactly which appliances I need – what brand, dimensions, pattern, also I have already decided on the colors of my cabinets, cooktop, shelves and wall.
- My budget is fixed.
- Now, the work is predictable and the outcome is already known.
- I have received an estimate from my renovation company that it will take 3 months for them to complete the renovation, and I would not be able to use my kitchen until it is ready. And, I am fine with the wait too.
This typically fits very well with Waterfall. It operates in phases – requirements, design, implementation, verification, deployment and maintenance. The requirements are locked at the end of requirements phase, design at the end of design phase and so on. Changes to them cannot be incorporated after being signed-off. So, there is very limited room for innovation and feedback.