Azure DevOps can export a work item query to CSV, but that file holds raw work items, not sprint metrics, so you still have to work out carryover, throughput and cycle time yourself. To get the metrics themselves as CSV, open the matching view in Agile Analytics and use its CSV export: one file per dataset, with one row per sprint, team, day or item depending on the view.
What a query export gives you, and what it does not
Run a work item query, export the results, and you get one row per work item with the columns you picked: ID, title, state, iteration path, story points. That is useful, but it is not a sprint report. There is no commitment figure, no carryover, no throughput per sprint, no cycle time percentile and no state history. Rebuilding those in Excel or Power BI takes time every sprint, and every team rebuilds them a little differently.
Related: Azure DevOps reporting: built-in vs Power BI vs extensions
Which view exports which CSV
Each view exports its own dataset. The row grain matters more than the file name, because it decides how you pivot or chart the file.
| View | One row per |
|---|---|
| Sprint Summary | Sprint per team |
| Flow Metrics | Sprint |
| Delivery Signals | Sprint |
| Cumulative Flow | Day |
| WIP Monitor | Team (current WIP), or sprint (WIP history) |
| Aging & Blocked | In-flight item, or blocked item |
| Flow Efficiency | Finished item |
| Live Stats | Team in scope |
| Sub-teams | Sub-team, then the parent team, then the total |
| Exec Report | Team |
| DORA Metrics | Window (summary), or week |
| Org Hygiene | Stale item, inactive team, or empty iteration |
| Audit Trail | State transition |
Step by step
The steps are the same in every view.
- Open Agile Analytics under Boards in your project.
- Pick the view whose row grain you need, from the table above.
- Select the team or teams and, where the view asks, the sprint range.
- Use the view's CSV button. In Sprint Summary, each team card has Download CSV, and Download All exports every team at once. In the other views, look for Export CSV or Download CSV.
- Save the file. Names follow the dataset and the date, for example
flow-metrics-2026-11-04.csv, so repeated exports sort by date in a folder.
What is in the sprint file
The Sprint Summary file uses the same sprint columns as the Dashboard's sprint export, so one spreadsheet can read either: team, project, sprint, sprint_start, sprint_end, committed, completed, reliability_pct, scope_churn_pct, items_added, items_removed, carryover_count, carryover_pct, throughput, and cycle time and lead time in days (average, p50 and, for cycle time, p85).
- Carryover in the file follows the product's one carryover rule. A running sprint has no carryover yet, so leave it out of carryover charts.
- The Sub-teams file counts every item once, so its total row does not double count work shared between the parent and its sub-teams.
- Live Stats shows demo data when no team is selected. Pick your teams before you export.
- Audit Trail is in the Extra group of the sidebar, which is collapsed by default.
Related: How carryover is counted
Where the file is built
The CSV is built in your browser from the Azure DevOps REST API, with your existing session; work-item content is not sent to a Baytek server to make it. A CSV contains only your data, with no attribution line, so it drops straight into a pivot table. The column lists are kept stable on purpose, so a spreadsheet that reads them keeps working from one export to the next.
Tips for working with the files
A few habits make the exports easier to use.
- Pick the grain first. Per-sprint files (Sprint Summary, Flow Metrics, Delivery Signals) suit trend charts. Per-item files (Aging & Blocked, Flow Efficiency) suit finding outliers.
- Keep the dated files. A folder of weekly exports becomes a simple history with no extra tooling.
- One organisation per file. Nothing rolls up across Azure DevOps organisations: each installs the extension separately, and the views read the organisation you are signed in to.
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. More on the sprint numbers behind the files is on the sprint reports page, and the extension is on the Azure DevOps Marketplace.
Related: Sprint reports: scope and carryover · Install instructions