If you facilitate retrospectives then you’re probably familiar with the 5 phases from “Agile Retrospectives” by Derby and Larsen:
- Set the stage
- Gather data
- Generate insight
- Decide what to do
- Close the retrospective
Whenever I talk about them and in all the material I’ve created, it always looks like the phases are strictly linear. But that is not how they work in the majority of my retrospectives – because I rarely have single-topic retros. I usually run a “gathering potential topics”-activity like “Speedboat” or “I like, I wish” and then the team works through 2 or 3 of these topics.
It would be strange to first talk about 3 topics in depth and afterwards come up with action items for all of them. Instead we talk about 1 topic in depth and create an action item for this topic. And only then start with the next topic. Like in this highly elaborate diagram 😉 :
I thought it might be worth stating this explicitly as it’s not necessarily obvious for beginners.
What about you? When do you decide on action items?
PS: Interested in retrospectives? Sign up to the Retromat newsletter to get related news and tricks!