My favorite Scrum Retro methodology

Retro is an important Scrum ceremony. It’s the most important part of learning iterations and process improvements.

This article is a part of my Scrum series, see with free links (including to this article):
I like Scrum. The good Scrum.

Sprint Retro

The best way that I’ve seen to gather data and feedback from team members is based on the starfish model:

Image from https://www.scrum-institute.org/Sprint_Retrospective_Meeting.php

… but extended by another dimension: the group scope (who is about?)

Starfish model with group scope

A similar retro is described well at https://www.scrum-institute.org/Sprint_Retrospective_Meeting.php , except the group scopes.

The story

I joined a team, where the tech lead had the Scrum Master role (they was overloaded with the Scrum Master role, see ). The Sprint Retros were so terrible that I asked to be allowed to facilitate the Sprint Retros.

The team was passive on the Sprint Retros at that time: they wanted to get through this meeting with as little effort as possible, because they weren’t really involved. So when I described my favorite methodology as short as possible, I…