To roll up sprint metrics from sub-teams to a parent team in Azure DevOps, give the parent team an area that includes sub-areas, then open the Sub-teams view in Agile Analytics. It shows one row per sub-team, the parent's own items and a total, with every item counted once, so a release train engineer or delivery lead sees the whole group in one table.
Why the built-in charts stop at one team
Azure DevOps sprint charts belong to one team. A tiered area structure leaves you with a burndown, a cumulative flow diagram and a velocity chart per team and no total. Adding the numbers up by hand double counts any work item that shows up in more than one backlog. If your teams already sit in an area hierarchy, you can use it instead of stitching numbers together.
Step 1: Check the area hierarchy
A team's sub-teams are the teams whose areas sit under the parent team's area, and only when the parent's area includes sub-areas. You set that in the Azure DevOps team settings, under Areas.
- If the parent's area does not include sub-areas, it has no sub-teams for this view.
- A team on exactly the same area as the parent is not a sub-team.
- A team nested under another sub-team folds into that sub-team's row. If Team C sits under Team B, and Team B under the parent, Team C's work appears in Team B's row.
Teams that are not nested
If your teams sit side by side rather than under one parent, this is the wrong view. One consolidated report for 10 teams covers Sprint Summary, Team Benchmarks and the Exec Report for that case.
Step 2: Open the Sub-teams view
Select the parent team in Agile Analytics. Sub-teams appears in the Live group, right after Dashboard, only for a team that has sub-teams. If you do not see it, go back to Step 1. The table shows the current sprint, with these rows:
- One row per sub-team.
- The parent's own items: work on the parent's area that no sub-team owns.
- Total: all of the parent, where every item counts once whichever team it sits under.
Step 3: Read the Progress tab
The Progress tab answers "where are we in this sprint?" for each row, with Items, Done, In progress, Blocked or stalled, Older than usual and Typical cycle time. In a sync meeting, Blocked or stalled and Older than usual lead to the useful conversations. If one sub-team's Older than usual is high for its size, open its Aging & Blocked view to find the items.
Step 4: Read the Delivery tab
The Delivery tab answers "are we delivering what we commit to?" with Committed, Delivered, Reliability, Added, Carryover, Delivered, last 6 sprints and Next sprint, 85% likely.
- Carryover follows one rule across the product: an item moved back to the backlog unfinished is removed scope, not carryover, and late additions are counted and disclosed.
- Read Added and Carryover together. A sub-team with high Added and high Carryover usually has a scope problem rather than a capacity problem.
- Both tabs have Export CSV, for a planning document or a quarterly review.
Related: How carryover is counted
One set of counting rules for every row
Every figure uses the parent team's item types and Workflow Mapping, so Done means the same thing on every row and the rows add up to the total. If a sub-team counts item types differently, its row is marked Counts item types differently, and its own Dashboard may show different numbers. Compare its settings with the parent's before anyone quotes them.
Related: Workflow Mapping docs
The parent team's other views
The parent team has a switch for its sprint views: Sub-teams' work: Included / Not included. Included is the default, so the parent's Dashboard and sprint views count its sub-teams' work once. An Agile Analytics admin can change it; everyone else sees "Set by your Agile Analytics admin". The Sub-teams view is not affected: "This view always shows both."
Combined forecasts
When you forecast several teams together, do not pick the parent and its sub-teams at the same time. While the parent includes their work, that work would be counted twice, and the view warns you to pick the parent or its sub-teams.
Try it
Agile Analytics runs on Azure DevOps Services (cloud) and needs Project Contributor access or higher. The 30-day free trial starts on install with no credit card, and everyone in the organisation has full access while it runs. If your teams are already nested by area, the Sub-teams view appears as soon as you select the parent. More on sprint reporting is on the sprint reports page.
Related: Sprint reports: scope and carryover · Install instructions