The other day, I facilitated a sprint retrospective in the park. The sun was shining, and we had all been working hard to complete our backlog, so it felt like a nice reward for everyone’s efforts. Holding a retrospective outdoors can also give it an energy and sense of enthusiasm that is harder to find in a small room.
I’ve run outdoor retrospectives before, and have previously followed fairly classic plans, with much arranging of index cards. This has never been a great success, as the slightest breath of a breeze can make a mess of your planning. For this retrospective, I designed a plan to avoid these problems, drawing some ideas from the Appreciative Retrospective plan.
This retrospective took an hour for a team of nine. You’ll need a pile of index cards or sticky notes, and a pen per person. Here’s how to do it:
Some people are sun lovers, whilst others, like me, burn easily and need some shade, so find a location that will work for everyone. Don't worry too much about the state of the grass, as I suggest you conduct the retrospective standing up, if possible.
Get everyone to stand in a circle, with enough personal space for everyone, but close enough that you can hear everyone speak.
Observations: It's nice if you can find a location where there won't be too many distractions. We weren't entirely successful: there was a hen party in another corner of the park, whose popping of prosecco corks and parading of an anatomically exaggerated blow-up mannequin was hard to ignore; there was also a group of male models sunning themselves noisily behind us (I’m working at a fashion company, so this is less unusual than it may sound), and three young women were smoking some interesting cigarettes upwind of us. Nonetheless, our retrospective was a success despite occasional distractions.
Ask everyone to spend a couple of minutes coming up with three words to characterise the sprint; then go clockwise round the circle and ask each person to tell the team their three words.
Observations: It's surprising how much difficulty people have sticking to three words; the important focus of this task is not the three-word limit, but getting a concise summary of the sprint.
Moving anticlockwise around the team, ask each team member to thank their neighbour for something they have done during this sprint.
Observations: Our Scrum Master broke the rules by thanking the whole team for their efforts. The focus of this task is to generate a positive mood across the team, and it's important that no one misses out on individual thanks, so I asked him to thank his neighbour for something as well.
Hand each person three cards, and give them three minutes to write down three things that went well during the sprint. Going clockwise round the circle from a different starting point, ask each person to read out their three successes.
Observations: It's useful for the facilitator to observe and comment on common themes, as this can help reinforce good practice.
Hand each person three more cards, and give them another three minutes to write down three things that could have gone even better during the sprint. Then go anticlockwise round the circle and ask each person to read out their three improvements.
Instead of arranging the cards on a whiteboard (which isn't practical in the park), appoint a champion for each improvement. Ask the first person to choose one of the improvements they suggested, and then get everyone else to hand this person any cards that describe a similar improvement. Keep running round the team until each team member has just one group of cards.
Observations: There's a chance that you'll end up with more themes than team members, in which case you'll have to make a decision to drop some of these themes; in our case we had fewer common themes than team members, so we didn't have to do this.
Rather than dot-voting, which again is impractical in the park, select the commonest themes. Ask everyone with any cards to take a step into the circle. Then ask everyone with just one card to take a step out again; then everyone with just two cards; then three, and so on until just three people are left in the inner circle.
Then have a three-minute discussion of each of these suggested improvements, with the focus of identifying at least one action per theme for the next sprint. Ensure someone is assigned to each action.
Observations: We ran slightly over the three minutes assigned to each theme, but this wasn't a problem; if we hadn't had a time limit, I suspect the conversation would have been much less focused.
Finally, going round the circle clockwise, ask everyone to describe how they felt about the retrospective itself.
Observations: The feedback was very positive. The team had clearly enjoyed the opportunity to get out of the office, and they felt that the session had been successful: everyone was engaged and we came up with some good actions.
Software is our passion.
We are software craftspeople. We build well-crafted software for our clients, we help developers to get better at their craft through training, coaching and mentoring, and we help companies get better at delivering software.