Sprint Retrospective Template: 4 Formats × 3 Team Sizes

What this template is for

For agile teams that want more than a printable checklist or a read-only guide. This template gives you a draggable whiteboard where the whole team can capture sticky notes, cluster themes, and vote on action items during a live 60-minute session. Includes 4 proven formats (Start-Stop-Continue, Mad-Sad-Glad, 4L, Sailboat) and time-box guidance from 3-person squads to 30+ person groups.

When to use this template

• Run a bi-weekly sprint retrospective with a scrum team using Start-Stop-Continue.
• Facilitate a first-time retro for a newly formed cross-functional team using 4L.
• Run an emotion-driven session after a tough sprint or conflict using Mad-Sad-Glad.
• Break down complex cross-team dependencies using the Sailboat metaphor.
• Scale the same board to a 30+ person department retrospective with sub-facilitators.
• Track and follow up on action items across multiple sprints in a single document.

How to use it

1. 1Set the stage (5 min): frame the sprint scope; each person describes current state in one sentence.
2. 2Gather data (15 min): everyone writes cards independently and posts them to the correct column.
3. 3Generate insights (20 min): cluster cards, label repeating themes, dot-vote to prioritize.
4. 4Decide what to do (15 min): pick 2–3 action items from top-voted issues; assign owners.
5. 5Close (5 min): each person shares one thing they want to change in the next sprint.

Quick example

Related resources

How it compares to similar tools

Common mistakes to avoid

• Collecting without converging

  Many cards, but no grouping or synthesis; the session ends with a raw list. Fix: force 2 rounds of clustering mid-session — each cluster must be given a label before moving on.

• It turns into a venting session

  The discussion fixates on negative events with no action output. Fix: every negative card must add a 'change we can make' field before it counts as complete.

• Action items with no owner

  Improvements are captured, but nobody executes. Fix: every action item must have owner + next-review date filled in — unassigned actions are intentions, not commitments.

• The loudest voices dominate

  A few people talk continuously; others only supplement. Fix: use 2 minutes of silent writing plus round-robin sharing so everyone contributes equally, regardless of speaking style.

• The board becomes a 'card graveyard'

  The board is left behind after the meeting; by the next retro nobody remembers what was discussed. Fix: in the last 5 minutes, copy action items into a dedicated frame named 'Sprint N Action Items'. Open this board at the start of the next retro and spend 5 minutes reviewing status. CodePic frames support titles, so every sprint's action items can live in a single traceable document.

Frequently asked questions