Sprint Retrospective Techniques | Actionable Insights
Run retrospectives that drive real improvement. GitScrum helps track action items, document outcomes, and build psychological safety for honest feedback.
9 min read
Retrospectives turn experience into improvement. GitScrum helps teams capture retro outcomes and track action items for continuous growth.
Retrospective Formats
Start-Stop-Continue
START-STOP-CONTINUE FORMAT:
┌─────────────────────────────────────────────────────────────┐
│ │
│ Sprint 12 Retrospective │
│ │
│ START (Things to try) │
│ ─────────────────────── │
│ • Daily async updates instead of standups │
│ • Pair programming for complex features │
│ • Design reviews before implementation │
│ │
│ STOP (Things not working) │
│ ────────────────────────── │
│ • Pulling work in mid-sprint │
│ • Skipping code reviews for "quick fixes" │
│ • Long planning meetings (3+ hours) │
│ │
│ CONTINUE (Things working well) │
│ ──────────────────────────────── │
│ • Friday bug fix day │
│ • Clear acceptance criteria on stories │
│ • Technical spikes for unknowns │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ VOTING: Each person gets 3 dots │
│ Discuss top-voted items │
│ Create 2-3 action items │
└─────────────────────────────────────────────────────────────┘
What Went Well - What Didn't - Ideas
4L'S FORMAT:
┌─────────────────────────────────────────────────────────────┐
│ │
│ Sprint 12 Retrospective │
│ │
│ LIKED (What went well) │
│ ─────────────────────── │
│ • Great team collaboration │
│ • Met all sprint commitments │
│ • New hire ramped up quickly │
│ • Clear communication with PO │
│ │
│ LEARNED (What we learned) │
│ ────────────────────────── │
│ • React Query simplifies data fetching │
│ • Need to estimate API work more carefully │
│ • Small PRs get reviewed faster │
│ │
│ LACKED (What was missing) │
│ ────────────────────────── │
│ • Documentation for new service │
│ • QA time before sprint end │
│ • Clear definition of done │
│ │
│ LONGED FOR (What we wish we had) │
│ ──────────────────────────────── │
│ • Automated E2E tests │
│ • Better staging environment │
│ • More refactoring time │
│ │
│ ACTIONS: │
│ 1. Add E2E tests for critical paths │
│ 2. Reserve last day for QA │
│ 3. Create DoD checklist template │
└─────────────────────────────────────────────────────────────┘
Mad-Sad-Glad
MAD-SAD-GLAD FORMAT:
┌─────────────────────────────────────────────────────────────┐
│ │
│ Sprint 12 Retrospective │
│ │
│ 😠 MAD (Frustrations) │
│ ─────────────────────── │
│ • Build breaks multiple times │
│ • Requirements changed mid-sprint │
│ • Blocked waiting for dependencies │
│ │
│ 😢 SAD (Disappointments) │
│ ──────────────────────── │
│ • Didn't finish the dashboard feature │
│ • Had to cut corners on testing │
│ • Less time for learning │
│ │
│ 😊 GLAD (Celebrations) │
│ ──────────────────────── │
│ • Shipped payment feature on time │
│ • Great cross-team collaboration │
│ • Zero production incidents │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ DISCUSSION FOCUS: │
│ │
│ "MAD" items usually have root causes │
│ Ask: "Why did this happen?" │
│ Ask: "What can we do differently?" │
│ │
│ "SAD" items often reflect process gaps │
│ Ask: "What prevented us?" │
│ Ask: "How do we enable this next time?" │
│ │
│ "GLAD" items should be reinforced │
│ Ask: "How do we continue this?" │
│ Ask: "Can we expand on this success?" │
└─────────────────────────────────────────────────────────────┘
Action Items
Creating Actions
ACTIONABLE OUTCOMES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ GOOD ACTION ITEMS: │
│ ────────────────── │
│ ✅ "Add PR size guidelines to contributing doc" │
│ Owner: @dev-alex │
│ Due: Next sprint │
│ │
│ ✅ "Create automated test for login flow" │
│ Owner: @qa-jordan │
│ Due: Sprint 13 │
│ │
│ ✅ "Schedule weekly cross-team sync" │
│ Owner: @sm-pat │
│ Due: This week │
│ │
│ BAD ACTION ITEMS: │
│ ───────────────── │
│ ❌ "Improve communication" │
│ (Too vague, no owner, no due date) │
│ │
│ ❌ "Be more careful with testing" │
│ (Not actionable, no specific change) │
│ │
│ ❌ "Fix all the bugs" │
│ (Too broad, impossible to measure) │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ ACTION ITEM FORMULA: │
│ │
│ [VERB] + [SPECIFIC THING] + [OWNER] + [DUE DATE] │
│ │
│ LIMIT: 2-3 actions per retro │
│ More is overwhelming and won't get done │
└─────────────────────────────────────────────────────────────┘
Tracking Actions
RETRO ACTION TRACKING:
┌─────────────────────────────────────────────────────────────┐
│ │
│ RETRO ACTION BOARD: │
│ │
│ TO DO IN PROGRESS DONE │
│ ─────── ─────────── ──── │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │S13 │ │S12 │ │S11 │ │
│ │Create │ │Add PR │ │Setup │ │
│ │E2E tests │ │guidelines│ │Slack │ │
│ │@qa │ │@alex │ │bot │ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ ┌──────────┐ │
│ │S11 │ │
│ │Reserve │ │
│ │QA day │ │
│ │@team │ │
│ └──────────┘ │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ RETRO REVIEW (First 5 min of each retro): │
│ │
│ "Let's check last sprint's actions:" │
│ │
│ ✅ Setup Slack bot - DONE │
│ Impact: Team gets build notifications │
│ │
│ 🔄 Add PR guidelines - IN PROGRESS │
│ "Will finish this week" │
│ │
│ ❌ Create E2E tests - NOT STARTED │
│ "Why didn't this happen?" │
│ "Do we still want to do this?" │
└─────────────────────────────────────────────────────────────┘
Facilitation
Running the Meeting
RETRO FACILITATION GUIDE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ STRUCTURE (60-90 min): │
│ │
│ 1. OPENING (5 min) │
│ • Set the stage │
│ • Review previous action items │
│ • Remind of safe space norms │
│ │
│ 2. GATHER DATA (15 min) │
│ • Everyone writes on sticky notes │
│ • Silent brainstorming │
│ • Post to board │
│ │
│ 3. GROUP & VOTE (10 min) │
│ • Cluster similar items │
│ • Each person votes (3 dots) │
│ • Identify top items │
│ │
│ 4. DISCUSS (30-45 min) │
│ • Deep dive on top voted items │
│ • Root cause analysis │
│ • Brainstorm solutions │
│ │
│ 5. CREATE ACTIONS (10 min) │
│ • Define 2-3 action items │
│ • Assign owners │
│ • Set due dates │
│ │
│ 6. CLOSE (5 min) │
│ • Summarize decisions │
│ • Thank the team │
│ • Note any follow-ups │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ FACILITATOR TIPS: │
│ │
│ • Stay neutral - don't lead conclusions │
│ • Ensure everyone speaks │
│ • Timebox discussions │
│ • Focus on process, not people │
│ • "What can WE do differently?" │
└─────────────────────────────────────────────────────────────┘
Psychological Safety
CREATING SAFE SPACE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ SAFE RETRO PRINCIPLES: │
│ │
│ PRIME DIRECTIVE: │
│ "Regardless of what we discover, we understand │
│ and believe that everyone did the best job they │
│ could, given what they knew, their skills, and │
│ the resources available." │
│ │
│ ─────────────────────────────────────────────────────────── │
│ │
│ GROUND RULES: │
│ │
│ ✅ Focus on system/process, not individuals │
│ "The process allowed this to happen" │
│ NOT "John caused this bug" │
│ │
│ ✅ Share your perspective, not THE truth │
│ "I felt overwhelmed by..." │
│ NOT "Everyone knows that..." │
│ │
│ ✅ Listen to understand, not to respond │
│ Let people finish │
│ Ask clarifying questions │
│ │
│ ✅ What's said here stays here │
│ Confidentiality builds trust │
│ Share learnings, not stories │
│ │
│ ✅ No "yeah, but..." │
│ Acknowledge before responding │
│ "I hear that, and..." │
│ │
│ IF RETRO FEELS UNSAFE: │
│ • People won't share real issues │
│ • Same superficial feedback each time │
│ • No improvement happens │
└─────────────────────────────────────────────────────────────┘
Recording
Retro Documentation
RETRO SUMMARY TEMPLATE:
┌─────────────────────────────────────────────────────────────┐
│ │
│ RETRO: Sprint 12 Retrospective │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Date: Jan 15, 2025 ││
│ │ Attendees: 6/6 team members ││
│ │ Format: Start-Stop-Continue ││
│ │ ││
│ │ TOP DISCUSSED ITEMS: ││
│ │ ││
│ │ 1. Mid-sprint scope changes (8 votes) ││
│ │ Problem: Requirements changed after planning ││
│ │ Root cause: PO getting late feedback from client ││
│ │ Solution: Earlier client review, change buffer ││
│ │ ││
│ │ 2. Build reliability (6 votes) ││
│ │ Problem: CI failed 4 times this sprint ││
│ │ Root cause: Flaky tests, resource limits ││
│ │ Solution: Fix flaky tests, increase resources ││
│ │ ││
│ │ 3. Cross-team dependencies (5 votes) ││
│ │ Problem: Blocked waiting for Platform team ││
│ │ Root cause: No visibility into their schedule ││
│ │ Solution: Weekly sync with Platform ││
│ │ ││
│ │ ACTION ITEMS: ││
│ │ ☐ Fix top 5 flaky tests (@alex, Sprint 13) ││
│ │ ☐ Add change buffer to sprint capacity (@sm, ongoing) ││
│ │ ☐ Schedule Platform sync (@pm, this week) ││
│ │ ││
│ │ CELEBRATION: ││
│ │ Shipped payment feature with zero bugs! 🎉 ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ STORE: Team wiki, linked from sprint │
│ REVIEW: Check actions next retro │
└─────────────────────────────────────────────────────────────┘