People often compare waterfall vs agile and argue one is better than others. Discussions also happen around simple requirement vs complex requirement and if simple then a waterfall and if complex then use one of the agile approaches. Is it that simple? Is comparing based on requirement type correct? Another argument is about predictive vs empirical and if predictive then waterfall else agile approach. People also do a comparison of a project vs product. If you have a project (often referred to as fixed time and fixed cost) then go for waterfall and if you have a product that is being built based on market reaction then take one of the agile approaches. I don’t see people consider full context and that stumps me. Let’s talk about complex predictive projects such as setting up a disaster recovery system, automation of plant, rolling out SAP HR in 28 multiple countries simultaneously or automating delivery pipeline. Here we have predictive work like setting up a production-like e...
Agilemania is a Bengaluru-based professional Agile and Scrum training provider company. It offers various technical workshops including Test-Driven Development (TDD), Behavior Driven Development (BDD), Agile Testing & Test Automation Framework and DevOps.