Retrospective roll-up report

About this report

The retrospective roll-up report is a roll up of the results of a sprint’s retrospective. The report may be beneficial to Scrum Masters, team leaders and members, and product owners for reviewing the last sprint and outcomes. This report is generated by selecting a certain sprint.

To navigate to this report:

If you’re using the new navigation:

1. Select Teams in the top navigation bar and select the team you want to view information about.
2. On the sidebar, select Reports in the list of options.
3. Select Retrospective roll-up report; the report displays.

If you’re using the old navigation:

1. Select the Reports icon from the left Nav menu.
2. Start typing the report's name in the Search box.
3. Once found, select the report.
   Note: You can also use the categories on the left to search for the needed reports.

Prerequisites

1. PI must exist in the system and be tied to a program. 
2. Sprints must be created and tied to the PI. 
3. Teams must be created and tied to a sprint. 
4. Retrospective meeting must be held. 

How are report values calculated? 

• Prior Sprint Experiments / Actions is a list of experiments and action items submitted during the previous retrospective meeting and their status: whether the experiment was implemented or not.
• Team Sentiment score is based on the result of the team voting during the retrospective meeting. The question here is “How do you feel about the sprint?” Participants respond using a point scale of 1-5; the total is the sum of all vote values divided by the number of participants voting.
• Team Performance score is based on the result of the team voting during the retrospective meeting. The question here is “How did the team perform?” Participants respond using a point scale of 1-5; the total is the sum of all vote values divided by the number of participants voting.
• Split Stories shows the number of split stories during a sprint, as well as the reasons that the team had to split stories and things the team will do to avoid splits in the future. Split stories are the ones that cannot be finished in the sprint and had to be split into smaller parts for completion in a future sprint.
  • Reasons that the team had to split stories lists the reasons the team members entered for splitting stories.
  • Things the team will do to avoid splits in the future lists the ideas the team members entered on how to avoid splitting stories.
• What Went Well This Sprint lists the things that team members entered for what they felt went well in the sprint.
• What Did Not Go Well This Sprint lists the things that team members entered for what they felt did not go well in the sprint.
• Suggested Experiments / Actions (ranked) lists the ideas that team members wrote on how to improve the workflow, quality of the product, or anything else.
• The Action Plan For Improvement lists the most voted ideas from Suggested Experiments / Actions that may be chosen to be implemented in the future. Participants respond using a point scale of 1-10; the total is the sum of all vote values divided by the number of participants voting on each suggestion.

How to interpret this report

This report provides feedback from the team on how they feel about their last sprint and identifies actions for improvement going forward. This Inspect and Adapt lessons learned practice provides a more comprehensive view of sprint results and the team spirit. It also gives you a valuable feedback from your team members about their sentiment and troubles they may have encountered during the sprint. A list of action items may help prevent the mistakes in the future and improve the quality of work in future sprints.