How do I analyze team radar results?
TeamHealth Radar Assessment Results
Once the team has completed the assessment, you’re ready to analyze the results, usually during a retrospective session with an AgilityHealth Facilitator and your ScrumMaster.
To view the results of your team's assessment, log into AgilityHealth, which will land you on the Team Dashboard. Click on your team's icon on the Team Dashboard. This will take you to your team’s assessments dashboard. Click on the specific assessment of interest and your results radar will appear in Summary view.
You can expand/collapse this view or toggle to the Detailed view where you see the dots. Each dot represents one person but as the results of the survey are anonymous, you will not know which dot belongs to a specific person. The shading between the dots is the ‘variance’ between answers. Wide variance shows lack of consensus, narrow shading shows consensus.
When analyzing the results, you should:
- View the detail view, with the dots for responses
- Zoom in to focus on each section
- Identify related competencies
- Look for trends and review the textual responses
- Document strengths, improvement areas and any impediments you see
- During the retrospective session, along with the Facilitator and ScrumMaster, build a growth plan in AgilityHealth with a few growth items for the team backlog and a few growth items for leadership/organizational backlog
Additional Insight into Analyzing Results
To help you with results analysis, here are some things to look for:
1. Overall Radar Analysis: When you look at the radar, when the average red line is towards the center, the team has rated themselves less mature, as it expands outwards, the team has rated themselves higher. So, what does the overall radar tell you?
2. Look for Patterns: Dig deeper by looking for specific patterns such as the ones below:
Pattern – Wide range of responses: Could be a symptom of several things: New team members, lack of communication on this area/competency, misunderstanding of what this competency means, different roles experience or view this differently.
Pattern – Very High scores: This should be rare as there are not many teams that have achieved world class maturity and adoption of practices so when you do see very high ratings, look for the following:
- Could be accurate and the team may have developed in maturity this specific area. Look around the rest of the radar to see if other related areas you expect to be high are actually mature as well.
- Too many World Class scores could also reflect fear, misunderstanding or over-rating. Some teams are afraid to rate themselves realistically because they are afraid of looking bad or being judged by management. Teams might also have a misunderstanding of the competency or perhaps they are new and very excited about improvements in this area and reflect this excitement by over-rating as they don’t know what they don’t know. This reduces the confidence in the data quality.
Pattern – Very Low Scores - Lack of Adoption, Low Maturity: Teams may rate themselves on the lower end for adopting specific practices. First, this is a good sign of the team being open and honest and reflecting realistically where they are. Dig to see if these areas could be impacting the team and if this is an area to discuss with the whole group.
3. Read the textual responses and try to understand the context behind the why on how the team rated themselves and what common threads emerge from the collective comments.
When you were taking your survey, you and your team members had the chance to add textual responses. The main sections are Strengths, Improvements, Impediments and the Sub-Dimension Notes (what you filled out as you rated each sub-dimension, see sample below). You will also review these during your retrospective and use them to help create growth plan items. These are anonymous so they should not contain information that can tie them back to one specific team member.
Filter the results by participant groups:
When Team Admins add team members to a team in AgilityHealth, they tag the team member with relevant participant group information. You can view the results on the data by selecting different participant groups, using the two green arrows in the upper left hand corner. Click on the green arrows and select which participant groups you want to see. For example: filter by Leadership Team vs. Technical to analyze how these two groups responded, or Contractor vs. Employee or California vs. India vs. Seattle to see this by geography.
View the analytics table:
Scroll down below the radar to view these four tables which provide a nice summary of the top and lowest 5 competencies (average score), highest 5 consensus (narrowest shading) and lowest consensus (widest shading). During your retrospective, as a team you should review and analyze these as part of your discussion.
Team Maturity Stage:
The Facilitator and ScrumMaster will work with your team to help determine which maturity stage the team believes they are in. You'll use the below maturity roadmap for guidance.
Learn more in our What do Crawl, Walk, Run, Fly mean as Maturity Stages article.