Implementing agile development in a waterfall project

From the developerWorks archives

Liz Hines, Scott Baldwin, Mark Giles, and Juan Peralta

Date archived: November 22, 2016 | First published: July 22, 2009

An application development team on a large project wanted to move to agile development, even though the overall project very much followed a waterfall model. Although there had been discussions to move the entire project to an agile model, the developers decided to use agile development for their piece of the project and fit it within the overall waterfall structure. As a result, the team observed increased quality, improved milestone deliverables, and better development efficiencies. This success enabled them to champion the agile idea across the project, involve more and more stakeholders, and gain support to eventually make all participating teams agile believers. This content is part of the IBM WebSphere Developer Technical Journal.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Business process management, WebSphere, Commerce
ArticleID=415686
ArticleTitle=Implementing agile development in a waterfall project
publish-date=07222009