The Agile 'Starfish' Retrospective explained (with Examples)
Are you, as an Agile Coach or Scrum Master, looking for the Starfish Sprint Retrospective or a template for it? Good choice - the starfish retrospective is one of the classics. I’ll be happy to explain how it works.
Sprint Retrospective Starfish
The 5 questions to ask in a starfish retrospective
The first thing you should know about the agile starfish retrospective: it’s called that because typically 5 questions are asked - represented in the form of a starfish. This is what it usually looks like on a digital whiteboard or on paper.
Each of these 5 areas in the retrospective template represents an area of feedback, usually introduced with a word as a heading (and instruction). You can either ask team members to leave feedback on the outside of the star, as the picture indicates - or within the 5 gaps that automatically form in a starfish.
There are the area’s Keep, Stop, Start, More, Less.
- Keep: [Optional: Looking at the last sprint / weeks] What should we keep doing, keep as it is?
- Example: You changed your daily, asking only one question. This produced better results, so you should keep it.
- Stop: What should we stop doing?
- Example: E.g., You were not satisfied with this new tool that is supposed to help you prioritize the product backlog. Let’s stop using it.
- Start: What should we start doing?
- Example: You feel like not everyone feels safe to speak up in your team, psychological safety So you think about implementing a Team health check in 3 steps in your team.
- More: What should we do more of?
- Example: You love that one of your team members actively gives kudos in meeting. We want more of that from everyone in the team!
- Less: What should we do less of?
- Example: It is good to look at agile metrics such as looking at your team’s velocity - but not in every sprint! That’s way too much. We should do it less often, for example only once a quarter in a retrospective.
By the way, you can also find this retrospective in our Echometer Retro Tool (More on this topic: Starfish Retrospective Tool ) and conduct it online with your team without logging in. Simply click on the “Open this retro now” button above to do so.
You may have noticed that the Starfish Sprint Retrospective is quite similar to the “Keep, Stop, Start” retrospective. But it’s not the same - two words are added and there’s a fancy metaphor behind it 😁.
What to be aware of when doing the Sprint Retrospective Starfish
As I mentioned in the last paragraph, this retrospective format has pretty many questions. Most retrospective ideas have 3 questions, this one has 5. So be sure to set a clear timebox!
Depending on how much time you planned for this retrospective, you might even ask everyone to write out their feedback in a way that is understandable. And then let everyone directly vote on the feedbacks so you only have to talk about those things that are prioritized by the team.
Conclusion - Starfish Retrospective
The sprint retrospective starfish is one of many retrospective ideas, one of the classics. If you like it, you will probably also like these 32 kickass retrospectives for beginners and professionals - right?
"Many team members are afraid to speak up!"
Solve this challenge
"We discover too many unexpected issues & bugs at a late stage!"
Solve this challenge
"Why does it sometimes take me hours to prepare a simple retrospective?"
Solve this challenge
