(Length: 4 pages)

March 22, 2004

Determining Iteration Length In Agile Development

by Liz Barnett

with Carey Schwaber


Executive Summary (This is a document excerpt)

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.

Buy Risk-Free

Download and print PDF immediately. Price: US $499

Our Money-Back Guarantee: If you are not completely satisfied, return it for a full refund within three weeks of your online purchase.

Already a Forrester Client?
Log in to read this document.

Add to cart

Find Documents In Related Categories

This document falls under the following categories. Click on a link below to find similar documents.

Technology: Application Development, Application Development Processes & Tools
Geography: Asia Pacific, Europe, North America

corner border corner
Ratings and Comments
NOT YET RATED
corner border corner