Great agile retrospectives engage the entire team, maintain trust and psychological safety, and allow everyone to equally share their perspective. If team members get bored or retrospectives feel monotonous, this can get in the way of gaining new insights and discussing the most important topics. Using a variety of retrospective techniques can help keep things fun and engaging for your team. And there is no retrospective that helps teams use qualitative data to drive conversations on alignment like a Team Radar Retrospective.
Team Radar retrospectives help teams compare individual responses on a variety of categories transparently and quickly to identify points where the team agrees or disagrees about a topic. They can be used alone or in combination with a column-based retrospective and can provide important insights into how a team is working together toward continuous improvement.
To start running a Team Radar retrospective meeting, the facilitator selects the Team Radar from Retrium's retrospective exercises toolbox and establishes the categories that participants will be able to vote on. To set the stage for a successful retrospective, it is important that everyone has a shared understanding and agrees to the same definition for each of the labels on the radar template before you move on to the next phase of the retrospective.
Each team member can then add their responses to the spokes on the radar. For each spoke, a team member will indicate (usually on a scale of 1-5, where 1 is the lowest rating and 5 is the highest) how they feel about the idea or issue on that spoke of the radar.
When conducting a Team Radar retrospective, it is important to choose your tools wisely. Flip charts and markers are okay for drawing a team radar, but an online retrospective tool like Retrium allows team members' responses to be collected anonymously and simultaneously. This prevents groupthink and regression to the mean, which can be common when responses are drawn one at a time often with your teammates watching your contribution. And unless you love spending time in meetings doing math, find a tool (we know a great one, ahem 😉) that takes care of data analysis to save the facilitator time and allow the team to focus on discussions that generate insights and action.
Once everyone has shared their feedback, the team moves on to the analysis phase to see and discuss the results. From there, the facilitator can lead a discussion on the results with questions like:
By the end of this retrospective, you will have gained valuable insight into what areas may need additional support or deeper discussions. And, as an added bonus, the team had a fresh, engaging retrospective that can be referenced in your retrospective history. 😎