Retrospective Formats That Energise Your Team
The Sprint Retrospective is one of Scrum's most valuable ceremonies — and one of the most frequently squandered. Run the same format every Sprint and you get the same predictable outputs: a handful of items in each column, a few action points that may or may not be followed up on, and a team that treats the ceremony as an obligation rather than an opportunity. Rotation of formats is not novelty for its own sake. Different formats surface different kinds of insight, and the right format for a team depends on where they are right now.
Why Format Matters
A retrospective format is a structured prompt for collective reflection. The questions it asks — explicitly or implicitly — shape what the team notices and what gets voiced. Start/Stop/Continue asks people to evaluate current practices. A sailboat asks them to think about propulsion and drag. Mad/Sad/Glad asks them to name their emotional experience of the Sprint. Each prompt opens a different window onto team dynamics and process health.
When a format becomes routine, teams answer it on autopilot. The same people raise the same issues, the same issues get actioned the same way, and the retrospective gradually becomes a ritual performance rather than genuine inquiry. Changing the format breaks the script and invites fresh observation.
A Menu of Formats
Start/Stop/Continue — The most widely used retrospective format for good reason: it is clear, fast, and works for almost any team at almost any stage. Participants identify practices they want to start, stop doing, and continue. Best used as a general health check or when you want to generate a broad set of improvement candidates quickly. The risk is that it becomes mechanical — consider pairing it with silent dot voting to surface genuine priorities.
4Ls: Liked, Learned, Lacked, Longed For — Particularly effective for new teams or teams onboarding to a new way of working. "Liked" and "Learned" encourage teams to name what is working before diving into problems. "Lacked" surfaces capability gaps. "Longed For" opens a conversation about aspirations rather than just deficits — which tends to generate more energising action items.
Mad/Sad/Glad — An emotional temperature check. When team health or morale is a concern, naming feelings directly — rather than talking around them in process terms — can unlock conversations that more analytical formats suppress. Facilitators should ensure psychological safety before running this format; it requires more trust than most.
Sailboat / Speedboat — The team imagines themselves on a boat moving toward a destination (the Sprint goal or product vision). Anchors represent things slowing them down; wind in the sails represents what is accelerating them; rocks represent risks ahead. The metaphor keeps the conversation concrete and forward-looking. Especially useful when a team is stuck in complaint mode and needs to reconnect with agency.
Timeline Retrospective — The team collectively reconstructs a timeline of the Sprint, marking significant events, decision points, and emotional peaks and valleys. Particularly effective for longer iterations, after a major incident, or when the team needs to build a shared narrative about a complex Sprint. Time-consuming but yields rich qualitative data.
Lean Coffee — A self-organising discussion format in which participants propose topics, the group votes on priorities, and discussion proceeds in timed rounds, with the group deciding after each round whether to continue or move to the next topic. Lean Coffee is excellent when the team has many potential topics and you want to ensure the most important ones get airtime — rather than having the agenda driven by whoever speaks first.
Practical Facilitation Tips
Regardless of format, a few facilitation principles apply consistently. Timebox each phase — generation, grouping, discussion, and action planning. Ensure that everyone contributes, not just the most vocal team members; silent individual generation before group sharing is one of the most reliable techniques for this. Keep action items small, specific, and owned by named individuals rather than the team as a whole.
Open each retrospective by briefly reviewing action items from the previous one. This creates accountability and signals that retrospective outputs actually matter. If previous action items were not completed, discuss why before generating new ones — otherwise you are adding to a backlog that nobody is managing.
Choosing the Right Format for the Context
New teams benefit from structured formats with explicit prompts — 4Ls or Start/Stop/Continue. Established teams with recurring issues may need something that breaks habitual thinking — try Sailboat or Timeline. Teams experiencing interpersonal tension or morale challenges need a format that creates emotional space — Mad/Sad/Glad, facilitated carefully. Teams with many competing improvement ideas benefit from Lean Coffee's democratic prioritisation.
The Scrum Guide does not prescribe a retrospective format because there is no single right answer. A skilled Scrum Master or facilitator reads the team's current state and selects a format that will surface what most needs to surface — then adapts as the team evolves.
XNM Consulting supports Agile teams and Scrum Masters in building retrospective practices that drive genuine continuous improvement. Learn more about our .