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.3. Release Planning

SpiraTeam® provides the ability to track different versions / releases of the application being tested. Each project in the system can be decomposed into an unlimited number of specific project releases, denoted by name and version number. Requirements and Test Cases developed during the design phase can then be assigned to these different releases. When a tester executes a series of test cases, they are able to choose the version of the project being tested and the resulting test run information is then associated with that release.

From a project planning perspective, the releases are the major milestones in the project, which are further sub-divided into iterations which are separate mini-projects with associated project scope and tasks. The project’s requirements are scheduled at a high-level against the releases and the detailed tasks are scheduled against specific iteration within the release.

In addition, all incidents raised during the testing process are associated with this release, allowing the development team to easily determine which version of the project is affected. Finally as the incidents are resolved and verified during the testing phase, the appropriate release can be selected to indicate which release the incident was resolved and/or verified in.