Sprint Retrospective

Description

At the end of each sprint the team reflects on what went well and what could improve, votes on actions and commits to a few process changes.

The retrospective applies routine course correction to the team's own process rather than to the product. The product manager makes sure it happens and is facilitated, either running it or participating closely if a scrum master or product owner runs it. Team members prepare by reflecting on two questions, what went well and what could be improved, and propose specific actions. A shared board, physical or in a tool, lets people pre-populate items, comment and vote. The facilitator keeps discussion blame-free, reinforces what worked and makes room to explore setbacks; proposed actions are voted on, prioritised and given owners. Crumlish advises against calling it a postmortem. The same reflect-and-iterate approach can be applied to working agreements between product and UX.

Attributes

Loss type
Active
Effort
Hours

Steps

  1. Schedule a retrospective at the end of every sprint, typically 45 to 90 minutes, and decide who facilitates.
  2. Ask each team member beforehand to reflect on what went well and what could be improved, with specific suggested actions.
  3. Collect items on a shared board and let people comment on and vote for each other's items.
  4. Facilitate a blame-free discussion, first reinforcing effective behaviours, then exploring setbacks and how to handle them better.
  5. Vote on and prioritise proposed actions, keeping to two or three, and agree an owner for each.
  6. At the next retrospective, check whether the agreed actions helped.

Sources

  • Product Management for UX People (Crumlish, 2022)

Also known as

  • Retro
  • Team retrospective
  • Agile retrospective

Categories

  • Design
  • Design & Product Practice