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

13.3.1. Release Backlog – By Iteration

This view is designed to let you see the release backlog organized by iteration / sprint. Each of the iterations defined for the current release is displayed as a heading, with the backlog items displayed in the same column underneath. The backlog items in this view can be either requirements (with associated tasks and test cases) or incidents. This view is commonly called a Scrum board:

You can drag and drop the requirements between the different iterations. If you schedule a requirement for a specific iteration, all the child tasks that have not yet been started, will follow the parent requirement in being associated with the iteration. Once the backlog item has been added to the iteration, the utilized effort for the iteration will increase, and the available effort will decrease by the same amount.

Note: The system will allow you to assign more backlog items to an iteration than it is possible to complete, however this will result in a negative value for ‘available effort’. If this happens, the “Available Effort” value will be displayed in red, and you need to rebalance the items, extend the iteration length or add project personnel resources to the iteration.

Clicking on the Iteration hyperlinks in the headers will switch the planning board into the ‘Iteration Backlog’ view described in section 13.4 below.