Glossary of AgilityHealth® Terms
We know the definition of some terms can vary, depending on the circumstances in which they are used. Here are some terms and their definitions, based on how we use them in reference to AgilityHealth®.
An AgilityHealth® retrospective is a 2-3 hour strategic session that aims to help individuals or teams reflect on their last quarter or release and develop a plan to improve during the next quarter or release. An AgilityHealth® retrospective is facilitated by a certified AgilityHealth® Facilitator (AHF).
Team members complete an assessment either prior to or during the retrospective. During the retrospective session, Facilitators will analyze the radar developed from the team's results and review the team's textual responses. Having real conversations about these items will allow the Facilitator and the team to build actionable growth plans to be worked on by the team and leadership over the next quarter.
AgilityHealth® Facilitator or AHF
A Facilitator plays a crucial role in the organization's utilization of AgilityHealth® by facilitating team retrospectives, helping the team to analyze the radar developed from the team's results and helping the team to develop a solid growth plan.
Online assessment taken by team members to gather their input on the team’s health and maturity. Results are anonymous and displayed on a radar with individual dots representing each team member’s answers. Textual responses are also gathered from the team members and displayed below the radar results for analysis by the team.
A team is comprised of individuals who are assigned to take an assessment together.
A multi-team is comprised of teams, rolled up into a multi-team or team of teams. A multi-team is created to roll-up assessment results from various teams, so leadership can see radar results for teams of interest all together. This also allows Leadership to pull in growth items into their backlog that have been marked as Organizational by teams.
An enterprise team is created to roll-up multi-teams into an enterprise level view to see common themes throughout the organization. This also allows Executive Leadership to pull in growth items into their backlog that have been marked as Enterprise by Leadership when reviewing their organizational growth items.
Tags are customizable attributes that can be used to organize your company within AgilityHealth®. Team Tags include things such as product line, program, portfolio, lines of business, methodology, work type, etc. and are used to link teams together, in order to roll their assessment results up into a multi-team or enterprise-team view.
Team Member Tags (Roles, Participant Groups)
Used to identify an individual’s role or other pertinent information within AgilityHealth®. These can be used to filter data within a specific team, as well as identify trends across teams among individuals in common roles.
- Role is the function or position each person holds on this team. Role tags will allow you to add additional roles to your company that can be assigned to team members. You will also be able to edit existing roles to update them to your company's specification.
- Role tags also determine if team members receive the appropriate assessment questions (product owner vs. team members for the Team Confidence competency in our TeamHealth Radar, for example). They are also important to ensure data at the multi-team roll-up level can be filtered for analysis.
- Participant Group tags will allow you to set general to specific tags related to the team member. This could be as easy as adding a Remote tag to show that the team member works from home or Europe to show that they are remote and part of the European team. This could also show that they are part of a Business Leadership team or the Support team. Participant Groups are usually the tags that are heavily customized based on the company’s needs.
A Stakeholder is simply someone who has an interest in the team and their health. This could be Managers, executives, team sponsors, etc. A Stakeholder will not have access to the assessment results, but if they are a Manager, the results may be shared with them during the Manager Debrief.
As part of our TeamHealth assessment, a short assessment is sent to Stakeholders of a team, usually a week or two prior to the retrospective session. The Stakeholder assessment is sent in advance so the results are available during the retrospective session.
Most of our team-based assessments do not have separate questions for the Stakeholders, they will be sent the same questions as the team in those cases.
Results from an AgilityHealth® Assessment are displayed on a Radar. The radar image has a summary view of all responses and a detailed view, plotting individual responses as dots on a scale.
The radar is broken into categories, called Dimensions, further broken into categories called Sub-Dimensions, further broken into categories called Competencies. The questions answered in the assessment are grouped by Competency.
Major area that we measure, includes Sub-Dimensions and Competencies.
Grouping of Competencies within a Dimension.
Specific area that we measure, through one or more assessment questions.
High and Low Competencies/Consensus
Each dot on the radar results represents one person’s answer within a competency, but as the results of the assessment are anonymous, you will not know which dot belongs to a specific person. The shading between the dots indicates the range of answers. A wide range shows lack of alignment, a narrow range indicates greater alignment. The 5 competencies with the highest consensus of agreement and the 5 competencies with the lowest consensus of agreement are displayed in an analytics table below the radar results. The table also displays the 5 competencies with the highest ratings from the compiled team’s answers, along with the 5 competencies with the lowest ratings from the compiled team’s answers.
Growth Items (Team, Organizational and Enterprise)
A growth item is an item a team has decided during their retrospective to focus on improving over the next quarter or other chosen time period. Growth items are written like stories, and should also follow the SMART guidelines.
- A team growth item or TGI is something that can be resolved by the team themselves.
- An organizational growth item or OGI is a growth item the team needs Leadership to help them resolve.
- An enterprise growth item or EGI is a growth item Leadership needs to elevate to the highest level in the organization to help them resolve.
Growth Item Competency Targets
When creating a growth item during a retrospective, you will need to pick which Competency Target the growth item relates to best. This is a way to clearly identify what you are trying to impact when making improvements, so that everyone working on the solution has the same goal in mind and so that you can test your assumptions about what will make a difference for team health and maturity.
Competency Targets also allow for the company to see over many teams, what areas need the most improvement and where Leadership can assist most.
A resource within AgilityHealth® that allows teams and individuals to leverage the results of their assessment. Participants can analyze their results to see where they are now, decide where they want to go and use multiple resources from the Growth Portal to highlight what they need to do to get there. This guidance includes best practices, improvement tips, helpful downloadable resources, videos focused on Agile concepts and strategies, as well as opportunities to request help from internal or external coaches.
If a team has taken multiple assessments, you can see trends over time to gain additional insights. The Growth Item Journey tabs displays the average score for each dimension, sub-dimension and competency across all of the assessments completed within a selected time period.
Allows companies to see how the results from their assessments at the Enterprise, Multi-Team and/or Team level compare to other companies within AgilityHealth® and to see how the results from Multi-Team and/or Team level assessments compare to other Multi-Team and/or Team level assessments within their own company. Benchmarking is a feature that is turned on/off by company and can be turned on/off for each level of results, at the company level as well. Companies can also decide if they want to participate in Global Benchmarking, so their results are able to be included with and benchmarked against all companies in AgilityHealth®, or they can choose to opt out. Benchmarking is currently available for our TeamHealth, DevOps and Enterprise Business Agility (EBA) Radars.