Today, I wanted to write about some flavors of a retro. For example, how do you guide a team that doesn’t want to address the elephant? However, I realized something was missing. How can I tackle the flavors when I haven’t discussed some facilitation fundamentals? So let’s get back to the basics of retrospectives.
- It’s always about them. Never enter the retro knowing what items the team will improve for next sprint. That’s not your decision; it’s theirs. A good scrum master will have ideas of where the team should grow. A great scrum master will let them find their own way there. Which leads me to my next tip.
- You create the container; they create the conversation. Most of the time should be spent here as you prepare for the retro. It’s your responsibility to find the right containers that allow the team to have the best discussions. It’s here with my retro flavors that I take a deeper dive in future blog posts.
- Practice good retro structure. Esther Derby has an outstanding model, and she writes about it in her book Agile Retrospectives. The idea is that the conversation initially diverges with a growing list of ideas and then ultimately converges into no more than three items that team agrees to implement the following sprint. If you don’t have time for all five stages, choose your stages wisely to take advantage of the team’s time. You’ll see the stages titled in the visual below.