Gather Data is the retro step that most teams don’t skip.
Still, what is quite often missing is hard data, e.g. events, metrics (WIP, throughput, leading time, velocity, NPS etc.), features, stories completed (or not completed), defects discovered on production, number of interruptions and task-switching, number of tasks in parallel. Think about what could be valuable input for your team retro and how you can present it.
Another common thing is that the same format is used all the time (“What went well? What didn’t?”).
Not only could we use variations of wording (Mad/Sad/Glad; Proud & Sorry; The Good, the Bad, and the Ugly; 4 Ls – Loved, Learned, Lacked, Longed for etc.) and variations of metaphors (Sailboat, Hot-Air Balloon, Treasure Island), but also come up with totally different formats like:
- Timeline – Participants write down significant events and order them chronologically
- Back to the Future – You take the DeLorean back to the beginning of the project
- Avoid Waste – Tackle the 7 Wastes of Software Development
This helps us look at situations from a different angle and leaves no place for boredom.
You can find the descriptions of most activities mentioned above and new ones on Retromat.
All Retrospective Phases:
5 Phases of Retrospective
Phase 1: Set The Stage
Phase 2: Gather Data
Phase 3: Generate Insights
Phase 4: Decide What To Do
Phase 5: Close The Retrospective
Leave a Reply