The Sprint Retros page is your team's hub to review the data behind how your sprint went. This page can be used as a starting point for discussion about what changes you can make as a team, and help you track whether your changes are making a difference sprint over sprint.
The top of the page provides an overview of how the sprint went with the sprint health and sprint completion scores to dive into the specific data around relevant people and project factors.
It's oftentimes easy to commit to a vague goal at the end of a sprint retro, but difficult to track the trends of tradeoffs being made in other areas to achieve those goals. The health trends sections in the Sprint Retro page can help validate if your team is moving in the right direction in specific areas your team is working on.
Scrolling down the page, we also have sections for Things going Well and Things to Look Into, with drop-downs for a more granular level of the data to discuss as a team. Each section also contains the Retro Reactions submitted by members of your team throughout the course of the sprint or during your team's retro itself.
Retro Reactions
Retro Reactions allow your team to react or comment on any Jira Issue, Subtask, Bug, or PR in Project Explorer for review during your sprint retro (shown below). These reactions help capture important sentiments that often times can be forgotten over the course of a two-week sprint, and specifically vary from comments in Jira because they reflect how your team feels about the work, rather than simply focusing on the details and logistics of the work.
Key Insights provided by Sprint Retro page: