Tag: distributed work

This is the second of a multi-part series on Agile Retrospectives with David Horowitz who’s the CEO of Retrium, a company that builds tools to help you facilitate remote retrospectives. The links to Retrium’s Retrospectives Academy below are affiliate links, if you prefer to follow a link that takes you to Retrium’s site, but does not give anything back to the podcast, you can. Just follow this link: Retrium.com. On the other hand, if you want to help us grow this podcast, you can follow the links below or this link to Retrium’s Retrospective’s Academy.

In the second instalment of the Agile Retrospectives Masterclass with David Horowitz, we talk about the 5 phases of a successful retrospective, and share tips and ideas for each of those phases to ensure you are prepared and get the team to find and act on breakthrough improvements. 

You can find Module 1 of the Retrospectives Master Class here. 

It all starts with a simple check-in: “Set the Stage”, Phase 1 of a successful retrospective

When we start a retrospective, usually at the end of a Sprint, the team member’s minds might be on that last bug they just closed, or the story that didn’t get delivered, or the feedback they just got from stakeholders. The Check-in phase of the retrospectives helps all the team members, and the facilitator to get into the retrospective mood. To forget the open threads that will need to be picked up later, and focus on the question: “How can we do even better in the next Sprint?”

In this segment, we talk about the Constellations exercise that helps everyone visualize agreement and disagreement with a specific statement in a way that raises engagement, and increases the energy level of the retrospective. You can find here a detailed description of the Constellation exercise for Agile Retrospectives. 

We also discuss the “one-word check-in” exercise and the “Mad/Sad/Glad” check-in for Agile retrospectives.  

For retrospectives that try to focus on improving collaboration between team members, David suggests The Circle Of Appreciation exercise. 

In this segment, we also refer to the classic book: Agile Retrospectives by Diana Larsen and Esther Derby. 

Gathering Data and Generating Insights, the core of an Agile Retrospective

If we want to enable deeper conversations, we need to be aware that the information that is shared will directly affect the quality of the conversations. Therefore, Agile Retrospectives require special attention to the “gathering data” phase. There are many ways to gather data, and some might even happen during the Sprint, instead of during the retrospective. 

During the retrospective, however, we will visualize that data and help the team make sense of it. 

In this segment, we talk about the timeline exercise, and how to use emotional-queues to help uncover important pieces of information. 

Soft or qualitative data can also be used to augment the use of other data in the timeline exercise. One such way is to use the “journey lines” exercise.

When the data is visible and understandable, then the team focuses on finding insights by analyzing the data and generating possible connections and causal links. Here the challenge for a Scrum Master is to prevent the team from jumping too early into solutions before they deeply understand the problem they are trying to solve. 

David shares some tips to help prevent the team from discussing solutions before they have a shared understanding of the problem. We talk about The 5 Why’s technique, but there are many more. 

Making Retrospectives Impactful: Deciding what to do

Many teams fail in Phase 4, Deciding what to do. But they might fail in quite different ways. For example, some teams might want to commit to too many items at once, while other teams might not commit to any improvement. And finally, the worst problem: those teams that commit to improvements, but work on none of them. 

Great teams, understand well how many improvements they can take from a retrospective, and are clear on the commitment, maybe even including the improvement ideas as items on their Sprint backlog. 

In this segment, we talk about the ICE method for prioritizing improvement ideas and the importance of brainstorming several solutions before deciding what to do. It’s also important to use methods of consensus generation when there are several options that seem equally valuable. The commitment of each team member to the solution to be tried will directly impact their commitment to the work to be done for that solution. 

In this segment, we talk about experiments and the use of such templates as the Hypothesis-Driven Development template by Barry O’Reilly. 

Phase 5: Close the retrospective

At the end of the retrospective, our goals are to provide closure, a sense of achievement, and energy for the work ahead. 

How can we do that? In this segment, we talk about the “retro on the retro” and the “gif check-out”. Two simple approaches that help the team feel a sense of accomplishment, and also get better at doing future retrospectives. 

Which closing exercises have you used? Share those with us on Twitter or LinkedIn! 

About David Horowitz

David Horowitz is the CEO of Retrium, a platform for agile retrospectives that has powered over 100,000 retrospectives from thousands of companies across the world.

Prior to co-founding Retrium, David spent a decade at The World Bank as an engineer turned Agile coach.

He has degrees in Computer Science and Economics from The University of Maryland and a Master’s Degree in Technology Management from The Wharton School of Business.

Learn more about Better Retrospectives with David Horowitz by accessing the FREE Retrospective’s Academy by Retrium: http://bit.ly/retromasterclass

You can link with David Horowitz on LinkedIn and connect with David Horowitz on Twitter.