The Five-Step Sprint Retrospective Framework for Agile Teams
The five-step sprint retrospective framework is a structured approach for agile teams to reflect on completed iterations and plan improvements. Created by Esther Derby and Diana Larsen, it consists of five sequential phases: setting the stage, gathering data, generating insights, deciding what to do, and closing the retrospective. Each phase builds on the previous one to transform raw observations into concrete action items that drive continuous improvement.
Overview
The Five-Step Retrospective Framework is the definitive structure for running an effective sprint retrospective. Originally introduced by Esther Derby and Diana Larsen in their landmark book Agile Retrospectives: Making Good Teams Great (2006), this framework gives facilitators a reliable sequence of phases that transforms an open-ended team discussion into a focused, outcome-driven session. Rather than letting retrospectives devolve into venting sessions or passive status updates, the five steps ensure every voice is heard, every observation is grounded in data, and every insight leads to actionable change.
The framework's five phases — Set the Stage, Gather Data, Generate Insights, Decide What to Do, and Close the Retrospective — mirror the natural arc of productive problem-solving. You begin by creating psychological safety, move into evidence-based reflection, synthesize patterns and root causes, commit to specific improvements, and end with a clear sense of closure and accountability. This progression is what separates high-performing agile teams from those that merely go through the motions of a sprint retrospective meeting.
What makes this framework enduring is its flexibility. While the five phases remain constant, the specific activities within each phase can be swapped and customized to keep retrospectives fresh. Teams can use timelines, dot voting, sailboat diagrams, four L's, or dozens of other exercises — all slotted into the appropriate phase. This modularity has made the Five-Step Framework the backbone of virtually every agile sprint retrospective template in use today.
In Hamster Studio, teams can operationalize this framework with AI-powered agents that help facilitate each phase — from prompting the right sprint retrospective questions during data gathering to automatically tracking action items across sprints. The result is retrospectives that consistently deliver measurable improvement, not just cathartic conversation.
How It Works
Step 1: Set the Stage
Open the sprint retrospective by welcoming participants, stating the goal and timebox for the session, and establishing working agreements (e.g., the Retrospective Prime Directive: *Regardless of what we discover, we understand and truly believe that everyone did the best job they could*). Use a brief check-in activity — such as a one-word mood check, ESVP (Explorer, Shopper, Vacationer, Prisoner), or a simple temperature reading — to gauge the room's energy and signal that every voice matters. This phase typically takes 5–10% of the total retrospective time but sets the tone for everything that follows.
Step 2: Gather Data
Build a shared picture of the sprint by collecting objective facts, events, metrics, and subjective experiences. Use techniques like a sprint timeline, Mad/Sad/Glad boards, or a data-driven dashboard review to ensure the team is working from the same factual foundation. Include both hard data (velocity, defect counts, cycle time) and soft data (feelings, energy levels, collaboration quality). This phase typically takes 30–40% of total retrospective time and directly addresses common **sprint retrospective questions** like *What happened?* and *How did it feel?*
Step 3: Generate Insights
Analyze the gathered data to identify patterns, root causes, and connections. Move beyond *what* happened to explore *why* it happened. Techniques include the Five Whys, fishbone (Ishikawa) diagrams, dot voting to surface priority themes, and affinity mapping to cluster related observations. The goal is to transform raw data into actionable understanding. This is the intellectual heart of the **agile retrospective** and typically takes 20–30% of total time.
Step 4: Decide What to Do
Translate insights into concrete, prioritized action items. The team should select a small number of improvements (ideally 1–3) that are specific, achievable within the next sprint, and have clear owners. Use techniques like impact/effort matrices, SMART goal framing, or simple dot voting to prioritize. Each action item should answer: *Who will do what by when?* Avoid overcommitting — a single improvement actually implemented is worth more than five that are forgotten. This phase takes 15–20% of retrospective time and defines the **sprint retrospective format** that drives real change.
Step 5: Close the Retrospective
End the session with intentional closure. Summarize the committed action items, confirm owners and deadlines, and decide how progress will be tracked (e.g., adding items to the next sprint backlog). Then run a brief 'retro of the retro' — ask the team what worked well about this retrospective and what could be improved next time. Express appreciation for participation. This phase takes 5–10% of total time but is essential for accountability and continuous improvement of the retrospective process itself.
When to Use
- At the end of every sprint or iteration as part of the standard Scrum ceremony — the framework provides the structure needed to make the sprint retrospective consistently productive rather than ad-hoc.
- When a team is new to agile and needs a proven, step-by-step format to guide their first retrospective meetings without an experienced facilitator.
- After a significant incident, failed release, or missed commitment where the team needs a structured way to analyze what happened without devolving into blame.
- When retrospectives have become stale or unproductive — the framework's modular activity system lets you reinvigorate the meeting while maintaining structural integrity.
- During team formation or after significant personnel changes, where the 'Set the Stage' phase is especially critical for building trust and establishing norms.
When Not to Use
- When time is extremely constrained (under 15 minutes) and you need a lightweight check-in — the five phases require adequate time to be effective, and rushing through them undermines their purpose.
- For real-time incident response or active crisis situations where immediate action is needed rather than structured reflection — use a post-incident review after the situation is resolved.
- When the team has no authority or organizational support to implement improvements — running retrospectives without the ability to act on outcomes breeds cynicism and disengagement.
- For cross-organizational strategic reviews spanning multiple teams and quarters — the framework is designed for a single team reflecting on a single iteration, not for portfolio-level analysis.
Skills in This Method
Closing Retrospectives Effectively
How to wrap up a retrospective by summarizing decisions, appreciating contributions, and gathering feedback on the retro process itself.
Deciding What to Do: Prioritizing Retrospective Action Items
Methods for helping the team select, prioritize, and commit to specific, actionable improvements they will implement in the next iteration.
Choosing Retrospective Activities and Exercises
How to select and facilitate engaging activities like Sailboat, Mad/Sad/Glad, or Timeline for each phase of the five-step retrospective.
Building Sprint Retrospective Templates
How to design reusable retrospective templates that map activities to each of the five phases for consistent and efficient facilitation.
Tracking Retrospective Action Items Across Sprints
Practices for following up on retrospective commitments, measuring improvement progress, and ensuring accountability between sprint cycles.
Setting the Stage for Effective Retrospectives
How to open a retrospective by establishing a welcoming environment, setting the tone, and defining the session's focus and working agreements.
Generating Insights from Retrospective Data
How to facilitate analysis of gathered data to uncover root causes, patterns, and meaningful insights that go beyond surface-level observations.
Gathering Data During Sprint Retrospectives
Techniques for collecting objective facts, events, metrics, and team sentiments from the past iteration to create a shared understanding of what happened.