A Stack Overflow question about the cumulative flow diagram puts the problem plainly: the chart belongs to one team, so what do you do with ten? Azure DevOps sprint and flow charts are set up per team, and nobody gets a team-of-teams summary unless they build one. Agile Analytics has several views that put teams side by side, and most of them can include teams from other projects in the same organisation. None of them rolls up across Azure DevOps organisations. Below is each view, what it shows across teams, and where it stops.
Sprint Summary: "Teams at a glance"
Sprint Summary is the per-team sprint report. Use Add Team to add more teams; the picker has a tab per project, so the teams can come from anywhere in the organisation (tick "Limit to current project" to hide the others). With two or more teams, a "Teams at a glance" table sits above the team cards, one row per team, with these columns:
- Team and Sprint. A running sprint is marked (in progress), because its figures are partial.
- Delivered of committed, and Done of all items.
- Scope change.
- Carryover. A running sprint shows a dash, with the note "Carryover is counted when the sprint ends."
Related: Sprint reports: scope and carryover
Read across, then down
The note under the table says it: "Each row uses the same numbers as its card below." Scan the rows for the team that stands out, then scroll to its card for the detail: "Delivered 8 of 10 committed", the Planned Items, Scope Change, Total Included Items and Carryover tiles, and the lists of carried-over and removed items. Each card has Download CSV, and Download All exports every team at once for anyone who still wants a spreadsheet.
Sub-teams: when the ten teams sit under one parent
If your teams are set up as sub-teams of a parent team, select the parent and a Sub-teams view appears in the Live group, right after Dashboard. It is offered only for a team that has direct sub-teams. It shows one row per sub-team, a row for the parent's own items and a "Total: all of" row, and every item is counted once, which matters when the same work item shows up in several backlogs.
- Progress tab: Items, Done, In progress, Blocked or stalled, Older than usual and Typical cycle time.
- Delivery tab: Committed, Delivered, Reliability, Added, Carryover, "Delivered, last 6 sprints" and "Next sprint, 85% likely".
- Export CSV on both tabs.
The parent's other views
By default, the parent team's other sprint views include its sub-teams' work, counted once. An Agile Analytics admin can switch that to the parent's own work only; everyone else sees "Set by your Agile Analytics admin". The Sub-teams view itself always shows both.
Team Benchmarks: which team needs help?
Team Benchmarks, in the Agile Coach group, compares teams and surfaces the biggest bottleneck first, with a suggested next step. It opens with Total Teams, Avg Health Score, Need Support and Healthiest Team, then a sortable table: Team, Health Score, Grade, Reliability, Throughput, Cycle p50, Flow Eff %, WIP, Carryover and Sprints.
- With no custom set, it shows this project's teams (up to 25), with the note "Showing all teams of this project. Pick a custom set in Configuration > General."
- A custom set can include teams from other projects, and the view then says how many teams and projects it compares.
- Its Carryover column still uses the older measure (committed items not finished by sprint end), so it can differ from Sprint Summary for the same team.
Exec Report: one page for leadership
The Exec Report is a "one-page leadership summary for the teams you select: forecast, risks, delivery trend and DORA, with per-team detail after it." Teams from the current project appear as checkboxes, and Add Team brings in teams from other projects in the same organisation. The report says "Each team is counted with its own project's Item Types and Workflow Mapping", so a project on a custom process is not forced into another project's definitions.
- Limit: once a team from another project is in the report, it holds up to 8 teams in total. With teams from the current project only, there is no such cap.
- Shared work is not de-duplicated: "If two teams share work items, that work appears in both sections." Do not add the team sections up to get a total.
- Share it from the Share menu: Export leadership report (PDF), Copy summary, or Copy email text to paste into your own email. The report is built in your browser from the Azure DevOps REST API; your work items never leave your browser.
Other views that take several teams
A few more views work across teams. They are useful alongside the four above:
- Multi-Team Aging: aging work across the teams you pick, with a Cross-Project Selection panel for teams in other projects.
- Live Stats: a live matrix of the current sprint for the teams set under "Scoped teams for live sprint views" in Configuration, which can come from several projects. Export CSV and Download PNG.
- Monte Carlo: forecasts for the same scoped teams. Multi-team forecasts add up each team's delivery.
- Cycle Time: "Compare teams across projects" in the team list, offered when the organisation has more than one project, for up to 8 teams.
Making the rows comparable
A side-by-side view is only useful if "done" and "carryover" mean the same thing on every row.
- Workflow Mapping is set per project, under Configuration. Done is the first state mapped as Done, so if one project maps Ready to Release as Done and another does not, their cycle times will not line up. Have an admin check each project before you compare.
- Carryover follows one rule in Sprint Summary, Sub-teams, the Dashboard, Delivery Signals and the Exec Report: an item in the sprint at the end of at least one sprint day, not done when the sprint ended or when it left, and either still in the sprint or moved straight into the next one. Team Benchmarks and Retro Snapshot still use the older measure, so pick one source for carryover when you report upward.
Related: How carryover is counted · Workflow Mapping docs
What this does not cover
Be clear about the gaps before you promise anyone one page:
- Other organisations. Nothing rolls up across Azure DevOps organisations. Each organisation installs and licenses the extension separately, and the views read the organisation you are signed in to. Ten teams in three organisations means three sets of reports.
- One cumulative flow diagram for ten teams. Cumulative Flow, Flow Metrics, Delivery Signals, Retro Snapshot and Sprint Capacity each work on one team at a time. For the consolidated picture, use Sprint Summary, Sub-teams or the Exec Report, and keep Cumulative Flow per team.
- Planning across teams. These views report on work; they are read-only and do not plan, move or change work items.
- Azure DevOps Server. Only Azure DevOps Services (cloud) is supported.
Which view for which question
A short guide for the next time someone asks for "one report":
| Question | View |
|---|---|
| How did every team do last sprint? | Sprint Summary, "Teams at a glance" |
| How is the parent team doing, counting each item once? | Sub-teams |
| Which team needs help first? | Team Benchmarks |
| What do I send leadership this month? | Exec Report |
| What is stuck right now, in any team? | Multi-Team Aging |
| Are cycle times similar across projects? | Cycle Time, "Compare teams across projects" |
Try it
Agile Analytics runs in your browser against the Azure DevOps REST API, with no Power BI and no personal access token. The 30-day free trial starts on install with no credit card, and everyone in the organisation has full access while it runs, which is enough time to load all ten teams into Sprint Summary and the Exec Report and check the numbers against what you expect. Every plan includes every view in this post.
Related: Install instructions · Pricing