Agile is just Waterfall, really?
Waterfall is a wonderful concept. It allows managers to ‘plan’ for problems. Also allows Developers to fix issues before testing has began and testers to possible approve products with bugs. In a nutshell, Waterfall is a little ‘stick to the deadline’ intensive. So, how does Agile relate to Waterfall? Does it relate to Waterfall at all?
Is Agile Waterfall
Waterfall is a form of ‘delivery plan’. The biggest disadvantage to Waterfall is the strict deadline and delivery requirements. Agile tries to remove some of that burden, but how? Well, let’s take a look at the process for Waterfall:
In general, Waterfall consists of Planning, Development and Testing. However, due to the nature of Waterfall, it is more like a cascading effect:
Agile has a number of similar methodologies. The similarity they share with Waterfall include planning, development and testing. Unlike Waterfall, Agile allows you to revisit previous phases. This mean that Agile is just many sets of mini Waterfalls (like so):
Does Agile Share Waterfall’s Pitfalls?
In short, no. You are given the luxury to repeat any phase, re-test, re-deploy in quick cycles. Methods such as Kanban and Scrum inherit the principle development flow of Waterfall but not the strict ‘stick to the time line’ thinking.
Agile Is Mini Waterfall
We can establish that Agile is a set of mini Waterfalls. Every time you pick a task, it requires planning, development and testing. The same process is then repeated for other tasks. Two stories which are picked up can have the same process running. The same processes may run in parallel or sequentially and may or may not impact each other.
Agile is in fact Waterfall, but due to it’s design it does not inherit the ‘fluff’ of Waterfall.