You can build a one-page delivery report by hand from Azure DevOps queries, charts and a slide, or generate one with the Exec Report in the Agile Analytics extension. Either way the page should answer four things: when work will land, what is at risk, whether delivery is improving, and how the delivery pipeline is performing.
What a leader needs on one page
A leadership reader wants to decide quickly whether to step in. Four blocks cover that.
- Forecast. A date range or item count with a stated confidence, not a single promised date.
- Risks. The few items or teams that need attention, with enough context to act.
- Delivery trend. Several past sprints, showing whether delivery is stable, improving or slipping.
- DORA. Deployment frequency, lead time for changes, change failure rate and time to restore.
Building it by hand, and what that costs
The manual version usually looks like this.
- Run a work item query per team for the finished sprint and export it.
- Count committed, delivered and carried-over items in a spreadsheet, with your own rule for each.
- Copy velocity or burndown charts from each team's dashboard.
- Pull deployment and incident data together for the DORA figures.
- Work out a forecast, often from average velocity.
- Paste it all into a slide, write the risk notes, and send it.
The real cost is the rework
It is not one big task. It is the same rework every sprint. Definitions drift between teams, charts use different scales, averages hide variance, and someone has to remember which state means done for each team. When a team sits in another project, the queries and mappings double.
Step by step with Exec Report
Exec Report builds the page in your browser and sends nothing to Baytek, which helps if your security team asks where leadership summaries go.
- Open Agile Analytics under Boards, then Exec Report in the Measure group.
- Use Add Team to put several teams on the page. You can include teams from other projects in the same organisation, up to 8 teams once a team from another project is added. Each team is counted with its own project's Item Types and Workflow Mapping.
- Read the page: forecast, risks, delivery trend and DORA.
- Open Share and pick Export leadership report (PDF), Copy summary or Copy email text.
Sending it
Sending is a manual step each time. Copy email text copies the text for you to paste into an email you write yourself; the extension does not open an email draft, and it does not schedule or send the report. If you want something automatic, the Delivery Digest under Tools, Configuration posts a weekly summary of throughput and bug flow to Slack or Teams. It runs as a pipeline in your own Azure DevOps, and it is a team summary, not this page.
What to check before sending it
A one-page report gets forwarded. Five minutes of checking saves a correction later.
- Workflow Mapping. Confirm each team's mapping under Tools, Configuration, Workflow Mapping. Done means the first state mapped as Done.
- Sprint timing. Carryover is counted only when a sprint ends, and a running sprint is never in averages. Send after the sprint closes if carryover matters to your readers.
- Carryover definition. Items moved back to the backlog unfinished are removed scope, not carryover. Make sure nobody is comparing the page with an older spreadsheet that used another rule.
- DORA inputs. DORA figures come from work items and pipelines. If a team deploys outside Azure Pipelines, say so in your note.
- The risk list. Read each risk yourself and add a sentence on what is being done, because leaders read actions before numbers.
Related: How carryover is counted · Measuring DORA metrics in Azure DevOps
One limit to know
Nothing rolls up across Azure DevOps organisations. If your teams are split across organisations, each one has its own report.
Related: One consolidated report for 10 teams
Try it
Agile Analytics runs on Azure DevOps Services (cloud). The 30-day free trial starts on install with no credit card, and everyone in the organisation has full access while it runs.
Related: Azure DevOps reporting · Install instructions