Planning Effective Sprint Retrospectives | Retro Guide
Run retrospectives that drive real improvement. Use Start/Stop/Continue and 4Ls formats, track action items, and avoid common anti-patterns in GitScrum.
9 min read
Retrospectives are where teams get better. GitScrum helps capture insights, track action items, and measure improvement over time so your retros lead to real change.
Retrospective Fundamentals
Purpose
WHY RETROSPECTIVES MATTER:
┌─────────────────────────────────────────────────────────────┐
│ │
│ WITHOUT RETROS: │
│ • Same problems repeat │
│ • Frustrations build up │
│ • Good practices aren't captured │
│ • Team doesn't improve together │
│ • Small issues become big problems │
│ │
│ WITH GOOD RETROS: │
│ • Problems surface early │
│ • Team learns from experience │
│ • Wins are celebrated │
│ • Process continuously improves │
│ • Trust builds over time │
│ │
│ THE PRIME DIRECTIVE: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ "Regardless of what we discover, we understand ││
│ │ and truly believe that everyone did the best job ││
│ │ they could, given what they knew at the time, ││
│ │ their skills and abilities, the resources available, ││
│ │ and the situation at hand." ││
│ │ ││
│ │ — Norm Kerth ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ This creates psychological safety for honest feedback │
└─────────────────────────────────────────────────────────────┘
Anti-Patterns
RETRO ANTI-PATTERNS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ ❌ THE BLAME GAME: │
│ "Who's responsible for this failure?" │
│ → People become defensive, hide issues │
│ Fix: Focus on systems, not individuals │
│ │
│ ❌ THE THERAPY SESSION: │
│ 90 minutes of venting, no action items │
│ → Feels good but nothing changes │
│ Fix: Timebox discussion, require actions │
│ │
│ ❌ THE ECHO CHAMBER: │
│ Same people talk, others stay silent │
│ → Missing important perspectives │
│ Fix: Anonymous input, round-robin, smaller groups │
│ │
│ ❌ THE GROUNDHOG DAY: │
│ Same issues raised every sprint │
│ → Action items never get done │
│ Fix: Track actions, hold accountable, follow up │
│ │
│ ❌ THE POSITIVITY ONLY: │
│ Only good things mentioned, real issues ignored │
│ → Problems fester underground │
│ Fix: Explicitly ask for improvements, anonymous input │
│ │
│ ❌ THE SKIP-IT: │
│ "We're too busy for retro this sprint" │
│ → Improvement becomes optional │
│ Fix: Retro is non-negotiable, even if short │
└─────────────────────────────────────────────────────────────┘
Retro Formats
Classic Format
WHAT WENT WELL / WHAT COULD IMPROVE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ DURATION: 45-60 minutes │
│ │
│ PHASE 1: COLLECT (15 min) │
│ Everyone writes on sticky notes (silent) │
│ │
│ WHAT WENT WELL ✅: │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Pair prog │ │ PR reviews │ │ Ship on │ │
│ │ really │ │ faster than │ │ Friday │ │
│ │ helped │ │ before │ │ 🎉 │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
│ │
│ WHAT COULD IMPROVE 🔧: │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Unclear │ │ Too many │ │ Tests │ │
│ │ requirements│ │ meetings │ │ flaky │ │
│ │ on feature X│ │ mid-sprint │ │ │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
│ │
│ PHASE 2: CLUSTER (10 min) │
│ Group similar items together │
│ │
│ PHASE 3: VOTE (5 min) │
│ Each person gets 3 dots to vote on topics │
│ │
│ PHASE 4: DISCUSS (20 min) │
│ Discuss top voted items │
│ │
│ PHASE 5: ACTIONS (10 min) │
│ Create specific action items with owners │
└─────────────────────────────────────────────────────────────┘
Start/Stop/Continue
START STOP CONTINUE FORMAT:
┌─────────────────────────────────────────────────────────────┐
│ │
│ START 🚀 │ STOP 🛑 │
│ Things we should begin │ Things to stop doing │
│ ────────────────────────────┼──────────────────────────── │
│ • Daily async standups │ • 2-hour planning meetings │
│ • Automated deployments │ • Manual testing everything │
│ • Design review before dev │ • Last-minute scope adds │
│ │ │
│ │
│ CONTINUE ✅ │
│ Things working well │
│ ──────────────────────────── │
│ • Pair programming on complex tasks │
│ • Quick PR reviews │
│ • Friday demos │
│ │
│ DISCUSSION QUESTIONS: │
│ • Which "start" has highest impact? │
│ • Which "stop" is easiest to change? │
│ • How do we protect our "continues"? │
│ │
│ ACTION OUTPUT: │
│ Pick 1 from each column to focus on next sprint │
└─────────────────────────────────────────────────────────────┘
4Ls Format
LIKED, LEARNED, LACKED, LONGED FOR:
┌─────────────────────────────────────────────────────────────┐
│ │
│ LIKED 😊 │ LEARNED 📚 │
│ What did we enjoy? │ What did we learn? │
│ ────────────────────────────┼──────────────────────────── │
│ • Team collaboration │ • New testing approach │
│ • Successful launch │ • GraphQL performance tips │
│ • Supportive culture │ • Better estimation │
│ │ │
│ │
│ LACKED 🔍 │ LONGED FOR 🌟 │
│ What was missing? │ What do we wish we had? │
│ ────────────────────────────┼──────────────────────────── │
│ • Clear requirements │ • Better monitoring │
│ • Testing time │ • Automated deploys │
│ • Documentation │ • More pairing time │
│ │
│ GOOD FOR: │
│ • Reflective teams │
│ • Learning-focused culture │
│ • When you want to celebrate AND improve │
│ │
│ PROCESS: │
│ 1. Silent brainstorm (10 min) │
│ 2. Share and discuss (25 min) │
│ 3. Action items (10 min) │
└─────────────────────────────────────────────────────────────┘
Effective Practices
Gathering Input
INCLUSIVE INPUT GATHERING:
┌─────────────────────────────────────────────────────────────┐
│ │
│ PROBLEM: Loud voices dominate, quiet people don't share │
│ │
│ SOLUTIONS: │
│ │
│ SILENT WRITING: │
│ Everyone writes before anyone speaks │
│ → All ideas captured regardless of personality │
│ │
│ ANONYMOUS INPUT: │
│ Use anonymous submission tool │
│ → People share uncomfortable truths │
│ │
│ PRE-RETRO SURVEY: │
│ Collect feedback before the meeting │
│ → More thoughtful responses, saves meeting time │
│ │
│ ROUND ROBIN: │
│ Each person shares one item, go around │
│ → Everyone speaks, can't be dominated │
│ │
│ BREAKOUT GROUPS: │
│ Small groups discuss, then share with full team │
│ → Easier to speak in smaller setting │
│ │
│ FACILITATOR ROTATES: │
│ Different person runs retro each sprint │
│ → Fresh perspectives, shared ownership │
└─────────────────────────────────────────────────────────────┘
Action Items
EFFECTIVE ACTION ITEMS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ ❌ BAD ACTION ITEMS: │
│ • "Improve communication" │
│ • "Write more tests" │
│ • "Be more careful" │
│ │
│ → Vague, no owner, no timeline, unmeasurable │
│ │
│ ✅ GOOD ACTION ITEMS: │
│ │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ ACTION: Set up daily async standup in Slack ││
│ │ OWNER: @alex ││
│ │ DUE: Before next sprint starts ││
│ │ SUCCESS: Team uses it for 2 weeks ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ ACTION: Add integration tests for checkout flow ││
│ │ OWNER: @jordan ││
│ │ DUE: End of next sprint ││
│ │ SUCCESS: Tests running in CI ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ RULES: │
│ • Max 3 action items per retro │
│ • Each has single owner │
│ • Clear deadline │
│ • Measurable success criteria │
│ • Review status next retro │
└─────────────────────────────────────────────────────────────┘
Following Up
RETRO FOLLOW-UP TRACKING:
┌─────────────────────────────────────────────────────────────┐
│ │
│ NEXT RETRO - START BY REVIEWING ACTIONS: │
│ │
│ Previous Sprint Actions: │
│ │
│ ✅ Set up async standup │
│ Owner: @alex | Status: Done │
│ Result: Team loves it, saving 30min/day │
│ │
│ 🔄 Integration tests for checkout │
│ Owner: @jordan | Status: In Progress │
│ Update: 50% done, carrying to next sprint │
│ │
│ ❌ Update deployment docs │
│ Owner: @maria | Status: Not Started │
│ Reason: Got pulled into urgent bug │
│ Decision: Re-prioritize or drop │
│ │
│ TRACKING METRICS: │
│ │
│ Action Completion Rate: │
│ Sprint 20: 2/3 (67%) │
│ Sprint 21: 3/3 (100%) │
│ Sprint 22: 1/3 (33%) ← Address this │
│ Sprint 23: 2/2 (100%) │
│ │
│ IF ACTIONS KEEP NOT GETTING DONE: │
│ • Too many actions? │
│ • Actions too big? │
│ • Not prioritized? │
│ • Wrong owners? │
└─────────────────────────────────────────────────────────────┘
Remote Retros
Virtual Facilitation
REMOTE RETROSPECTIVE TIPS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ TOOLS: │
│ • Digital whiteboard (Miro, Mural, FigJam) │
│ • Video with faces visible │
│ • Timer visible to all │
│ • Anonymous voting │
│ │
│ CHALLENGES & SOLUTIONS: │
│ │
│ Reading the room is hard: │
│ → Use emoji reactions, explicit check-ins │
│ │
│ People talk over each other: │
│ → Raise hand feature, facilitate turn-taking │
│ │
│ Engagement drops: │
│ → Keep it shorter (30-45 min) │
│ → More interactive activities │
│ → Cameras on if possible │
│ │
│ Technical issues: │
│ → Have backup plan │
│ → Test tools before meeting │
│ │
│ ASYNC RETRO OPTION: │
│ 1. Collect feedback async (1-2 days) │
│ 2. Facilitator summarizes themes │
│ 3. Short sync call to discuss and decide (30 min) │
│ 4. Actions recorded and tracked │
│ │
│ Good for: Distributed teams across timezones │
└─────────────────────────────────────────────────────────────┘