Secret ingredients to quality software

Do you know what happens at a Sprint Retrospective Meeting?

Last updated by Tiago Ara├║jo [SSW] on 17 Oct 2021 11:36 pm (about 1 month 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:

  • What went well?
  • What didn't go well?
  • 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 organisation 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
  • the Burndown
  • Code Coverage
  • Number of deployments
  • Number of errors in Application Insights

For example the Scrum Master can find PBIs (Product Backlog Items) in the Sprint that were successful / not successful and then facilitate the discussion as to why.

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 to 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 time-box for this meeting is usually as many hours as weeks in the Sprint.

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

Adam CoganAdam Cogan

We open source. Powered by GitHub