The wait is finally over! Axon now supports team-level grouping of metrics. 🎊
Why is this important?
Great software is built by productive teams - engineering leaders understand that. While organization level metrics matter, it is also important to zoom in a bit to see how each team is doing, which teams need help, and what's slowing them down.
In Axon, a “team” is a logical grouping of one or more code repositories along with one or more projects (from a project tracking tool like Jira). In other words, it allows you to bring together your planning (Epics, stories, bugs) with the output (Pull Requests, commits, etc.) that the actual team works on. Together this allows you to get a cohesive picture of what’s happening in the team. Zooming in at the team level will make it easier to understand the pulse of the team and identify bottlenecks quickly.
Here are some of the key things you can now analyze at the team-level:
How quickly is team delivering customer value?
How many Pull Requests are stuck in review or waiting to be merged?
What is the Cycle Time for the team as a whole? Is it getting better or worse?
How often does the team deploy to production?
How many production incidents are open?
How long did it take for a team to resolve a production incident in a given period (MTTR)?
How are the leading quality indicators?
How many Pull Requests are under-reviewed or merged without any review?
Does the team have too many big-bang code pushes with huge PRs?
Does the team need help with their planning?
How many of the team’s Sprints are delayed?
How many unplanned tasks are getting added in the Sprints?
Is the team constantly overcommitting or undercommitting?
How do I create a team?
A team can be created in just 3 simple steps:
Decide a unique name for your team
Select the one or more code repositories you want to include in the team
Optionally, select one or more projects you want to include in the team.
That’s it! Here’s an example:
Want to add another repository or project to team? No problem, you can always edit the team and the metrics will automatically update!
Note: You should have the “Org Admin” access right to create a team.
How do I analyze metrics at the team level?
Once your teams are created, you can switch between them easily to monitor progress.
You can also view a high-level summary of all the teams by clicking on the “Teams” icon at the top.
From this table you can drilldown to the details of a particular metric - just click on the cell you want to know more about.
And, of course, you further filter by selecting the repository or project at the metric detail level.
Team-level KPI targets can be also defined, helping you fine-tune the targets per team instead of using arbitrary org-level ones.
FAQs about team-level metrics
Who can create teams?
Anyone with "Org admin" access can create teams. Once created, everyone in the organization can the team in their filter.
Is it available for all plans?
Is there a limit on the no. of teams?
Can I include the same repository or project in two or more teams?
Can I create a team based on people instead?