Zoltán Ludányi, one of my customers for whom I did an in-house retrospectives workshop, designed a retrospective exercise where team members pair up to discuss why, when and how to do specific agile practices. Purpose of the exercise is to involve minorities and introverts into the team’s improvements and actions. Here it is: the Extreme Pairing Retrospective!
About half a year ago I have taken some of my Scrum masters to Ben’s retrospective training. I liked the training very much, and also his website collecting many retro techniques. I still use this as a reference when I coach people.
However, recently I have hit an obstacle. In one of the teams that I have visited, a minority of people were suffering with Scrum ceremonies. These members were passive not only in the ceremonies but also on the retro.
Since the majority of the team have been talkative and positive, these issues did not get enough attention on the retrospective either. Standard retro techniques where ideas are dot-voted by the team have down-prioritized the issues, and the team did not realize they are leaving someone behind.
Even though it’s good to focus on problems that matter to the majority, with a member of the team we have often said it’s also a team responsibility to address issues of the minorities; in this case to make these ceremonies work for others.
Extreme Pairing Retrospective Exercise
So in order to address this issue, I knew I had to approach the retrospective from a new perspective; and after a long evening, I have come up with a retro idea of “pairing up extremes”.
The retro goes like this:
- You identify a topic where you feel the team is divided, or where you have minorities, then you break it down to independent parts/topics/aspects. In our case, we target ceremonies and simply go through each of them. Let me continue the technique using this example.
- In each round, you ask the team members to evaluate a ceremony, and vote using a fist-or-five. Then the two extreme values pair up. You repeat this until everyone has a pair.
- Once we have all members paired up, they go for a 1-on-1, and discuss why one loves and the other hates the ceremony, and they have to think about how the hater could get the same value out of the ceremony. Encourage them that any action items are OK, even saying “I do not participate, instead I will get the outcome like this or that”. I recommend that pairs talk in the same space, so that the coach can observe the discussion, and coach the pairs in equal share of conversational turn taking. If required, please remind the pairs that the purpose is not to convince each other that the ceremony is good/bad, but to understand the other side, and find a common ground. This is especially important if you know certain members in the team are too talkative or pushy.
- Then after 15-20 mins, we discuss the outcomes on the team level, finetune the action items, and commit to them on the team level.
- Instead of doing a fist-or-five you can also start the technique with a constellation exercise (described in the book Getting Value out of Agile Retrospectives). Usually, you will also see many conflicting opinions there.
- If everyone hates a given ceremony, then this can be topic for an open discussion. Put it aside until after the pair discussions are done.
One of the major things that I have taken away from Ben’s training (and his book) is double learning. Even though I think I have been doing this before, I think I am much more focused on this now that I have identified it as a behavior. I more often ask myself ”how did I get to this question?”, ”how did I find this solution?”, etc. It’s like self-coaching.
My double learning for this exercise is that many agile techniques can be used for a different purpose. If you look at the technique, then I have obviously derived it from planning poker – subconsciously. Once I have realized where it came from, I have even introduced the game saying “this is just like planning poker, we vote, and then extremes talk”.
I think people like things that they know, and there is more buy-in if the rules are already familiar in any form. So whenever next time I get stuck with retro techniques or other facilitation techniques, the first thing I will do is to review the practices I do in another context. It seems they may be powerful under other circumstances as well.
I hope you have liked the technique, but more than that I hope I have motivated you to design your own! If you have any thoughts, especially if you have managed to use or alternate this technique, please leave a comment below.
Zoltán Ludányi is an Agile Software Development Consultant.
Valuable Retrospective Exercises
Thank you Zoltán Ludányi for sharing your retrospective exercise with my readers. I like it and want to try it out when I work with a team that’s struggling to involve minorities and introverts. And thank you for your kind words about my workshop, it was a pleasure to do the in-house retrospectives workshop for your Scrum masters.
To truly understand how a team is doing you need to involve all team members in the agile retrospective. A suggestion to include introverts is to use Non-verbal Exercises in your Agile Retrospectives.
Have you designed your own retrospective exercise?