You may be wondering: in what ways does agile differ from the traditional, phase-based and sequential approach of waterfall? Why would an organization want to use adaptive planning techniques rather than predictive ones?
The truth is -- if the work you're doing is simple and can be planned with total accuracy up front -- then you wouldn't need agile. However, most of the work we do is complex, and increasingly so. If what we did were easy, everyone would be doing it, and there would be no competitive advantage. Instead, we are inundated with statistics of high-cost waterfall projects that -- even if they are on time and on budget -- still fail to deliver the promised value back to the organization. Scope is planned in advance, obstructive and costly change processes are put in place, and in the end something is delivered that may have been needed when it was requested, but is no longer relevant based on current market conditions and business realities.
Agile frameworks provide a toolset to help manage change, and deal with ambiguity. It makes transparent and explicit the things that other methodologies only imply:
Reasons for adopting agile: