5 Sprint Retrospective Formats That Actually Work

The Sprint Retrospective is the team's dedicated time to inspect how the last sprint went and to plan improvements for the next one. Done well, it is the single most powerful driver of continuous improvement on a Scrum Team. Done lazily — the same three columns every fortnight — it becomes a ritual people quietly dread.

The fix is variety with purpose. Rotating formats keeps people engaged and surfaces different kinds of insight. Here are five that reliably work.

1. Start, Stop, Continue

The classic for good reason. The team names things to start doing, things to stop doing, and things to continue doing. It is fast, intuitive, and great for newer teams or when you have limited time. The risk is staleness, so reserve it for when you genuinely need speed.

2. Mad, Sad, Glad

This format works on the emotional dimension of the sprint. Team members capture what made them mad, sad, or glad. Because it gives feelings a legitimate place in the conversation, it is excellent after a stressful or chaotic sprint where tension needs an outlet before the team can think clearly about process.

3. The Sailboat

A visual metaphor: the boat is the team, the wind pushes it forward, the anchors hold it back, the rocks are risks ahead, and the island is the goal. Drawing the picture together makes systemic issues visible and is a refreshing change for teams bored of columns. It pairs especially well with longer-horizon thinking.

4. The 4 Ls — Liked, Learned, Lacked, Longed For

A reflective format that balances the positive and the constructive. Liked and Learned celebrate wins and growth, while Lacked and Longed For expose gaps and unmet needs. It is well suited to mature teams capable of honest self-assessment and to milestone moments like the end of a release.

5. Starfish

A more granular cousin of Start, Stop, Continue with five categories: stop, less of, keep, more of, and start. The middle gradations let teams fine-tune practices rather than treating everything as binary. Use it when the team is broadly healthy and wants to optimize at the margins.

Make any format land

The format is only the container. Three habits make a retro actually improve things. First, protect psychological safety so people speak honestly. Second, converge on one or two concrete experiments rather than a long wish list — small, owned, and revisited next sprint. Third, follow through: open each retro by checking what happened to last time's action.

Rotate these five, match the format to the team's current mood and maturity, and your retrospective will stop being a checkbox and start being the place where your team genuinely gets better.