GuideRolesEventsWorkflow

Scrum Events

Sprint Retrospective

The Sprint Retrospective is where the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and the Definition of Done. It’s the engine of continuous improvement — the most impactful improvements are addressed as soon as possible and may be added to the next Sprint Backlog.

Continuous improvement · Timebox: ≤ 3 hours (1-month Sprint)

Overview

The Sprint Retrospective is where the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and the Definition of Done. It’s the engine of continuous improvement — the most impactful improvements are addressed as soon as possible and may be added to the next Sprint Backlog.

Event Ownership

Owned / Facilitated By
Scrum Master (facilitator and guardian of improvement culture)
Design and facilitate the retrospective using appropriate techniques for the team’s current needs
Create psychological safety — people must feel safe to be honest
Ensure the retrospective produces concrete, actionable improvement items with owners
Track follow-through on previous retrospective commitments
Vary the format to prevent retro fatigue and surface different insights

Who Should Be Present

Entire Scrum Team
All members (Developers, PO, SM) participate equally. Everyone reflects, contributes ideas, and commits to improvement actions
Scrum Master
Facilitates the session, models vulnerability, and ensures action items are concrete and assigned
Product Owner
Participates as a full team member — their perspective on collaboration, priorities, and communication is essential

Preparation Checklist

01Scrum Master: Select a retrospective format appropriate for the team’s current situation
02Scrum Master: Gather Sprint data — velocity, burndown, escaped defects, impediment resolution time — to ground discussions in facts
03Scrum Master: Review previous retrospective action items and their completion status
04Team: Reflect individually on the Sprint before the meeting — what went well, what didn’t, and what they’d change
05Scrum Master: Prepare the facilitation space — boards, sticky notes, timers, or digital equivalents

Facilitation Techniques

Click any technique to expand details and learn when to apply it.

Start, Stop, Continue

Three columns: What should we start doing? What should we stop doing? What should we continue? Simple, effective, and great for newer teams. The ‘stop’ column is often hardest — prompt with ‘What takes time but adds little value?’

Click to expand

4Ls (Liked, Learned, Lacked, Longed For)

Four quadrants that capture both emotional and practical dimensions. ‘Liked’ celebrates wins. ‘Learned’ captures growth. ‘Lacked’ identifies gaps. ‘Longed For’ surfaces aspirations.

Click to expand

Sailboat / Speedboat

A visual metaphor: Wind (what propels us forward), Anchors (what slows us down), Rocks (risks ahead), Island (our goal). Teams place items on the diagram. The visual nature makes abstract dynamics concrete.

Click to expand

1-2-4-All (Liberating Structure)

1 minute of silent individual reflection → 2 minutes in pairs → 4 minutes in groups of four → all-group discussion. This ensures introverted voices are heard and ideas are refined before group discussion.

Click to expand

Dot Voting + Affinity Mapping

After generating items, group similar ones into themes (affinity mapping). Then give each person 3 dot votes to prioritize. This democratically surfaces the team’s top priorities without lengthy debate.

Click to expand

5 Whys Root Cause Analysis

For recurring problems, ask ‘Why?’ five times to drill past symptoms to root causes. Example: ‘Why did we miss the Sprint Goal?’ → ‘Why were stories larger than expected?’ → ‘Why wasn’t complexity identified during refinement?’ and so on.

Click to expand

Timeline Retrospective

Draw a timeline of the Sprint. Team members place events, emotions, and turning points along it. Walk through the timeline together. This surfaces cause-and-effect relationships that topic-based formats miss.

Click to expand

Silent Retrospective

The entire session is conducted in writing on a shared digital board. Team members add sticky notes, react to others’ notes, and vote — all silently. Verbal discussion only happens for the top-voted items at the end.

Click to expand

Tips & Tricks

01
Open with the Prime Directive: ‘Regardless of what we discover, we understand that everyone did the best job they could given what they knew’
02
Always review previous retrospective action items first — if the team never follows through, trust erodes
03
Limit improvement actions to 1–3 per Sprint. Ten action items means zero will get done
04
Every action item needs an owner and a definition of done — ‘improve communication’ is not actionable
05
Vary the format every 2–3 Sprints. The same format produces diminishing returns
06
Use data (velocity, defect rates, cycle time) to supplement gut feelings — data grounds the conversation
07
End on a positive note — acknowledge something the team did well, even in a tough Sprint
08
Use ROTI (Return on Time Invested, 1–5) at the end to gauge if the retrospective itself is valuable

Success Takeaways by Role

What each participant should walk away with when this event is run well.

Developers

Feeling heard; confidence that process pain points will be addressed; shared ownership of improvement actions

Product Owner

Understanding of team dynamics and constraints; alignment on process changes that affect product delivery

Scrum Master

Deep insight into team health; concrete improvement items to track; validation of what coaching is working

The Team

Renewed energy from being heard; 1–3 specific, owned improvement actions for the next Sprint; stronger trust

Cross-Framework Definition
See Sprint Retrospective in the glossary
→