As described in the Scrum Guide, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
The team inspects how the last fortnight went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.
The team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.
Note stakeholders are not normally invited, but we should (maybe monthly) retrospect as a wider group as well. The retro is a relaxed meeting at the end of the week, so food, drink, jokes etc, all welcome.
Attendees
Dev team is mandatory, PO optional, stakeholders not normally invited
Duration
1 hour per sprint or up to 2 hours for special purposes.
Agenda
(prior to meeting) Choose different questions each time to draw out different ideas
- Set the scene and establish psychological safety
- Silent brainstorm
- Group and vote on ideas
- Discuss ideas in order of top votes to least (time permitting)
- Identify actions to improve and add to backlog, DoD, Team Charter etc.