Iteration Scope Change
The Iteration Scope Change app displays all work items (user stories, defects, and defect suites) that have been added or removed from an iteration, giving a succinct view of whether scope is changing during the course of an iteration.
- View a day-by-day report of work items added or removed from the iteration
- Click a work item name or FormattedID to navigate to the item's detail page
- Filter the report by work added or removed
- Print the report from the App Tools drop-down menu
- Use the Auto Height setting to automatically adjust the vertical space of the app based on the amount of visible data
Interpret app data
Interpreting the report is an important part of the scrum master's role to understand why work is removed or added, and how it is affecting the team's commitments.
For example, scheduling work at the end of the iteration may occur because the team pulled in more work than originally planned; this is a very positive scenario. At the same time, removing work at the end of the iteration may mean the team committed to too much work, and indicates a poor practice. Unfinished work should not be removed from an iteration. Instead, there should be a record of overcommitment so that it may be avoided in future iterations.