Azure DevOps sprint reporting, dashboards, and forecasting without Power BI

Agile Analytics is an Azure DevOps extension that adds Next Sprint Planning, sprint health, flow metrics, DORA metrics, and Monte Carlo forecasting to Azure DevOps Services (cloud). 30-day free trial with no credit card, then from $300 a year per organisation; every feature on every plan.

Install from MarketplaceSee it in action
5.0 on Azure Marketplace
Agile Analytics dashboard inside Azure DevOps showing cycle time percentiles, work in progress, and sprint flow metrics
Real, unedited screenshot of our demo organisation (Payments Platform project, sample data), version 6.75.1, captured 2026-10-08.
  1. Lives in your project’s left menu, next to Boards and Pipelines
  2. Cycle time with sample size and a data-quality grade
  3. Current WIP for the selected team and sprint
  4. A “How many?” forecast at 95, 85, 70 and 50% confidence

One price per organisation · Unlimited projects · 30-day free trial

Three questions a sprint planning meeting asks

  1. Agile Analytics Monte Carlo view inside Azure DevOps, demo organisation, unedited screenshot

    How many items will we finish by the 30th?

    Pick a target date and the forecast reads your own throughput: here 16 or more items at 95% confidence and 19 at a coin flip, from 10,000 simulated runs over the last 6 sprints. The distribution chart below shows how likely each count is.

    Find it under Plan › Monte Carlo

  2. Agile Analytics WIP Monitor view inside Azure DevOps, demo organisation, unedited screenshot

    Who is over their WIP limit?

    One line answers it: 1 of 2 teams is over its WIP limit. Checkout Team runs 6 items against a limit of 5, 120% utilisation; Payments Team sits at 5 of 7 and reads healthy.

    Find it under Health › WIP Monitor

  3. Agile Analytics Cycle Time view inside Azure DevOps, demo organisation, unedited screenshot

    How long does work really take?

    Every completed item is a dot on the day it finished. For Payments Team, 53 items in scope: a typical item takes 7.7 days (p50) and 85% finish within 12.5 days, against a 10-day target.

    Find it under Plan › Cycle Time

All Features Included

Every feature on every plan

Agile Analytics is licensed per Azure DevOps organisation. Pick the number of seats that fits your team. Every plan unlocks the full product.

  • Next Sprint Planning

    Capacity- and Monte-Carlo-aware recommendation for what your team can realistically commit to next sprint, with cycle-time reality check, backlog risk scan, and commitment reliability, all read from your existing Azure DevOps Boards data.

  • Flow metrics that stay inside Azure DevOps

    Track cycle time, cumulative flow, WIP pressure, and throughput without exporting your delivery data into another reporting stack.

  • Monte Carlo forecasting

    Run probability-based forecasts from your own throughput history so delivery conversations are grounded in confidence ranges, not guesses. Built-in Azure DevOps reporting stops at averages and standard deviations.

  • Sprint intelligence

    See velocity, scope change, carryover, burndown, team health, and alerts in one place for every team in the organisation.

  • Sprint capacity planning

    Read sprint dates, working days, days off, and per-member capacity directly from Azure DevOps Boards to calculate effective capacity and recommended commitment.

  • AI adoption analytics

    Track GitHub Copilot adoption across every team: active users, acceptance rates, team leaderboards, and an admin panel for acting on the signal.

  • Operational alerts

    Catch WIP breaches, stale work, sprint risk, and weekly digest events early through built-in notifications and monitoring.

  • Stakeholder-ready exports

    Export any chart to PNG and any table to CSV, and build shareable sprint summaries for stakeholder reviews and leadership reporting, straight from the views your team already uses.

Shipped recently

6.75.1
November 2026Ask your own AI assistant about your numbers, on your own computer.
6.74.1
November 2026Three new ways to see your delivery: Epic Timeline, Quality & Rework, and what changed since your last visit.
6.72.0
November 2026Retro Snapshot counts carryover the same way as your other views.

Release notes

Details

Runs
In your browser, inside Azure DevOps. Azure DevOps Services, not Azure DevOps Server.
Permissions
Four read-only Azure DevOps scopes: vso.project, vso.work, vso.graph, vso.build
Your work items
Stay in your Azure DevOps tenant. Baytek does not receive work-item content. What we receive
Trial
30 days, every feature, for everyone in your organisation.
Price
One price per organisation, from $300/year.
Version
6.75.1, November 2026

See the dashboards your teams will actually use

From sprint summaries to flow analytics and forecasting, the full experience lives inside Azure DevOps from trial through paid activation.

Agile Analytics Dashboard view inside Azure DevOps: Sprint health at a glance: cycle time percentiles, work in progress, lead time and throughput, all read from the Boards data you already have.
Dashboard · Overview · Sprint health at a glance: cycle time percentiles, work in progress, lead time and throughput, all read from the Boards data you already have.

Pricing

Pricing that grows with your team

Team
2 seats included
$300/year
Business
6 seats included
$1,200/year
Premium
Unlimited seats
$2,000/year

One flat price per organisation. You're never charged per user. See how it compares to per-user pricing →

View PricingInstall from Marketplace

Product paths

Choose the product experience that matches your platform

Azure DevOps and Jira editions are priced and trialled separately, and Copilot Metrics and Testaro are their own products. Pick the one that matches your platform and problem.

  • Agile Analytics for Azure DevOps

    Azure DevOps · Trial + Paid

    The commercial edition: 30-day trial, one price per organisation, and every sprint and flow view.

    View pricing →

  • Agile Analytics for Jira

    Jira · Free during beta

    The Jira Cloud edition: sprint intelligence, aging charts, flow metrics, and forecasting.

    Explore Jira edition →

  • Copilot Metrics

    GitHub Copilot · AI adoption analytics

    GitHub Copilot adoption, engagement, and seat usage for teams on Azure DevOps or Jira.

    Explore Copilot Metrics →

  • Testaro

    Azure DevOps · Early access · Free

    Native test management for Azure DevOps: author cases, run suites, and report on quality without leaving your ADO tenant or paying per tester.

    Explore Testaro →

Explore by use case

Start with the delivery problem you want to solve first

Browse targeted pages for sprint reporting, flow analytics, forecasting, WIP control, and buyer comparisons. Browse use cases · Browse comparisons

From the blog

Practical rollout guidance for Azure DevOps teams

Three recent posts. Browse all articles →

Start here

Common questions

What counts as a seat?

A seat is an assigned place on your plan. Your extension admin assigns people in Configuration → Access Control; assigned users, including admins, each hold one seat. The Team plan includes 2 seats, Business includes 6, and Premium is unlimited. You can swap seats at any time by removing someone and assigning someone else. During the trial there are no seats: everyone in your organisation has full access.

What happens if my team grows past my seat count?

You can never be billed for more than your plan. When every seat is assigned, new assignments are simply refused until you remove someone or upgrade. Everyone without a seat still sees the Dashboard and can request a seat from your admin in one click.

Which plan should I pick?

Pick Team if a few people on one squad will open the reports, Business if you have a full delivery team or two, and Premium if you want every Azure DevOps user in your org to be able to look at the metrics whenever they like. For example, if two people such as a Scrum Master and a Product Owner will open the reports, the 2 seats on Team cover them, as long as no one else is assigned a seat (assigned admins hold a seat too). Everyone else in the organisation still sees the Dashboard, and during the 30-day trial everyone has full access, so you can see who actually opens the reports before you choose.

What counts as an "organisation"?

One Azure DevOps organisation (for example, dev.azure.com/your-org). The extension is installed at organisation level, so the seat count is scoped to that organisation. Each subscription covers a single organisation, and your license key locks to the first organisation it is activated in. If you run more than one organisation, each needs its own subscription.

Who's behind it

Hi, I'm Henry Sword

I'm Henry Sword, and I lead Agile Analytics. I started it because the teams I coached kept exporting Azure DevOps to spreadsheets to answer "when will it be done?". It is installed in more than 100 Azure DevOps organisations, and I read every message that comes through the form.

Henry Sword, Baytek · Ask Henry, personal reply within one business day

Ready to start the 30-day trial?

Install from the Azure Marketplace, use every feature with your whole organisation, and activate your license key only when you're ready to keep going.

Start Free TrialView pricing

30-day free trial • Then from $300 a year per organisation • Every feature on every plan