Raging Waterfall, Just Another Software Development Approach

Raging Waterfall, Just Another Software Development Approach

I am new to Agile and I don’t claim to be an expert on Agile, but I’ve read some articles that made me knowledgeable enough to try out Agile together with a dedicated team. Most of the articles I’ve read work on the basis that the people who are collaborating share the same mindset of delivering software increments fast, but it’s not always the case.

I thought my team and I are the only ones experiencing the dilemma of using Aglie while our counterparts aren’t, only to find out that there are other teams who experience it as well. I also listened to some Agile practitioners’ opinions and have asked the question “how do you become Agile when your collaborators are not?” We even tried to have Agile work while, clearly, our workflow is Waterfall. The struggle was real.

Then one time we sat on a couch during our free time and decided we should have a term we can use to describe our process. Many ideas came out: agile waterfall, white water rapids, raging waterfall. The suggestions were funny!

However, I thought of using the “Raging Waterfall” method and realized we can still apply Agile practices to our current workflow. Because, why not? Although Agile’s advantage is more applicable to projects with rapidly changing requirements, we can find some practices to be useful to any workflow. I read through the Agile principles and it didn’t state how you should apply what and when you should apply it. It only states what is important when becoming Agile – which to prioritize and what to do, regardless of how you do it.

Even if your contracts/deadlines are fixed, you can still do any/all of the following:

  • daily stand-ups to improve the transparency between the team, identify impediments during development and address those before it becomes an even worse bottleneck.
  • weekly retrospectives to reflect and identify what you did right, what you did wrong, and what you can improve helps the team achieve more in the future.
  • face-to-face conversations to get answers to important questions right away.
  • other practices you deem fit to your workflow that is guided by the Agile principles.

Agile is a mindset. A set of principles guide it. Use those principles to your advantage!

Leave a Reply

Your email address will not be published. Required fields are marked *