Retrospective Tools
Browse our suite of retrospective tools. Select a tool from the tabs below to learn more about how it works and when to use it.
Available Tools
Retro Board
Structured team reflection with sticky notes
What is it?
A dedicated space for the team to reflect on the past iteration and identify actionable improvements.
Why use it?
To foster a culture of continuous improvement, celebrate successes, and address process issues before they compound.
How it works
Create columns like 'What went well', 'What didn't go well', and 'Action Items'. Team members silently write sticky notes for each category, group similar notes, and vote on the most important ones to discuss.
When to use it?
At the end of every sprint or iteration.
Who should attend?
The entire Development Team, Scrum Master, and Product Owner.
Facilitator tips
- 1
Time-box the silent writing phase to 5–8 minutes. Open-ended brainstorming drags and the first few notes start anchoring everyone else.
- 2
Don't allow discussion while notes are being written. Group and vote after reveal — premature discussion collapses independent thinking into groupthink.
- 3
Review action items from the previous retro first. If last sprint's actions were never followed up, address that before adding new ones.
- 4
End with no more than two concrete actions, each with a named owner and a due date. 'We should improve communication' is not an action item.