Document Controls
For Application Development Professionals
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
|
March 22, 2004 Determining Iteration Length In Agile Developmentby Liz Barnett with Carey Schwaber |
|
This is an excerpt
Executive Summary
Today's popular Agile development processes agree that work should be performed in iterations. But these processes do not agree on how long each iteration should last. No one iteration length is right for every organization — or even for every team at a single organization. Application development organizations should use 30 days as a baseline iteration length and then increase or decrease that length depending on the nature of the team and the nature of the project. These factors all concern the nature of the development team and the nature of the work to be performed. Larger teams, distributed teams, and more experienced teams should work in relatively longer iterations, while projects that are complex, smaller in scope, or mission-critical should be performed in shorter iterations.
This is an excerpt
Buy Risk-Free
Price: US $499
Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.
Already a Forrester Client?
Log in to read this document.
