Related Posts

LeadingIn Tech #8: Wrapped

Here is a set of retrospective activities to use to collect different kind of outputs as needed depending on different team stages or context (new team, project completion, regular sprint retrospectives, team health check, etc.)


Team Radar

When:

This is the activity I run with less frequency because the changes you can compile for this session could take longer to generate a visible impact. That's why I usually run them twice a year or when landing to a new team where I want to get a temperature check of the team health.

Expected Outcome:

This retrospective pretends to collect a general overview of the team perception on a set of 5 (or more) dimensions such as: Team, Process, Requirements, Collaboration with external teams and Tools. As a result you will generate a visual to show the team where they stand strong and what areas need to be looked at. By asking additional probing questions on this areas the team creates action items to improve the areas where the team is not happy with the current situation.

How it works:

The team vote with an emoji for each of the dimensions, in the end all points get aggregated for each and represented in a radar chart (ideally) . This will show to the team a visual on what are the strengths and weaknesses to put focus on. Finally triggering a conversation on how to tackle on the weakest points and how to double down on the strengths.

😃 (happy= 2 points), 😐 (neutral = 1 point), 😞 (sad = 0 points)

Radar Axis: