Retrospectives that start with how the team actually feels
Run an anonymous mood check before your retro. See trends across sprints. Give everyone a voice without putting anyone on the spot.
Built-in retrospective formats
Mad / Sad / Glad
Classic retro format. Quick emotional temperature check.
Start / Stop / Continue
Actionable categories for process improvement.
Sailboat
Visual metaphor: wind (helps), anchor (holds back), rocks (risks).
Mood Check
Simple emoji scale from happy to unhappy.
Energy Level
Rate team energy 1 to 5 before diving into discussion.
Why teams use ScrumMastr for retros
Start the retro somewhere other than the board
Most retrospectives open by reviewing the sprint board, and most retrospectives therefore produce observations about the sprint board. That is a shame, because the things worth changing are usually about how people worked rather than which column a ticket sat in. A team that spent two weeks blocked and frustrated will describe that fortnight in terms of ticket flow if that is the only vocabulary the meeting offers.
Opening with an anonymous mood round changes the vocabulary. It takes half a minute, and it puts the actual state of the team in front of everyone before the first person speaks. When the distribution comes back split, the retro has a subject. When it comes back uniformly flat after a sprint everyone called fine, that is worth a conversation too.
Picking a format that fits the sprint you just had
Mad, Sad, Glad works when there is feeling in the room and people need permission to name it. Start, Stop, Continue is the better choice when the team is calm and the goal is concrete process changes. Sailboat suits a sprint that got stuck, because separating what pushed you forward from what held you back tends to surface dependencies and risks that a two-column format flattens.
Rotating formats matters more than picking the perfect one. A team that runs the same retro every fortnight for a year stops thinking and starts filling in the boxes it filled in last time. Changing the shape of the question is the cheapest way to get a different answer.
Making a remote retro produce more than silence
Remote retros fail in a specific way: the facilitator asks an open question, nobody wants to speak first over a video call, and the two most senior people fill the gap. Everyone else agrees with them, because agreeing is what you do when the alternative is interrupting.
Voting first fixes the ordering problem. Everyone submits at the same time, anonymously, and the discussion starts from a distribution that already contains everybody's input. Nobody has to be the person who raises the awkward thing, because the awkward thing is already on the screen. In ScrumMastr this is a link, so people join from a laptop or a phone without an account, an install, or a password reset five minutes before the meeting.
End with one change, not a list of eight
A retro that generates eight action items generates zero, because a list of eight is a way of avoiding a decision. Pick the one change with the clearest owner, write down how you will know in two weeks whether it helped, and let the rest go. If something matters it will come back, and if it does not come back it did not matter.
Then check the next retro against the last one. Running a mood round every sprint gives you a trend line rather than a series of disconnected meetings, which is the difference between a team that retrospects and a team that improves.
Keep reading
Better retros start with honest feelings. Free, anonymous, instant.
Create a room