Length of an Iteration

In the MSF for Agile Development Process, the first activity of the "Plan an Iteration" work stream is "Determine iteration lenght". The guidance talks about planning an iteration length that "provides just enough time to get a small number of scenarios or quality of service requirements done". Does anyone has an example of how much scenarios this implies? How long should be an iteration for a mid size project of one a couple of months? Does anyone has an aproximate number?

Thanks.

[489 byte] By [JulioCasalT.] at [2008-2-14]

«« Resource Editor: Add/Remove operation is impossible '(null)' is read only
»» XML document error, while accessing .NET webservice.

# 1

It depends on many factors, so a good guess for one situation may not be applicable to another. Three people working closely together on a simple application may determine that a week is adequate, whereas a larger team working on a more complex application may determined that a month or more is needed. Even then, the length of an iteration can vary within the context of a single project.

Essentially, you want to have something to show for your efforts at the end of an iteration that repesents a gain in functionality, performance, or some other aspect. How long it takes to achieve that should guide your determination.

RobCaronMSFT at 2007-9-9 >

Visual Studio Team System

Visual Studio Team System - Microsoft Solutions Framework (MSF)

Visual Studio Team System Hot Topic

Visual Studio Team System New Topic

Visual Studio Team System

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech