Agile, as characterized by the Agile Declaration is a situated of qualities and standards. These qualities might be followed in any procedure, even waterfall. Yes! Waterfall is not the antonym of agile. Waterfall is only one of numerous techniques utilized as a part of programming advancement (ordinarily by non-spry associations/groups).
Order is additionally not an antonym of Agile like Barry Boehm and Richard Turner proposed in their incompetently titled book “Adjusting Agile with Control” (read a survey by Ron Jeffries here).
Agile obliges a significant number of the same fixings that made a lot of people non-light-footed ventures fruitful (the 16.2% the Standish gathering alludes to in this (PDF) occasion of their well-known Confusion report).
So what’s the distinction? You may ask. The contrast is that agile likewise declares a set of values that are not piece of any technique; rather they are values that ought to be connected autonomously of the strategy utilized within any product venture.
What I’m attempting to secure is that, despite the fact that Agilist have a tendency to disdain at the waterfall strategy they – as I would see it – do so not as a result of the system itself, but since of a bigger reason. The Waterfall approach has been utilized by associations that uphold the genuine antonym of Agile (as portrayed by the Qualities and Practices in the Agile Declaration): Summon and-Control.