Team Collaboration & Change
Retrospective Canvas
Look back at the last sprint or project, agree what to keep and change, and leave with actions that have owners.
- Time: 45 to 60 min
- With: The team, one facilitator
- You get: Two or three actions the team commits to
How to use this worksheet
- Set the stage: the Prime Directive, "everyone did the best job they could given what they knew".
- Collect what went well and what could improve. Write silently first, then cluster the notes.
- Vote on the one or two topics that matter most. Do not try to fix everything.
- Turn each chosen topic into an action with one owner and a date. Review the actions at the start of the next retrospective.
Practices, events and results worth keeping or repeating.
Prompts and example
Ask yourself
- What made us proud?
- Which habits should we protect?
Example
- Release went smoothly with no rollbacks - Pairing sessions helped the new colleague onboard - Stand-ups finished in 10 minutes
Problems, frustrations and slowdowns. Describe the situation, not the person.
Prompts and example
Ask yourself
- Where did we lose time?
- What surprised us unpleasantly?
- What would we do differently?
Example
- Too many urgent interrupts during the sprint - Acceptance criteria were unclear for two stories - Test environment was down for a day
Concrete, small and owned: what will we do, who, by when?
Prompts and example
Ask yourself
- Is the action small enough to finish in one iteration?
- How will we know it worked?
Example
- Rotate an "interrupt owner" each week (Sam, from Monday) - Add acceptance criteria to the story template (Priya, Wednesday) - Ask platform team for a stable test environment (Alex, Friday)
Before you finish
- No more than three actions.
- Every action has exactly one owner and a date.
- Last retrospective's actions were checked first.
- Nothing here singles out a person.
About retrospectives
Retrospectives are a regular pause where a team inspects how it works and decides how to improve. They are a core ritual in agile frameworks, described in depth by Esther Derby and Diana Larsen.
The value comes from follow-through. A retrospective that ends in a long list nobody owns teaches the team that the meeting is optional.
Recommended reading
Werbung / Ad: Affiliate links. As an Amazon Associate I earn from qualifying purchases at no extra cost to you.
- Agile RetrospectivesEsther Derby & Diana Larsen
The definitive playbook for designing retrospectives that produce real change.
- The Art of Agile DevelopmentJames Shore
Practical agile practices, with retrospectives as the engine of continuous improvement.