Any phase · Ways of working
Run a retrospective
A regular session where the team looks at how it is working and agrees one or two improvements. It is how teams get better over time.
About 1-2 hoursEvergreenLast reviewed 5 November 2026
Who this applies to
- Skills it builds
- Delivery and executionLeadership and coaching
- PM types
- All
- Product types
- All
- Starting points
- All
- Ways of working
- All
- Experience
- All
- Size of organisation
- All
Steps, by experience
Beginner (under 1 year)
- Hold it at the end of each sprint or every few weeks.
- Make it safe: what is said stays in the room, and no blame.
- Ask what went well, what did not and what to try.
- Group the ideas and vote on the most important.
- Agree one or two actions with owners.
- Check last time's actions at the start of the next one.
Intermediate (1 to 4 years)
- Vary the format to keep it fresh.
- Agree a small number of actions.
- Follow up actions next time.
Experienced (5+ years)
- Look at patterns across several retrospectives.
- Use data such as cycle time to inform discussion.
- Address team health, not just process.
Who can do this
Owner: Product manager
Can be delegated to
- Scrum Master or Delivery Manager: Facilitate the retrospective
Reviewed by: Scrum Master
Tool examples
- Miro
- Use a retrospective template with sticky notes.
- Confluence
- Use the retrospective page template to record actions.
- Mural
- Run anonymous input then group and vote.
Definition of done
- Held regularly
- One or two actions with owners
- Previous actions reviewed
Common pitfalls
- Too many actions
- Same complaints every time with no change
- The most senior person dominates