Hybrid Agile Methodology
This category contains topics associated with a hybrid Agile methodology. There is a big misconception among many people that there is a binary and mutually-exclusive choice between an “Agile” and “Waterfall” approach. That is not the case. It is very possible to blend the principles and practices behind those two approaches to develop a hybrid approach that provides the best of both worlds.
What Is a Hybrid Agile Process?
What is a hybrid Agile Process? Is there such a thing? I’ve seen many articles that position “Agile” and “Waterfall” as two binary and mutually-exclusive alternatives with no middle ground between the two.
Instead of thinking of what people commonly call “Agile and “Waterfall” as individual discrete methodologies, it is more accurate to see it as a continuous spectrum of approaches from heavily plan-driven at one extreme to heavily adaptive at the other extreme like this:
If you think of it in that way, it is much easier to see the possibility for lots of approaches in the middle of that spectrum that blend the right level of plan-driven principles and practices with more adaptive principles and practices to fit a given situation.
How Do You Make a Hybrid Approach Work?
It takes some skill to make a hybrid Agile methodology work successfully and anyone who would literally try to combine an Agile methodology with a Waterfall methodology to create a hybrid methodology is asking for failure. That’s not the way to do it.
It requires a shift in thinking to do it successfully. Instead of thinking about how you might go about mechanically combining an “Agile” development process with a “Waterfall” process, I prefer to think of a hybrid approach as the appropriate blend of an adaptive approach and a plan-driven approach. The words “adaptive” and “plan-driven” convey an entirely different meaning than “Agile” and “Waterfall”.
Please check the articles associated with this category for more detail: