AGILE – WATERFALL: Is this the best Hybrid Model?

Waterfall model is one of the most traditional and earliest SDLC approach that is used for software development. It is also referred to as the Linear – Sequential Life Cycle Model. It gained popularity as it is easy to understand and implement. Waterfall model are generally preferred for small projects where there are no uncertain requirements. Waterfall model may be the best when it comes to small projects with defined and fixed requirements, however, Waterfall Model fails when the requirements changes dynamically in the course of the project. Accommodating change in requirements is difficult under Waterfall Model.

To solve this problem with Waterfall Model, Agile approach comes into picture. Agile needs no explanation, the name in itself is self-explanatory. With Agile, handling changes in requirement is a cake walk. In fact, Agile Model is preferred when the project demands inclusion of new requirements at every stage in the project. Although Agile seems to be a solution to most of the software development problems, it is not a ‘one size fits all’ solution. 

Hybrid models are created to tackle the limitations of choosing a methodology for software development. Hybrid models help to bridge the gap and provide optimum solution. It provides best of both worlds and eliminates the difficulties faced in the base models. Hybrid model does not guarantee to be a problem free methodology but with proper planning and careful monitoring of the processes, its benefits can negate its drawbacks.

Agile – Waterfall Hybrid is one approach that seems to have gained a lot of popularity. It gives you the sturdiness of Waterfall model but also provides flexibility related to dynamic requirements. With any Hybrid model, both sides must understand the boundaries of the framework. Waterfall development must be lenient with regards to fixed expectations for the flexibility and freedom of the Agile world. The Agile method should be creative with a little less freedom when working against a fixed deadline project.

Conclusion: 

The Agile-Waterfall Hybrid mode is not only helpful in retaining clarity that Waterfall model provides but also is determined in accepting the strengths and benefits of the Agile methodology. It is difficult to say whether this is the best hybrid model but if the blend between Agile and Waterfall models is appropriate, all the stakeholders involved in the project will have a happy time.

About Author:

Sachin Poojary is a consultant in Systems Plus Pvt. Ltd. Within Systems Plus, he actively contributes to the areas of Technology and Information Security. He can be contacted at: sachin.poojary@spluspl.com