agile is just waterfall

Agile Is Just Waterfall

Reading Time 2 minute

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:

agile is just 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 is just waterfall

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):

agile is just waterfall

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.

Mo

I am a passionate tester, father, husband and gamer. I love to write blogs about Software Testing and generally contribute back to the Software Testing world.

More Posts - Twitter - Facebook

Published by

Mo

I am a passionate tester, father, husband and gamer. I love to write blogs about Software Testing and generally contribute back to the Software Testing world.

  • Good and informative post. As waterfall is a structured software development methodology it is quite rigid, where as agile is known for its flexibility. Anyone using waterfall for development needs to be very clear about the requirements as there is no scope of any change after it starts. And on the other hand agile allows you to change even after the initial planning has been completed.

    • Your absolutely spot on.

      I have worked in both environments and Agile is certainly more easier to work with, handle and firefight issues but most importantly (as you point out) adapt to changes.

      Many thanks for commenting.

      Best,
      Shahin

  • Mary O

    This is really interesting, detailed and informative which i find very helpful. I am learning of this for the first time. Thanks for sharing this.

    • Hi Mary,

      Thanks for commenting. This post was mainly about discussing how one method is being used as a mask for another, in this case Agile for Waterfall.

      Have you used any of these methods?

      Best,

      Shahin

  • PossesstheWorld

    An interesting article, well written although your introduction might need to include something about what Waterfall does for those of us who are learning about testing

    • Hey PossesstheWorld,

      Many thanks for your comment. I think your absolutely right. I will update the post to include a short description of what Waterfall is. Many thanks for the suggestion.

      Thanks,

      Shahin