This page is maintained for older versions of Spira only. The latest documentation can be found at: https://spiradoc.inflectra.com

Spira 4.2 User Manual Help Viewer

1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access
Search:
1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access

2.4. Iteration Planning

As described in section 2.3, in addition to high-level project releases, SpiraTeam® can also track the individual iterations that comprise a release, giving the project manager the option to manage agile methodology projects within the SpiraTeam® environment. Unlike the release planning stage, where high-level requirements are estimated and scheduled, the iteration planning phase involves assigning each of the requirements, incidents and tasks in the project backlog against a specific iteration until the available effort in the iteration has been completely allocated.

When you first create iterations, you specify the start and end-dates together with the notional number of project resources assigned to the iteration and any non-working days. SpiraTeam® uses this information to calculate the planned effort available to the iteration, from which it will subtract the estimated task and incident effort values to determine how much effort is available to schedule.