The debate over what development method is better is still being waged. The agile method is not new to Information Technology anymore and has gotten put though he passes in many projects, of varying types, and by many teams worldwide. Since offering a compelling alternative to the stoic waterfall model it is time to ponder the question does agile live up to or even surpass the waterfall method?
In my professional experience working for various organizations in New York I would argue yes. But mine would be an argument based mostly on qualitative results. Today I stumbled upon this quantitative explanation of the agile method’s superiority to the waterfall model.
Also, I am interested to gather the thoughts of Information Technology professionals who lived on both sides of the fence and can offer opinions on this subject.
Tags: agile, development, project management, software, waterfall
Kacalapy's Blog 
January 18, 2009 at 2:26 pm
Be careful… this short presentation quantifies the value of iterative development over long release projects. Though this is normally correlated with agile and waterfall… a good waterfall manager can shorten his release cycle to get similar gains.
You would also need to find something like this to quantify the gains of self-empowered teams, TDD, CI, retrospectives, etc.
I’m only pointing this out because I’ve seen many people say they are doing agile, but after investigation, they are only doing an iterative approach.