Agile Facilitation method

Sprint Retrospective

Turns learning from the Sprint into improved quality and effectiveness for the next Sprint.

The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.

Core question

What affected the quality and effectiveness of the last Sprint, and which change will we inspect next Sprint?

Plan session Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: Scrum Team
Time: Up to 3 h for a one-month Sprint

The Scrum Team agrees improvements and examines their effects in the next Sprint.

The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.

Frame
Clarify Sprint and purpose
Recall the Sprint Goal, period, and conditions for a safe conversation.
Inspect
Collect observations
Collect concrete observations about people, interactions, processes, tools, and the Definition of Done.
Learn
Inspect patterns and causes
Cluster patterns, ask about conditions, and value multiple perspectives without blame.
Improve
Agree improvements
Choose a few actions for the next Sprint with an owner, Definition of Done, and evidence of effect.
Follow-up
Agree review and ownership
Close by agreeing who observes which signals and by when. Evaluate actual effects after implementation.

Update when new observations, signals, or effects appear.

A good fit when

Use it at the end of every Sprint in Scrum. It is timeboxed to at most three hours for a one-month Sprint; shorter Sprints are usually shorter.

Ideal for

Scrum teams
Team improvement
Process tuning

Not good for

Roadmap-level decisions
Blame sessions

Outputs

Improvement agreement
Concrete outcomes with an owner, effect signal and agreed review date.

Working board

Fictional example

Structured board with a blank workspace and fictional example view.

Observations

Fictional: offline cases unclear

Definition of Done does not visibly cover returns without network.

Patterns

Fictional: handoffs lack acceptance note

Support and Development repeat questions.

Next improvements

Fictional: add offline checklist

Lea adds and tests one case by Sprint 12.

Learning over blame: Inspect conditions and effects; nobody must disclose personal matters.

The 2020 Scrum Guide

First step

Start with a clear period, goal, and safe frame.

Open the method guide

Good to do first

Engineering

Kanban

Supplies the flow and rule issues that became visible during the sprint.

Where to go next?

Operations

5 Whys

Traces a recurrently named problem back to its root cause.

Delivery

RAID Log

Enters the agreed actions as tracked items.

Deep dive

Purpose

When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.

How it works

It gathers experiences from the cycle, condenses them into recurring themes, and translates them into practical changes. This makes improvement part of the next work rhythm instead of just a look back.

In detail

A Sprint Retrospective holds up because it translates collective experience into concrete learning work and thereby changes the next cycle. Good facilitation keeps the conversation close to observable patterns from the sprint and prevents premature blame or wish lists. Impact only comes once the team distinguishes symptom from cause and genuinely tries out one small behavior change.

Facilitation

Gather a few striking observations from the sprint beforehand so the session doesn't start in a fog of mood. The turning point becomes tangible when individual frustration turns into a recognizable shared pattern. Close with exactly one change, a clear picture of responsibility, and an agreement on what signals its effect in the next sprint.

The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Retrospective Improvement Learning

Sources

The 2020 Scrum Guidescrumguides.orgOfficial Scrum Guide by Schwaber and Sutherland; defines the purpose, focus, and timebox of the Sprint Retrospective.

In playbooks

Turn Retrospective into ImprovementMove from team feeling to prioritized learning points, experiments, and verifiable change.

Artifact templates

Sprint Retrospective: WorksheetPlan purpose, period, and the next work block.

markdown

sprint-retrospective-working-template.md

Plan purpose, period, and the next work block.

Sprint Retrospective: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Whole flow Time: In one session

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: Board, Stickies, Timer
Roles: The Scrum Master facilitates; Developers, Product Owner, and other Scrum Team members contribute observations; one person records actions.
Advance information: Collect the Sprint Goal, Sprint Backlog, Increment, Definition of Done, relevant events, and known metrics beforehand.
Overall time needed: 90 minutes
Setup: Explain the safe frame and timebox. Collect observations about people, interactions, processes, tools, and the Definition of Done separately.

Prepare for the work steps

Frame: Clarify Sprint and purpose

Fictional tool-rental context
Shared observations

Inspect: Collect observations

Fictional tool-rental context
Shared observations

Learn: Inspect patterns and causes

Fictional tool-rental context
Shared observations

Improve: Agree improvements

Fictional tool-rental context
Shared observations

Follow-up: Agree review and ownership

Selected actions
Potential effect signals