Retrospective
A recurring team reflection that examines how work happened, identifies a meaningful improvement, and turns learning into a concrete experiment or action.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/retrospective/
01What 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.[1][2][3]
- 01Set respectful purposeFormat matches current concerns
- 02Gather evidenceOutcomes, flow, quality, collaboration
- 03Find patternsSystem conditions and causes
- 04Choose improvementSmall action with expected effect and owner
- 05Review next timeKeep, change, or stop the experiment
Explore contributing conditions rather than hunt for a person to blame, and review prior commitments at the next retrospective.
02Why 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.
03When 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.
04How it works
- Set a respectful purpose and choose a format appropriate to the team’s current concerns.
- Gather observations and relevant evidence about outcomes, workflow, quality, and collaboration.
- Explore patterns and contributing system conditions rather than hunting for a person to blame.
- Select one or two improvements with meaningful expected effects.
- Assign ownership, define a small experiment or action, and make follow-up visible.
- Review previous commitments at the next retrospective and keep, change, or stop them.
05A 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.
06Where 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.
07Sources
- The Scrum GuideScrum Guides · Official framework guideThe Scrum Guide
- What Is a Retrospective?Agile Alliance · Professional glossaryWhat Is a Retrospective?
- What Are Agile Retrospectives?Atlassian · Established practitioner guideWhat Are Agile Retrospectives?