Do you know what happens at a Sprint Retrospective meeting?

Last updated by Tiago Araújo [SSW] 23 days ago.See history

At the end of every Sprint, the Development Team performs a Sprint Retrospective, also known as the Retro. The Retro provides an opportunity for the Scrum Team to reflect on what has gone well, what has gone poorly, and what the team wants to change.

Inspect-and-adapt is a key component of the Scrum framework and the Retro gives Scrum Teams an opportunity to learn from their successes and mistakes.

The Retro is a time-boxed event that focuses around 3 questions:

  1. What went well?
  2. What didn't go well?
  3. What will we do differently in the next Sprint?

The Scrum Master facilitates the meeting and collects issues as they are raised. Once every Scrum Team Member has spoken, he facilitates debate on each issue so that team consensus is achieved. The result should produce an actionable outcome, for example:

  • An adjustment is made to the daily processes followed by the Scrum Team
  • An adjustment is made to the Definition of Done
  • An adjustment is made at the organization level
  • An item is added to the Product Backlog

To help aid discussion, it can be useful for the Scrum Master to prepare items for review by inspecting the Sprint Backlog and statistics such as:

  • Velocity
  • Burndown
  • Code Coverage
  • Number of deployments
  • Number of errors in Application Insights
  • The Product Roadmap - to see how well the team is doing at achieving the high level strategy.

As an example, the Scrum Master can find PBIs (Product Backlog Items) in the Sprint that were successful/not successful and then facilitate the discussion to find the reasons.

retrospective meeting 1
Figure: The Scrum Master can inspect the Sprint Backlog for items which are "Not Done" at the end of a Sprint

retrospective meeting 2
Figure: The Scrum Master can inspect the team’s velocity over multiple Sprints

retrospective meeting 3
Figure: The Scrum Master can inspect the team’s Sprint Burndown for insight into how work progressed through the Sprint

retrospective meeting 4
Figure: The Scrum Master can inspect the team’s Code Coverage for an insight into code quality

Once all issues have been discussed to the satisfaction of The Scrum Team, the meeting concludes.

If the timebox limit is reached, the remaining issues should be recorded and dealt with by the Scrum Master. Any outstanding issues must be raised at the next Retrospective if they are still relevant.

The timebox for this meeting is usually as many hours as weeks in the Sprint.

Using interactive tools (Apps)

The goal is to make Retro sessions as engaging and insightful as possible. There are 2 main options:

The advantages are:

  • Interactive - app participants can access the board (not one person writing an email, while others watch)
  • Participants can upvote and downvote specific items on the Retro
  • Participants can add items to the board
  • Participants feel more engaged with the process
  • You can leave the board open (if some people have missed the Retro, they can add items afterwards)
  • After you close the board, participants still have access to the Retro and can see what happened

retrospected bad
Figure: Bad example – This is a paste from the tool, but the action points are unclear

retrospected good
Figure: Good example – This is a paste from the tool, but with the modifications at the end, the action points are clear


In Scrum, there are 4 meetings in total that you need to know about:

We open source. Powered by GitHub