# Retrospective

A recurring team reflection that examines how work happened, identifies a meaningful improvement, and turns learning into a concrete experiment or action.

- Type: practice
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/retrospective/>)

## What it means

A retrospective is a structured opportunity for a team to inspect its collaboration, process, tools, quality, and working conditions, then adapt them. In Scrum, the Sprint Retrospective concludes the Sprint and plans improvements for the next one. Other teams can use the practice at regular intervals or after significant events.

## Why it matters

Delivery systems do not improve merely because problems are noticed. Retrospectives create protected time to compare perspectives, find patterns, and take responsibility for changes within the team’s influence. Repeated small experiments can improve safety, quality, flow, and collaboration while making hidden friction discussable.

## When to use it

Run retrospectives on a predictable cadence, after major releases, or following incidents and organizational changes. The team needs enough psychological safety to speak honestly and enough authority to change something. Use a blameless incident review when detailed technical reconstruction is the primary need.

## How it works

1. Set a respectful purpose and choose a format appropriate to the team’s current concerns.
2. Gather observations and relevant evidence about outcomes, workflow, quality, and collaboration.
3. Explore patterns and contributing system conditions rather than hunting for a person to blame.
4. Select one or two improvements with meaningful expected effects.
5. Assign ownership, define a small experiment or action, and make follow-up visible.
6. Review previous commitments at the next retrospective and keep, change, or stop them.

## A practical example

A mobile team repeatedly discovers accessibility defects late. Its retrospective maps when design and code checks occur, revealing that screen-reader testing waits for release candidates. The team experiments with pairing a designer and engineer on one story per week and adds an accessible-component check to review.

## Where it breaks

A meeting cannot repair unsafe leadership or structural constraints by itself. Repeatedly discussing problems without authority or follow-through creates cynicism. Anonymous collection may surface concerns but can also remove context, and entertaining formats should never replace analysis of actual work and evidence.

## Common mistakes

- Repeating generic prompts without examining data or previous actions.
- Turning the session into blame, complaint collection, or forced positivity.
- Choosing too many improvements to execute meaningfully.
- Keeping systemic obstacles inside the team when escalation is required.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/retrospective/#visualization-retrospective>)

## Sources

1. [The Scrum Guide](<https://scrumguides.org/scrum-guide.html>) — Scrum Guides · Official framework guide
2. [What Is a Retrospective?](<https://agilealliance.org/glossary/heartbeat-retrospective>) — Agile Alliance · Professional glossary
3. [What Are Agile Retrospectives?](<https://www.atlassian.com/agile/scrum/retrospectives>) — Atlassian · Established practitioner guide

## Related topics

- [Scrum](<https://wiki.soroush.uk/topic/scrum/>)
- [Sprint Review](<https://wiki.soroush.uk/topic/sprint-review/>)
- [Continuous Delivery](<https://wiki.soroush.uk/topic/continuous-delivery/>)
