Wagile – Pronounced “Waa Gee Lee” – Blended Agile and Waterfall

We all hear a lot about Agile being the new and Waterfall being the old approach to software development.

So tongue firmly in cheek I am going to talk about those Agile projects that don’t quite cut off the ties with the old Waterfall.

What is known in the industry as Wagile.

Looking at Agile, we should have user stories for all the functionality required by the business. However sometimes it is just ends up with focus on one part of the functionality being done in  Agile mode while run of the mill ancillary items are handled in a more waterfall model.

I am not going to try and guess all the possible items that could somehow fall out of Agile into Waterfall but I am sure that you can think of a few. Most likely low risk candidates for Wagile is reporting – assuming that someone somewhere has identified all the fields that need to be captured and made available to the reports as part of the initial Agile development portion of the project.

So why does Wagile come about? Not everything can make it in the sprints so to keep the client happy, items are basically snuck in outside of the sprints using the Waterfall approach sometime under the support budget rather than the development budget.

Is this the wrong approach? No approach is wrong if it keeps the customer happy but don’t try to pass off your shop as 100% Agile if your are doing Wagile.

 

Comments

Tell me what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!