What is a Retrospective?
A retrospective (retro) is a recurring team meeting where the team pauses to reflect on their recent work and process. The classic format asks three questions: What went well? What did not go well? What should we change?
Retros are about process improvement, not blame. The goal is to make the team's way of working better over time through small, continuous adjustments.
Why Retrospectives Matter
Teams that never reflect never improve. Without retros, the same problems repeat: deployments break because the testing process is broken, estimates are off because requirements are unclear, handoffs fail because communication channels are wrong.
Retros also build team health. They give everyone a voice, surface frustrations before they fester, and create shared accountability for improvement.
How to Run Effective Retrospectives
Set the stage with a safety check. Ask the team to rate how comfortable they feel speaking honestly (1-5). If the score is low, address psychological safety before diving in.
Use a structured format. The simplest: "Start, Stop, Continue." What should we start doing? Stop doing? Continue doing? Vary the format quarterly to prevent staleness.
Focus on actions, not venting. Each retro should produce 2-3 specific, assigned action items. "Improve communication" is not an action item. "Add a 15-minute sync every Tuesday between design and engineering" is.
Follow up. Start each retro by reviewing action items from the last retro. Did we do them? Did they help? Accountability makes retros meaningful.
Retrospectives in Practice
At Toyota, retrospectives (called "hansei") are a foundational practice. The culture of continuous improvement (kaizen) treats every process failure as a learning opportunity, not a mistake to punish.
Spotify runs retros at multiple levels: squad retros after each sprint, tribe retros quarterly, and company-wide retros annually. Each level produces improvements at the appropriate scope.
Common Pitfalls
- No action items. A retro without action items is just a group therapy session. Pick 2-3 changes and assign owners.
- Same format every time. Teams stop engaging when retros feel repetitive. Rotate formats: timeline, sailboat, 4Ls, starfish.
- Manager-dominated discussion. The most junior team member's perspective is often the most valuable. Ensure everyone speaks.
- Skipping retros when busy. Teams skip retros during crunch time, which is exactly when process improvement matters most.
Related Concepts
Retrospectives are a core Scrum ceremony alongside sprint planning and sprint review. They embody the agile principle of continuous improvement. For post-incident learning, see blameless post-mortems. See also the detailed entry on retros.