Sprint Retrospective Formats

Retrospectives are where teams learn and improve. Good retros surface real issues and create actionable change. Bad retros become repetitive venting sessions that never change anything. This guide covers formats that work.

Retro Formats

Classic Formats

Start/Stop/Continue

START/STOP/CONTINUE
═══════════════════

STRUCTURE:
─────────────────────────────────────
┌────────────────────────────────────┐
│            START                    │
│  What should we start doing?       │
│  ├── Try pair programming          │
│  ├── Daily design reviews          │
│  └── Earlier testing               │
└────────────────────────────────────┘

┌────────────────────────────────────┐
│            STOP                     │
│  What should we stop doing?        │
│  ├── Long meetings                 │
│  ├── Last-minute scope changes     │
│  └── Skipping tests                │
└────────────────────────────────────┘

┌────────────────────────────────────┐
│           CONTINUE                  │
│  What's working well?              │
│  ├── Daily standups                │
│  ├── Code reviews                  │
│  └── Sprint demos                  │
└────────────────────────────────────┘

PROCESS:
─────────────────────────────────────
1. 5 min: Silent writing
2. 5 min: Share START ideas
3. 5 min: Share STOP ideas
4. 5 min: Share CONTINUE items
5. 10 min: Vote and discuss top items
6. Pick 1-2 actions

BEST FOR:
─────────────────────────────────────
├── Quick retros
├── New teams
├── Simple format
├── When time is short
└── Getting started

4Ls Retrospective

4Ls RETROSPECTIVE
═════════════════

STRUCTURE:
─────────────────────────────────────
┌─────────────┐ ┌─────────────┐
│   LIKED     │ │   LEARNED   │
│  ─────────  │ │  ─────────  │
│ What did we │ │ What did we │
│ enjoy?      │ │ learn?      │
│             │ │             │
│ • Teamwork  │ │ • New API   │
│ • On time   │ │ • Testing   │
│ • Quality   │ │   approach  │
└─────────────┘ └─────────────┘

┌─────────────┐ ┌─────────────┐
│   LACKED    │ │ LONGED FOR  │
│  ─────────  │ │  ─────────  │
│ What was    │ │ What do we  │
│ missing?    │ │ wish for?   │
│             │ │             │
│ • Clarity   │ │ • More time │
│ • Resources │ │ • Better    │
│ • Testing   │ │   tools     │
└─────────────┘ └─────────────┘

PROCESS:
─────────────────────────────────────
1. 10 min: Write stickies for each L
2. 15 min: Share and group by theme
3. 10 min: Vote on top issues
4. 20 min: Discuss and create actions
5. 5 min: Assign owners

BEST FOR:
─────────────────────────────────────
├── Comprehensive review
├── Deeper reflection
├── Experienced teams
├── When there's more time
└── Full picture

Mad/Sad/Glad

MAD/SAD/GLAD
════════════

STRUCTURE:
─────────────────────────────────────
┌──────────────────────────────────┐
│  😠 MAD: What frustrated you?    │
│  ├── Blocked for 3 days          │
│  ├── Requirements kept changing  │
│  └── Build broken all week       │
└──────────────────────────────────┘

┌──────────────────────────────────┐
│  😢 SAD: What disappointed you?  │
│  ├── Missed sprint goal          │
│  ├── Bug in production           │
│  └── Team member leaving         │
└──────────────────────────────────┘

┌──────────────────────────────────┐
│  😊 GLAD: What made you happy?   │
│  ├── Feature shipped             │
│  ├── Great collaboration         │
│  └── Customer feedback           │
└──────────────────────────────────┘

PROCESS:
─────────────────────────────────────
1. 5 min: Silent writing
2. 15 min: Share and discuss
3. Focus on MAD items for actions
4. Celebrate GLAD items
5. Create 1-2 actions

BEST FOR:
─────────────────────────────────────
├── Emotional check-in
├── After difficult sprint
├── Building psychological safety
├── Simple and accessible
└── Surfacing feelings

Sailboat

SAILBOAT RETROSPECTIVE
══════════════════════

VISUAL:
─────────────────────────────────────
                    ☀️ ISLAND
                   (Our Goal)
                       
       Wind 💨───────→ ⛵ ←───── ⚓ Anchor
     (Helps us)        │       (Holds back)
                       │
                    🪨 Rocks
                  (Risks ahead)

ELEMENTS:
─────────────────────────────────────
Island (Goal):
├── Where are we trying to go?
├── Sprint goal
├── Quarter objectives
└── Shared destination

Wind (Helping):
├── What's pushing us forward?
├── Good practices
├── Tools that work
├── Momentum
└── Keep doing

Anchor (Holding back):
├── What's slowing us down?
├── Blockers
├── Bad habits
├── Technical debt
└── Address these

Rocks (Risks):
├── What might hurt us?
├── Upcoming risks
├── Dependencies
├── Concerns
└── Mitigate

PROCESS:
─────────────────────────────────────
1. Draw visual on board
2. 10 min: Add stickies to each area
3. 15 min: Discuss themes
4. 10 min: Prioritize anchors/rocks
5. 10 min: Create actions

BEST FOR:
─────────────────────────────────────
├── Visual thinkers
├── Forward-looking teams
├── Strategic discussions
├── Change of pace
└── Fun and engaging

Facilitation Tips

Running Effective Retros

FACILITATION
═════════════

BEFORE:
─────────────────────────────────────
├── Book room/time
├── Prepare materials
├── Review last retro actions
├── Check on team mood
├── Set up space
└── Preparation matters

SILENT WRITING:
─────────────────────────────────────
Why:
├── Introverts participate
├── No anchoring bias
├── More ideas surface
├── Everyone contributes
└── Better input

How:
├── 5-10 minutes
├── Sticky notes or digital
├── No discussion
├── Just write
└── Share after

VOTING:
─────────────────────────────────────
├── Dot voting (3 dots each)
├── Focus discussion
├── Democratic prioritization
├── Quick and fair
└── Team decides focus

TIME-BOXING:
─────────────────────────────────────
├── Strict time limits
├── Move discussion along
├── Don't go too deep on one thing
├── Cover more ground
└── Respect time

ACTIONS:
─────────────────────────────────────
├── 1-3 actions max
├── Specific and actionable
├── Owner assigned
├── Due date set
├── Review next retro
└── Accountability

GitScrum Integration

Tracking Actions

GITSCRUM FOR RETROS
═══════════════════

ACTION ITEMS:
─────────────────────────────────────
├── Create tasks for actions
├── Label: retro-action
├── Assign owner
├── Add to sprint
├── Track completion
└── Visible commitment

NOTEVAULT:
─────────────────────────────────────
├── Document retro notes
├── Record themes discussed
├── Action items logged
├── Historical reference
├── Pattern recognition
└── Retro history

SPRINT REVIEW:
─────────────────────────────────────
├── Check last retro actions
├── Start retro with review
├── Celebrate completed
├── Discuss incomplete
└── Accountability loop

Best Practices

For Retrospectives

1. Silent writing — Everyone contributes
2. Rotate formats — Keep fresh
3. Few actions — Complete them
4. Psychological safety — Honest feedback
5. Review previous — Accountability

Anti-Patterns

RETROSPECTIVE MISTAKES:
✗ Skip retros
✗ Same format always
✗ No silent writing
✗ Too many actions
✗ Never complete actions
✗ Blame individuals
✗ Manager dominates
✗ No follow-through

Related Solutions

• Running effective sprint retrospectives
• Team feedback collection methods
• Tracking improvement from retrospectives