Yes. Azure DevOps already has burndown, velocity and cumulative flow reports built in, and an extension such as Agile Analytics adds what teams coming from Jira tend to miss most: a sprint report built around commitment, scope change and carryover, and a cycle time chart with percentile lines.
What people usually mean by "the reports"
Jira boards come with a familiar set of agile reports: a burndown or burnup, a velocity chart, a cumulative flow diagram, a control chart for cycle time, and a sprint report. Most of these exist in Azure DevOps, spread across the sprint backlog, the board and dashboard widgets rather than collected in one place.
The five reports, side by side
Here is where each one lives.
| Report | Built into Azure DevOps | Agile Analytics adds |
|---|---|---|
| Burndown or burnup | Sprint burndown, plus dashboard widgets | A Sprint Burndown card on the Dashboard, with Items and Story Points |
| Velocity | Velocity report and dashboard widget | Flow Metrics, Delivery Signals and a Sprint Velocity card covering the last 6 sprints |
| Cumulative flow | On the board, plus a dashboard widget | The Cumulative Flow view |
| Cycle time control chart | Cycle time and lead time dashboard widgets | A Cycle Time scatterplot with p50, p70, p85 and p95 lines, and a histogram |
| Sprint report | No single page: teams combine the burndown with queries | Sprint Summary: commitment, scope change, carryover, planned work and bugs |
Related: The velocity chart · Reading a cumulative flow diagram
When the built-in reports are enough
They are a reasonable place to start. A team on a single board with a standard process, which mainly wants a burndown at standup and a velocity number for planning, may not need anything else. If all you want is a next-sprint forecast on a dashboard, the separate Monte Carlo Sprint Forecast extension is free, with no account, trial or licence key. Try the built-in reports for a couple of sprints. Once you know which questions they leave unanswered, you will know whether an extension is worth adding.
The sprint report
This is the gap teams notice first. Sprint Summary answers what you committed to, what got done, and what changed mid-sprint.
- Committed work is what was in the sprint at the end of its first day, measured in UTC.
- Anything added later shows under Scope Change, listed by the day it arrived.
- Carryover follows one documented rule. An item moved back to the backlog unfinished is removed scope, not carryover.
- With two or more teams selected, a Teams at a glance table sits above the cards.
Related: How to see scope change during a sprint · How carryover is counted
Cycle time beyond the average
When someone asks when something will be done, a percentile is usually more useful than an average. The Cycle Time view draws percentile lines, and SLE Violations lists completed items that missed their service level expectation, worst first. Aging & Blocked plots every item still in progress against the team's p50 and p85, so you can see which are getting old before they finish late.
Custom workflows and several teams
Teams coming from Jira often bring many custom states. Agile Analytics works with Agile, Scrum, CMMI, Basic and custom inherited processes, and an admin can check where each state belongs under Tools, Configuration, Workflow Mapping. For several teams, Sprint Summary, Team Benchmarks, Multi-Team Aging and the Exec Report can include teams from other projects in the same organisation.
What it needs
It reads the work items already in your organisation, so reports reflect the history that exists there.
- Platform: Azure DevOps Services (cloud) only. Azure DevOps Server is not supported.
- Access: Project Contributor or higher, and a modern browser.
- No extra infrastructure: no Power BI, Analytics views or personal access token.
- Data handling: views run in your browser with your existing session, using four read-only scopes. Work-item content is never sent to a Baytek server.
Related: Security and data handling
Try it
The 30-day free trial starts on install with no credit card, and everyone in the organisation has full access while it runs. After that it is from $300 a year per organisation, with every feature on every plan. Compare it with the built-in widgets for a sprint or two.
Related: Azure DevOps sprint reporting · Install instructions