1

Work From End Date

• If the project is date-driven, the end date often impacts iteration length. Create a project plan or use a calendar to determine how much time is available for development.
• Divide the time period into a suitable number of iterations to allow a small number of scenarios, quality of service requirements, or bug fixes to be implemented. Map out the iterations between the start and the end date.

2

Check Scenario Size

• When the first iteration is being planned, recheck the iteration length to be sure that scenarios are not constantly getting unnecessarily split into smaller scenarios due to iteration length. Increase the iteration length, if necessary, to accommodate the actual scenario size.

3

Examine Integration Costs

• Integration is done throughout the iteration as the development tasks are completed. Consider any special needs or costs for integration in the iteration length.

4

Review Iteration Length

• Review the iteration length with the project team. The optimal iteration length provides just enough time to get a small number of scenarios or quality of service requirements done. Each iteration should result in an internal or external release with the additional functionality of the scenarios, quality of service requirements, or bug fixes scheduled for the iteration.

The iteration length is understood and agreed upon by the project team.