The retrospective is Scrum's most underestimated ceremony. Yet when done well, it can transform the entire dynamic of a team. Here's how to approach it differently.
The Scrum retrospective often falls victim to a well-known syndrome: after a few sprints, teams settle into routine. Same questions, same silences, same three post-its. The problem isn't the format — it's the mechanical repetition of a ritual whose purpose has been forgotten.
To breathe life back into your retros, start by varying the format. The classic Keep / Stop / Start is great for getting started, but after six months it's time to move on. Try the 4Ls format (Liked, Learned, Lacked, Longed For) or the Sailboat where the team identifies what propels them forward and what holds them back. These visual metaphors unlock conversation better than abstract columns.
Second lever: selective anonymity. Some frustrations don't get voiced out loud, especially in the presence of management. Tools like FunRetro or Miro allow anonymous feedback collection before discussing together. And don't forget to review actions decided in the previous retrospective — without this follow-up, the exercise loses all credibility.
- Vary the format every sprint
- Start with a quick emotional check-in
- Limit actions to 2-3 maximum, well-defined
- Assign an owner to each action