Study guide
4.5 The Sprint Retrospective
Certified ScrumMaster CSM
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Agile Foundations, Scrum Theory & Empirical Process Control
1.1 Agile Manifesto & Lean Thinking 1.2 Empirical Process Control 1.3 Complex Adaptive Systems & Cynefin Framework 1.4 Scrum Framework Overview & Core Rules 1.5 Iterative & Incremental Delivery 1.6 Partial Scrum Adoption & Its Consequences
2 Chapter 2: The Five Scrum Values & Cultural Mindset
2.1 Commitment & Focus 2.2 Openness & Respect 2.3 Courage & Ethical Leadership
3 Chapter 3: Scrum Team Accountabilities & Dynamics
3.1 Developers Accountability & Self-Management 3.2 Product Owner Accountability & Business Value 3.3 Scrum Master Accountability & Servant Leadership 3.4 Team Characteristics, Size & Cross-Functionality 3.5 How the Scrum Team Interacts Across a Sprint 3.6 Why Scrum Has No Project Manager
4 Chapter 4: The Five Scrum Events & Timeboxing
4.1 The Sprint Container & Goal Preservation 4.2 Sprint Planning Event 4.3 Daily Scrum Event & Micro-Planning 4.4 The Sprint Review 4.5 The Sprint Retrospective 4.6 Effects of Skipping the Sprint Retrospective 4.7 Choosing a Suitable Sprint Length 4.8 Inspect & Adapt at Every Scrum Event
5 Chapter 5: Scrum Artifacts, Commitments & Definition of Done
5.1 Product Backlog & Product Goal 5.2 Sprint Backlog & Sprint Goal 5.3 Increment & Definition of Done 5.4 Multi-Team DoD & Technical Debt Management 5.5 Product Backlog Refinement 5.6 Product Backlog Item Attributes & Ordering 5.7 Creating & Evolving the Definition of Done
6 Chapter 6: Scrum Master Core Competencies, Servant Leadership & Coaching
6.1 Facilitation & Professional Coaching Techniques 6.2 Removing Impediments & Root Cause Analysis 6.3 Servant Leadership & Organizational Change 6.4 Agile Metrics, Velocity Traps & Scaling Basics 6.5 Development Practices That Protect the Increment 6.6 Serving the Product Owner 6.7 Organizational Design Change from Adopting Scrum
7 Chapter 7: The CSM Test — Format, Logistics & Official Blueprint
7.1 CSM Test Format & Scoring 7.2 Course Prerequisite, Attempts & Renewal 7.3 The Official Learning Objectives Blueprint
4.5 The Sprint Retrospective
Key Takeaways Explain This Topic AI
The Sprint Retrospective is timeboxed to a maximum of 3 hours for a one-month Sprint and concludes the Sprint — it is the last event before the next Sprint begins.
Its purpose is stated plainly in the Scrum Guide: to plan ways to increase quality and effectiveness.
The Scrum Team inspects individuals, interactions, processes, tools, and its Definition of Done — the Definition of Done is explicitly named as an inspection target.
The most impactful improvements are addressed as soon as possible and may be added to the Sprint Backlog for the next Sprint.
Attendance is the Scrum Team only; external managers are not participants, which is what makes candid discussion possible.
Last updated: August 2026
Quick Answer: The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness . Maximum 3 hours for a one-month Sprint. The Scrum Team inspects individuals, interactions, processes, tools, and its Definition of Done . It concludes the Sprint . The most impactful improvements are addressed as soon as possible and may be added to the next Sprint Backlog.
Every other Scrum event improves the product. The Retrospective is the only event that improves the team's ability to produce the product — which is why removing it is the single most damaging ScrumBut, and why the CSM Learning Objectives devote a separate objective to the effects of skipping it.
The Formal Definition
- Attribute Value
- Purpose Plan ways to increase quality and effectiveness
- Maximum timebox 3 hours for a one-month Sprint; usually shorter for shorter Sprints
- Position in the Sprint The final event — it concludes the Sprint
- Attendees The Scrum Team: Developers, Product Owner, Scrum Master
- Inspection targets Individuals, interactions, processes, tools, and the Definition of Done
- Output Identified improvements, the most impactful addressed as soon as possible
Note the phrase "increase quality and effectiveness." Quality comes first in the Scrum Guide's own sentence. A Retrospective that only produces morale actions and never touches the Definition of Done or engineering practice is under-using the event.
What the Scrum Team Actually Inspects
The Scrum Guide names five targets, and "inspected elements often vary with the domain of work":
Individuals — workload, sustainable pace, skills growth, sources of frustration.
Interactions — how the team communicates, how disagreements resolve, how the Product Owner and Developers collaborate on scope.
Processes — refinement, branching and release practice, how work flows and where it queues.
Tools — build pipelines, environments, issue trackers, collaboration tooling.
The Definition of Done — whether the current quality bar is still appropriate, and whether it should be strengthened.
The Guide adds a specific instruction that candidates frequently miss: "Assumptions that led them astray are identified and their origins explored." The Retrospective is not only about what happened, but about the beliefs that produced the decisions.
Structure and Facilitation Techniques
The Scrum Master facilitates, but does not own the conclusions. Common structures:
Technique How It Works Best Used When
Start / Stop / Continue Three columns: practices to adopt, abandon, and keep A quick, reliable default for most Sprints
Sailboat Wind (helping), anchors (holding back), rocks (risks ahead), sun (what is going well) The team needs to surface risks, not just past events
5 Whys Repeatedly ask why to move from symptom to systemic cause One specific failure dominates the Sprint
Timeline / Mad-Sad-Glad Reconstruct the Sprint chronologically and mark emotional peaks Something felt wrong but nobody can name when
Lean coffee Participants generate and dot-vote topics, then timebox each Trust is high and the team knows what it needs to discuss
Varying the format matters less than varying the depth . A team running Start/Stop/Continue for the twentieth Sprint in a row tends to produce the same three tired items; the Scrum Master's job is to notice that pattern and change the lens.
Making Improvements Actually Happen
The most common Retrospective failure is not a bad conversation — it is a good conversation that changes nothing. The Scrum Guide provides the mechanism directly: the most impactful improvements are addressed as soon as possible, and "they may even be added to the Sprint Backlog for the next Sprint."
Practical discipline:
Cap the number of improvements. One or two that actually ship beat eight that do not.
Make them concrete and owned. "Improve communication" is not actionable. "Add a contract test to the payment adapter before any change to it" is.
Put at least the top item in the Sprint Backlog so it competes for real capacity rather than living on a wish list.
Review the previous Sprint's improvement first at the start of the next Retrospective. Nothing enforces follow-through like routine inspection.
Psychological Safety and Who Attends
The Retrospective is an event for the Scrum Team. It is not a performance review, and inviting line managers or executives predictably converts honest reflection into defensive reporting. When a manager asks to attend, the substantive answer is not "the rules forbid it" but "the event only produces value if people can say uncomfortable things about their own work, and an evaluator in the room makes that irrational." Direct such stakeholders to the Sprint Review , where their business input is genuinely wanted.
The Scrum Master should also be alert to the opposite failure: a Retrospective so committed to being "safe" that no one names a real problem. Safety exists so that difficult truths can be spoken, not so they can be avoided.
Real-World CSM Scenario
A team's Retrospectives are pleasant and consistently generate the same complaint — flaky integration tests — which never gets fixed because "there is never capacity."
The Scrum Master reframes the discussion using the team's own data: hours lost to re-running failed builds over the last four Sprints, expressed against the Sprint Goal that was missed as a result. The team then agrees a single concrete improvement — stabilize the three worst tests — and places it in the next Sprint Backlog, where it competes with feature work as a first-class item rather than as unpaid overtime. The Product Owner is present for that trade-off, which is precisely why the Product Owner attends the Retrospective.