Use Team health insights to gain an understanding of your teams’ health. View information related to your teams’ coding processes and code collaboration. This information helps you investigate and diagnose potential issues as well as see where your team is succeeding.
Team health insights metrics
Team health insights shows your teams’ work across a collection of coding, collaboration, and DORA metrics. These metrics give you visibility into your teams’ activity in commits and PRs across five categories: Activity, Culture, Efficiency, Predictability, and Reliability.
Team health insights shows two years of data. Data older than two years does not factor into the metrics.
Note: PR data from ADO Services and ADO Server is only available starting from six months before the integration is first processed, at the earliest. Users on a Core plan only have access to select Team health insights metrics. Users on a Plus plan who do not have a Jira integration may not see the incident-based metrics Change failure rate and Time to restore service.
Selecting Team health insights metrics
There are several metrics tabs in the report to help you quickly see the metrics that are of most interest to you. Use the Activity, Culture, Efficiency, Predictability, and Reliability tabs to see all metrics for each of those categories.
The first All tab lists all available metrics in the report until you use the Edit metrics dropdown to customize which metrics you want to see. Then the tab becomes a Custom tab containing only the metrics you’ve selected until you change them.
There are a few ways to approach the decision of which metrics to select, depending on your goals for the report:
- Decide which metrics you want to use to drive change on your team, then deselect all other metrics to make your most important metrics visible.
- Select one metric from each of the categories to get a more holistic view of metrics across your team.
- Select only commit metrics to dive deeper into your teams’ coding practices.
- Select only PR collaboration metrics to see how your team is working together to release code.
Whatever way you decide to choose metrics, make sure you customize the report to help you achieve your goals. Selecting only the metrics most important to you gives you the information you need to focus on team goals without extra noise. Change the metrics you’ve selected at any time to get a different view of your teams’ health.
Tip: To get the most out of your Team health insights experience, configure targets for your metrics. Either navigate to the Targets page or click Edit targets next to the Edit metrics dropdown to configure your targets.
Learn more about Flow metrics.
How do I use Team health insights?
Engineering leaders can use Team health insights to view commit and PR collaboration activity trends over time. Use this information to gauge your teams’ health.
Use the filter at the top of the report to select the teams, repos, and date ranges you want to view metrics for.
The Team filter shows metrics for the selected team, including for:
- Commits authored by a member of the team
- Pull requests authored by a member of the team
- Pull requests commented on by a member of the team
- Deployments where a member of the team is a commit author
- Incidents where a member of the team has ever been the assignee on the ticket
The Date range filter shows metrics for the selected date range, including:
- Commits created during the date range
- Pull requests created during the date range
- Deployments made during the date range
- Incidents created during the date range, for Change failure rate
- Incidents closed during the date range, for Time to restore service
In the tiles at the top of the report, see:
The overall, average, or median value for your selected metrics.
The trend arrow for the metric. A trend arrow only displays if you include four or more Monday to Sunday weeks in your selected date range.
The target for your metric, if one exists, and whether you’ve achieved it.
In the details view below the tiles, see:
The overall, average, or median value for your selected metric.
The trend value and targets for your selected metric, if they exist. The trend is calculated using linear regression.
A bar graph of the weekly values for the metric.
Information about the metric, its calculation, and recommendations to improve it.
- A Hide details option to collapse this view so you can more easily see the team overview below.
Important: The Team health insights report shows commits based on the local time zone of the commit author, not the time zone of the person viewing the report. If you want to see commits shown based on your time zone, use Work log. Because of this difference, the total number of coding days for a user may appear different between Team health insights and Work log. Team health insights looks at the author date for commits, not the date the commit was pushed.
How do I view insights for a user or a team?
Below the Team health insights graph is a team-by-team view showing the average of a metric for each team. Click into a team to view the report filtered by that team.
Sort the teams alphabetically or reverse alphabetically, or by sorting metrics from high to low or low to high.
If you don't immediately see a team you're looking for, use the Search filter. This searches for any immediately nested teams in the team you have selected. It does not search for nested teams within those nested teams.
Note: For contributor metric tiles, only work associated with the selected team is included in the individual calculation. If the user is also associated with a different team, selecting that team may result in a different metric being displayed for the user.
If you need help, please contact Pluralsight Support.