Complete firstShared context
Period and goal are set.
Without a frame, contributions are hard to compare.
Method guideAgile
Sprint Retrospective
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityLow
TimeUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
ParticipantsScrum Team
FormatWorkshop
MaturityCanonical
01
Prerequisite
What needs to be finished first
02
Preparation
What needs to be ready before start
Materials
Board, Stickies, Timer
People / roles
The Scrum Master facilitates; Developers, Product Owner, and other Scrum Team members contribute observations; one person records actions.
Pre-read
Collect the Sprint Goal, Sprint Backlog, Increment, Definition of Done, relevant events, and known metrics beforehand.
Time needed
90 minutes
Setup
Explain the safe frame and timebox. Collect observations about people, interactions, processes, tools, and the Definition of Done separately.
03
Core question
The one question this method answers
What affected the quality and effectiveness of the last Sprint, and which change will we inspect next Sprint?
04
Flow
Phases with goal, actions, output and pitfall
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
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.
- 1
Frame
Clarify Sprint and purpose
Goal
Recall the Sprint Goal, period, and conditions for a safe conversation.
Inputs for this step
- Fictional tool-rental context
- Shared observations
Actions
- Recall the Sprint Goal, period, and conditions for a safe conversation.
- Capture the result visibly.
Output
Sprint Goal, period
Sprint Goal, period
Quality check
Is the step concrete, safe, and actionable?
Pitfall
The discussion stays generic or blames people. Return to observable work, effects, and the next check.
Timing: 10–20 minutes
- 2
Inspect
Collect observations
Goal
Collect concrete observations about people, interactions, processes, tools, and the Definition of Done.
Inputs for this step
- Fictional tool-rental context
- Shared observations
Actions
- Collect concrete observations about people, interactions, processes, tools, and the Definition of Done.
- Capture the result visibly.
Output
Observations
Observations
Quality check
Is the step concrete, safe, and actionable?
Pitfall
The discussion stays generic or blames people. Return to observable work, effects, and the next check.
Timing: 10–20 minutes
- 3
Learn
Inspect patterns and causes
Goal
Cluster patterns, ask about conditions, and value multiple perspectives without blame.
Inputs for this step
- Fictional tool-rental context
- Shared observations
Actions
- Cluster patterns, ask about conditions, and value multiple perspectives without blame.
- Capture the result visibly.
Output
Patterns and learnings
Patterns and learnings
Quality check
Is the step concrete, safe, and actionable?
Pitfall
The discussion stays generic or blames people. Return to observable work, effects, and the next check.
Timing: 10–20 minutes
- 4
Improve
Agree improvements
Goal
Choose a few actions for the next Sprint with an owner, Definition of Done, and evidence of effect.
Inputs for this step
- Fictional tool-rental context
- Shared observations
Actions
- Choose a few actions for the next Sprint with an owner, Definition of Done, and evidence of effect.
- Capture the result visibly.
Output
Improvement plan
Improvement plan
Quality check
Is the step concrete, safe, and actionable?
Pitfall
The discussion stays generic or blames people. Return to observable work, effects, and the next check.
Timing: 10–20 minutes
- 5
Follow-up
Agree review and ownership
Goal
Prepare a clear follow-up review.
Inputs for this step
- Selected actions
- Potential effect signals
Actions
- Record an owner, review date and observable signal for each selected action.
- Confirm the agreement and choose where later results will be recorded.
Output
Agreed follow-up plan
Action · owner · review date · signal · record location
Quality check
Are owner, review date and effect signal clearly agreed?
Pitfall
The action is completed but its effect is not inspected. Carry the review date into the next retrospective.
Timing: 5–10 minutes to agree follow-up
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Sprint retrospective record with observed conditions, patterns, a few improvement actions, owners, an action Definition of Done, and a review date in the next Sprint.
Versioning / ownership
Keep date, period, and owner on the artifact.
Tool alternatives
- Whiteboard
- Confluence page
- Miro retrospective board
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
Working board
Observations
...
Patterns
...
Next improvements
...
Working policies
Learning over blame ...
Frame: Clarify Sprint and purpose
Expected artifact: Sprint Goal, period
Sprint Goal, period
Entry:
...
- Is the step concrete, safe, and actionable?
Inspect: Collect observations
Expected artifact: Observations
Observations
Entry:
...
- Is the step concrete, safe, and actionable?
Learn: Inspect patterns and causes
Expected artifact: Patterns and learnings
Patterns and learnings
Entry:
...
- Is the step concrete, safe, and actionable?
Improve: Agree improvements
Expected artifact: Improvement plan
Improvement plan
Entry:
...
- Is the step concrete, safe, and actionable?
Follow-up: Agree review and ownership
Expected artifact: Agreed follow-up plan
Action · owner · review date · signal · record location
Entry:
...
- Are owner, review date and effect signal clearly agreed?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/sprint-retrospective/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
sprint-retrospective-beispiel.md
Concrete filled scenario, fictional example
Fictional Sprint Retrospective: tool rental
Sprint Goal: Enable online return for three device types.
Observation: The Definition of Done was unclear for offline cases. Pattern: Support to Development handoffs lacked an acceptance note. Action: Lea adds an offline checklist by Sprint 12; done means one tested case in review. Check: Inspect questions and rework next Sprint.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Clarify Sprint and purposeThe discussion stays generic or blames people.View in phase
- Collect observationsThe discussion stays generic or blames people.View in phase
- Inspect patterns and causesThe discussion stays generic or blames people.View in phase
- Agree improvementsThe discussion stays generic or blames people.View in phase
- Agree review and ownershipThe action is completed but its effect is not inspected.View in phase
Trap
Clarify Sprint and purpose
Symptom
The discussion stays generic or blames people.
What to do
Return to observable work, effects, and the next check.
Trap
Collect observations
Symptom
The discussion stays generic or blames people.
What to do
Return to observable work, effects, and the next check.
Trap
Inspect patterns and causes
Symptom
The discussion stays generic or blames people.
What to do
Return to observable work, effects, and the next check.
Trap
Agree improvements
Symptom
The discussion stays generic or blames people.
What to do
Return to observable work, effects, and the next check.
Trap
Agree review and ownership
Symptom
The action is completed but its effect is not inspected.
What to do
Carry the review date into the next retrospective.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
The Sprint Goal and concrete observations are traceable.
People, interactions, processes, tools, and the Definition of Done were considered.
A few actions have an owner, done criterion, and check in the next Sprint.
The action is checked for effect in the next Sprint.
The conversation stays focused on work and conditions.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.