What is a retrospective?
A retrospective is a short, regular meeting where a team looks back at how it worked over a set period and decides what to change next. It is not about what the team built, but about how it built it: what helped, what got in the way, and what to do differently. Most teams run one at the end of each sprint or every couple of weeks, and it usually takes 30 to 60 minutes.
In plain words
Think of a retrospective like the conversation a sports team has after a match. They do not replay every pass. They ask what worked, what cost them, and what they will train before the next game. A team that skips this keeps making the same mistakes. A team that does it well gets a little better every week.
Why it matters
The point of a retrospective is improvement you can act on, not a vent session. When it works, the team fixes its own problems before they grow, and people feel heard instead of stuck.
- Problems surface early. Small frustrations get named while they are still cheap to fix, instead of building up into burnout or a missed deadline.
- Improvement compounds. One concrete change every two weeks adds up to a noticeably smoother team over a quarter.
- The team owns the solution. Changes the team chose itself stick far better than process handed down from above.
- Trust grows. A regular space to speak openly makes it normal to raise issues, which is the foundation of a healthy team.
How to run one that works
- Look at the period, then pick a few themes. What went well, what did not, and what to try next.
- End with owned actions. Two or three concrete changes with a name attached, not a long wish list nobody follows up on.
- Check last time's actions first. If nothing from the previous retro happened, the meeting becomes theatre and people stop engaging.
Common pitfalls
- No action comes out of it. A retrospective that ends with a list nobody owns or revisits is wasted time. Always close with two or three changes someone is accountable for.
- It turns into blame. The moment it becomes about who failed, people stop being honest. Focus on the system and the process, not on individuals.
- The same issues every time. If the same complaint returns sprint after sprint, the team is talking about it but not fixing it. Escalate it or commit to a real change.
- Skipping it when busy. The weeks you feel too busy for a retrospective are usually the weeks you need it most.
Related articles:
- 7 steps for efficient meetings - Practical rules that keep any team meeting, including a retro, short and useful.
- What is self-management and how does it work? - How teams take ownership of their own way of working.
- Metrics and information over emotions - Bringing data into the conversation so decisions are not just based on feelings.
Want to stay one step ahead?
Don't miss our best insights. No spam, just practical analyses, invitations to exclusive events, and podcast summaries delivered straight to your inbox.