When a sprint ends, use the Sprint Closure page to review a summary of the sprint, perform a sprint retrospective, and carry over open items to the next sprint.
Open the Release Management > Sprint Closure page, and make sure the correct release, sprint, and team are selected.
What do you want to do?
The dashboard at the top of the page includes the following reports:
|Sprint Backlog Status||A summary of essential statistics regarding the team sprint.|
|Backlog Planning and Delivery||
A summary of the scope changes that occurred throughout the sprint.
Displays the number of user stories planned for the sprint, along with the number of those added, split, broken, or rolled out during the sprint after the sprint baseline was set. Green indicates user stories whose status is Done.
Use the graph to evaluate how well you planned the sprint in advance.
Note: We started collecting information on user story changes within the sprint only in version
|Defect Cumulative Flow Diagram||Displays the flow of the team's defects through the different statuses.|
|Acceptance Tests||A summary of the passed and failed acceptance tests connected to the sprint's user stories.|
For additional retrospective graphs on the sprint planning, open the Dashboard, and select widgets from the Retrospective category.
Ideally, at the end of a sprint all backlog items planned for the sprint should be closed.
Click the Open Items tab located on the right of the page. A grid opens listing the leftover backlog items from the current sprint.
You can edit the backlog items directly in the grid.
Use the following toolbar commands to close the open items:
Roll to Next Sprint Move the selected backlog items to the next sprint. Planning Reassign the selected backlog item to another release, sprint, and team. Split Story
At the end of a sprint, all user stories should be closed. If you invested time in a user story, but not all its tasks and acceptance tests are completed, split the story. Remaining effort and non-passed acceptance tests are moved under a new user story, which you can assign to a future sprint. A link is automatically created between the original user story and the new one.
For further details, see Split a user story.
In the Sprint Closure tab, click .
Agile Manager creates an Excel report listing this sprint's user stories. The Scope Change column indicates which user stories were Planned for this sprint and remained in scope, and which were Added, Rolled out, Split, or Broken.
Note: A week after the A week after the sprint ends, Agile Manager saves the sprint content.
- If you generate the Scope Change report after this point in time, the report compares the saved sprint content with the sprint baseline content.
- If you generate a report before that time, the report compares the current data in the sprint with the sprint baseline content.
For more details, see Sprint Scope Change report.
In the Things that went well and Things to improve boxes, list the team's positive and negative takeaways from the sprint.
If you created a bulleted or numbered list, you can automatically convert the items to action items. Exit the text box to save the text, and click Convert to action item(s).
In the Action Items pane, create a list of the action items that resulted from the sprint retrospective. The action items are specific to the team, but not to the selected sprint.
Optionally, use the Create Backlog Item button to convert selected action items to backlog items for future sprints.