-
Retrospectives happen after the sprint review (but can be delayed if needed) and involve all squad members.
-
The should take 30-60 minutes.
-
The are run by the squad’s scrum master.
-
The purpose of the retrospective is to improve the team's processes.
-
Squads should use Confluence’s Whiteboard - Simple Retrospective Template
-
All squad members get 10 minutes (use inbuilt timer) to add sticky notes to the first three columns:
-
Good
-
Bad / could do better
-
-
Similar sticky’s are then grouped together (team exercise)
-
All squad members get 3 minutes to vote on the most important notes (use stamps). 3x votes each.
-
Team members get 5 minutes to add to the Ideas column. These are ideas to address the most important problems, or to take advantage of the most important good things.
-
Ideas might be a change in process, an escalation, or just something fun to try.
-
-
All squad members get 2 minutes to vode on the most important ideas. 2x votes each.
-
The team then discuss the highest voted ideas, and add them to the actions column if there is a consensus that they should happen. Someone is tasked with implementing the ideas.
-
The whiteboard should be kept as a record of the retrospective.