Sprint retrospectives lose their power when they become repetitive. A team that runs the same “What went well / What did not / What to improve” format every two weeks eventually stops generating meaningful insights. The conversations become shallow, the same issues resurface without resolution, and team members disengage. Varying the retrospective format keeps the discussion fresh, surfaces different types of insights, and maintains the team’s investment in continuous improvement.

15 Sprint Retrospective Formats That Teams Actually Enjoy

Classic Formats

1. Start, Stop, Continue

Three columns. What should we start doing? What should we stop doing? What should we continue doing? This format is simple, direct, and works well for new teams or teams new to retrospectives.

Best for: New teams, first retrospective, teams that want actionable outcomes.

2. Mad, Sad, Glad

Team members write items that made them mad (frustrated), sad (disappointed), or glad (happy) during the sprint. The emotional framing often surfaces issues that more analytical formats miss — people share how they felt about events, not just what happened.

Best for: Teams that need to address emotional dynamics, teams recovering from a difficult sprint.

3. Liked, Learned, Lacked, Longed For (4Ls)

Four categories that cover satisfaction (Liked), growth (Learned), gaps (Lacked), and aspirations (Longed For). The “Learned” and “Longed For” categories encourage forward-looking reflection rather than just complaint.

Best for: Teams that want to balance reflection with aspiration.

Metaphor-Based Formats

4. Sailboat

Draw a sailboat on a board. The wind represents things pushing the team forward. The anchor represents things holding the team back. Rocks ahead represent risks. The island on the horizon represents the team’s goal.

Team members add sticky notes to each element. The metaphor makes the exercise feel less clinical and encourages creative thinking about obstacles and opportunities.

Best for: Visual teams, teams that are bored with standard formats, remote teams using Miro.

5. Hot Air Balloon

Similar to the sailboat but with different elements: hot air (what lifts us), sandbags (what weighs us down), storm clouds (risks), and the sun (what energizes us). The additional “sun” element explicitly identifies energy sources, which connects to team burnout prevention.

Best for: Teams experiencing fatigue, teams that want to identify positive energy sources.

6. Speedcar / Race Car

A race car with an engine (what powers us), parachute (what slows us down), and a finish line (our goal). An optional pit crew element represents support from outside the team.

Best for: Teams focused on velocity improvement, competitive team cultures.

Data-Driven Formats

7. Timeline

Create a timeline of the sprint, day by day. Team members add events, decisions, blockers, and emotions to each day. Walking through the sprint chronologically reveals cause-and-effect relationships that topical formats miss: “We were blocked on Monday because of the decision made the previous Friday.”

Best for: Long sprints, complex sprints with many events, teams that want to understand causality.

8. Metrics-Based Review

Start with data: sprint velocity, cycle time, bug count, deployment frequency, and other agile metrics. Discuss what the metrics reveal and what actions could improve them. This format grounds the conversation in objective data rather than subjective feelings.

Best for: Mature teams comfortable with metrics, teams that want evidence-based improvement.

9. Lean Coffee

No predefined agenda. Team members write topics on sticky notes. The group votes on which topics to discuss first. Each topic gets a time-boxed discussion (5 minutes), and the group votes to continue or move on.

Best for: Teams with strong facilitation, teams that want to discuss the most relevant topics rather than following a structure.

Engagement-Boosting Formats

10. Superhero Retrospective

Each team member identifies their “superpower” that helped the sprint and their “kryptonite” that hindered them. The team then discusses how to amplify superpowers and mitigate kryptonite across the group.

Best for: Team building, teams with new members, teams that want to focus on strengths.

11. Newspaper Headlines

Team members write newspaper headlines summarizing the sprint. “Team Ships Feature Ahead of Schedule Despite Third-Party API Outage” or “Sprint Derailed by Unclear Requirements.” The headlines force concise, narrative framing of the sprint’s story.

Best for: Creative teams, teams that enjoy storytelling, remote teams.

12. One Word

Each team member chooses one word that summarizes their sprint experience. The facilitator writes all words on the board, and the team discusses the patterns. “Overwhelmed,” “Chaotic,” and “Rushed” from different team members signal a systemic problem.

Best for: Quick energy check, start of a longer retrospective, teams that struggle to open up.

Action-Oriented Formats

13. Problem-Solve One Thing

Instead of generating a list of issues, the team picks the single biggest problem and spends the entire retrospective solving it. Use a problem-solving framework: define the problem, identify root causes, brainstorm solutions, select the best solution, and assign action items.

Best for: Teams with recurring unresolved issues, teams tired of generating lists that never get addressed.

14. Circles of Control

Draw three concentric circles: Control (things we can change directly), Influence (things we can affect through advocacy), and Concern (things we cannot change). Categorize each issue. Focus action items on the Control circle, advocacy plans on the Influence circle, and acceptance for the Concern circle.

Best for: Teams frustrated by organizational issues they cannot control, teams that need to refocus on what they can change.

15. Starfish

Five categories: Keep doing, More of, Less of, Start doing, Stop doing. More nuanced than Start/Stop/Continue because it includes gradients (“more of” and “less of”) that capture practices the team should adjust rather than completely adopt or abandon.

Best for: Established teams refining their practices, teams that want nuanced feedback.

Facilitation Tips

Rotate the facilitator. When the same person facilitates every retrospective, the format and dynamic calcify. Rotate facilitation among team members or bring in an agile coach periodically.

Silent writing before discussion. Give team members 5-10 minutes to write their thoughts silently before any discussion. This prevents anchoring (the first speaker influencing everyone) and ensures introverted team members contribute equally.

Vote before discussing. When the board is full of items, use dot voting to prioritize. Discuss the top-voted items rather than trying to cover everything.

Limit action items to three. A retrospective that produces ten action items will complete zero. Choose three specific, assignable, time-bound improvements and track them in the next sprint. Check last sprint’s action items at the beginning of each retrospective.

Psychological safety is non-negotiable. If team members do not feel safe being honest, no format will produce useful insights. Working agreements that explicitly state retrospective content stays in the room and that no one is blamed for honest feedback are essential.

Choosing a Format

Match the format to the team’s current need:

Need	Recommended Formats
New team, first retro	Start/Stop/Continue, 4Ls
Team in crisis	Mad/Sad/Glad, Problem-Solve One Thing
Stale retrospectives	Sailboat, Newspaper Headlines, Lean Coffee
Data-driven culture	Metrics-Based, Timeline
Team building focus	Superhero, One Word
Action deficit	Problem-Solve One Thing, Circles of Control