Sprint Retrospective
The engine of continuous improvement.
1Purpose of the Retrospective
The Sprint Retrospective is where the Scrum Team inspects itself—how it worked together—and creates a plan for improvement.
Key points:
- Timebox: Maximum 3 hours for a one-month Sprint (90 min for 2-week)
- Attendees: Scrum Team only (no stakeholders)
- Output: Actionable improvements, ideally added to the Sprint Backlog
This is the heart of continuous improvement. Skip it, and you stop getting better.
The Most Important Event
Many argue the Retrospective is the most important Scrum event. It's the primary mechanism for the team to adapt their process. Everything else can be fixed here.
2What to Inspect
The Retrospective examines three areas:
People: How well did we work together? Communication? Collaboration?
Processes: Are our practices serving us? Standups, planning, refinement?
Tools: Are our tools helping or hindering? CI/CD, communication tools?
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."
This mindset creates psychological safety for honest reflection.
3Formats That Work
Start/Stop/Continue: What should we start doing? Stop doing? Keep doing?
Mad/Sad/Glad: What frustrated us? What disappointed? What made us happy?
4Ls: What did we Like? Learn? Lack? Long for?
Sailboat: Wind (what pushes us forward), Anchors (what holds us back), Rocks (risks ahead), Sun (what we're aiming for).
Timeline: Walk through the Sprint chronologically. Where did things go well or poorly?
Rotate formats: The same format every Sprint gets stale. Mix it up.
4Making Improvements Stick
The biggest failure mode: identifying improvements but not acting on them.
Make improvements specific: Not "communicate better" but "pair program on complex items for the first hour."
Add to Sprint Backlog: Treat process improvements as Sprint work with time allocated.
Limit improvements: Pick 1-2 to focus on. Don't try to fix everything.
Review last Sprint's improvements: Did we do them? Did they help?
Action Item Graveyard
If your retro action items consistently go undone, you're wasting the Retrospective. Either make them smaller, prioritize them in the Sprint, or address why they're not happening.
- Retrospectives inspect people, processes, and tools
- The Prime Directive creates safety for honesty
- Rotate formats to keep it fresh
- Improvements must become Sprint work or they won't happen
- •Same format every Sprint leads to boredom
- •Blaming individuals violates the Prime Directive
- •Too many action items means none get done
- •Skipping when 'too busy' kills the improvement engine