Agile Analytics — Sprint Intelligence for Azure DevOps

Stop copying data into spreadsheets. Stop waiting for a weekly report. Get the sprint intelligence your team needs, live inside Azure DevOps — zero infrastructure with fast first-time setup.

Agile Analytics is a project hub extension that turns your existing Azure DevOps work items, sprints, and iteration data into 15+ interactive analytics views plus built-in readiness and support diagnostics. Core analytics run directly from your ADO organization data with no publisher-hosted analytics backend. Data leaves your tenant only when you explicitly enable optional external integrations (AI providers or webhook notifications).

Product Updates

Latest release (March 13, 2026): Agile Analytics 2.6.4 — Release Notes

Pricing & Licensing

Agile Analytics uses per-user pricing through the Visual Studio Marketplace — the same mechanism as all paid Azure DevOps extensions. No separate billing system or backend required.

Every plan includes real analytics. Upgrade to expand how many teams and projects you can work with at once.

Plan	Price	Teams	Projects
Starter	Free forever	1 team	1 project
Pro	$5 / user / month	Up to 3 teams	1 project
Business	$10 / user / month	Up to 10 teams	3 projects
Enterprise	$20 / user / month	Unlimited	Unlimited

Licence assignment: Org admins purchase seats through Visual Studio Marketplace and assign them to users via Extensions → Assigned licences in ADO organisation settings. Individual users do not need to register or purchase — access is granted through the admin's assignment.

Who Is This For?

Role	What you get
Scrum Master	Live sprint health, commitment reliability, scope churn alerts, and coaching questions auto-generated per team
Engineering Manager	Multi-team velocity comparison, cycle time trends, flow efficiency, and team leaderboard
Agile Coach	Configurable health thresholds, prioritized action items (P1/P2/P3), and a retro snapshot you can export to PowerPoint in one click
Product Owner	Feature delivery progress, Epic/Feature completion with child story rollups, and Monte Carlo forecast dates
Developer	Personal metrics: PRs merged, review participation, work items closed — across any sprint range

The Problem It Solves

Azure DevOps has powerful raw data but no built-in views for:

Cycle time trends across past sprints with statistical percentiles
Monte Carlo simulation for probabilistic "when will we be done?" answers
Cross-team scope completion in a single view
Flow efficiency — how much of lead time is actual work vs. waiting
Coaching-ready insights — which teams are at risk and what to ask them

Agile Analytics fills every one of these gaps without leaving Azure DevOps.

Views at a Glance

Dashboard — Sprint KPI summary with velocity, burndown, WIP, and delivery grade

Sprint Health

View	What it shows
Dashboard	Sprint KPI summary card: velocity, cycle time, burndown status, WIP count, and delivery grade
Live Stats	Real-time item counts by workflow state for the active sprint — refreshes on every open
Multi-Team Scope	Side-by-side completion % across all your teams in one scrollable view
Delivery Signals	Commitment reliability %, scope churn %, and carryover rate per team with trend direction

Flow Analytics

WIP Monitor — Active items with age and configurable team WIP limits

View	What it shows
WIP Monitor	Active items with age in days, configurable team WIP limits, and breach alerts
Flow Metrics	Throughput, lead time, and flow efficiency trends over rolling 4/8/12-week windows
Aging & Blocked	Items exceeding configurable age thresholds, with blocked items flagged separately
Cycle Time	Interactive scatterplot — completion date vs. days-to-complete, with P50/P85 percentile lines
Monte Carlo	Run 10,000 simulations on historical throughput — get P50/P85/P95 delivery date estimates

Flow Metrics — Throughput, lead time, and flow efficiency trends

Cycle Time — Interactive scatterplot with P50/P85 percentile lines

Portfolio

View	What it shows
Team Leaderboard	Normalized ranking across all teams: velocity, reliability, scope discipline
Feature Analytics	Epic and Feature cards with live child-story completion bars and rollup counts

Monte Carlo Forecasting

Monte Carlo — 10,000-run simulation returning P50/P85/P95 delivery date estimates

Agile Coach

View	What it shows
Agile Report	Multi-team health grid with configurable goals, status badges (On Track / At Risk / Critical), and auto-generated P1/P2/P3 coaching action items
User Metrics	Per-contributor view: PRs merged, code reviews given, work items closed — filterable by sprint range

Tools

View	What it shows
Retro Snapshot	One-click PowerPoint export of the current sprint summary, ready for your retro
AI Assistant (optional)	Ask natural language questions about your sprint data by connecting your own Claude or OpenAI key with explicit usage limits
Configuration	WIP limits, workflow state mappings, sprint transition alerts, notification webhooks, background monitors, access control, readiness checks, support diagnostics export

Dark mode — Full dark theme, one-click toggle, persisted per user

Key Differentiators

No infrastructure required Everything runs in the browser against your live ADO data. No Azure Function, no database, no service connection to configure. Install, complete Access Control claim plus Workflow Mapping once, and it works across your organization.

Built-in customer diagnostics Configuration includes a Readiness report to validate whether a customer org has the data and mappings needed for each dashboard, plus a Support Diagnostics export that keeps sanitized logs inside the customer's Azure DevOps tenant until they choose to share them.

Monte Carlo forecasting — built in Enter your remaining backlog size, pick a confidence level, and get a forecast date backed by your own team's historical throughput. Not a guess — a simulation.

Role-based access control Built-in Admin/User role system with ADO directory search. Admins can keep the extension open to all project users, or switch to assigned-users-only mode for tighter rollout control.

Retro-ready exports Export any sprint summary to a branded PowerPoint slide deck in one click. Paste into your retro deck without formatting work.

AI that uses your actual data When the AI Assistant is enabled, it reads your live sprint report before answering — not generic advice, but answers grounded in your team's actual numbers.

Background Monitor — proactive WIP alerts without the browser open Configuration generates the pipeline YAML for you. Your admin adds it to a repo in your ADO organization, then Azure Pipelines runs it on your chosen cron schedule, checks WIP limits, and fires a Teams or Slack notification automatically — even when no one has the extension open. No external infrastructure, no publisher-hosted servers — the pipeline runs entirely within your tenant.

Dark mode Full dark theme — persisted per user, toggleable with one click.

Getting Started in Under 2 Minutes

Step 1 — Install Open the Marketplace listing, review the plan that fits your organisation, then install the extension into your Azure DevOps organization.

Step 2 — Open Navigate to any project. Find Agile Analytics in the left hub navigation bar (under your project name).

Step 3 — Claim Admin Access (Required) An Azure DevOps Project Administrator or Organization Administrator must go to Tools → Configuration → Access Control and click Claim Admin Access.

Step 4 — Configure Workflow Mapping (Required) Go to Tools → Configuration → Workflow Mapping, then map your Azure DevOps board states to your analytics flow stages based on your company's process, and save.

Step 5 — Select your team and explore Use the team selector in the top-left corner, then browse views using the top navigation. Starter lets each user work with one selected team in one project at a time while still browsing all projects and teams from the toolbar. Pro expands to up to 3 teams in 1 project and adds Team Leaderboard. Business expands to 10 teams across 3 projects and unlocks Access Control plus custom workflow mappings.

Optional — Additional setup After required setup is complete, visit Tools → Configuration to set WIP limits, add Teams/Slack webhook alerts, run Readiness checks, and export Support Diagnostics.

For correct analytics behavior in customer environments, complete Access Control claim and Workflow Mapping before broad team rollout.

Access Control

Agile Analytics ships with a lightweight built-in role system — no Azure DevOps group configuration required.

How it works:

An Azure DevOps Project Administrator or Organization Administrator visits Configuration → Access Control and clicks Claim Admin Access
Admin chooses whether the extension is open to All project users or restricted to Assigned users only
Admin adds users by searching the ADO directory and assigning them Admin or User roles
Admin configures which views are visible to User-role members
Admins always see every view regardless of settings

Settings are stored at organization scope in Azure DevOps Extension Data Service — one configuration shared across all users in the org.

Access Control in this extension controls in-app view visibility and feature access. It does not replace Azure DevOps native permission and repository security models.

AI Assistant (Optional)

The AI Assistant is disabled by default and completely optional. When enabled:

Ask natural language questions: "How did Team Alpha perform this sprint?"
It reads your live sprint data before answering — not generic responses
Connect Anthropic Claude, OpenAI, or GitHub Copilot with your own organization-managed API key
Configure provider, model, per-session request limits, and output token limits before enabling it
Admins can disable it org-wide via Configuration → Access Control

Data sent when AI is active: your prompt + sprint name + team name + aggregated metrics (point counts, percentages). Work item titles and user names are never included automatically.

Notification Alerts

Connect to Microsoft Teams or Slack to receive automatic alerts. Seven configurable triggers are organised into three groups:

Sprint Health

Commitment Reliability Low — fires when sprint commitment reliability drops below your configured threshold
Scope Churn Exceeded — fires when mid-sprint scope changes exceed your churn threshold
Carryover Risk — fires when the share of incomplete work being carried over to the next sprint is too high
Sprint End Summary — a one-time digest sent at the end of each sprint summarising key delivery metrics

Flow & WIP

WIP Over Limit — fires when any team column exceeds its configured WIP limit
Stale In-Progress Items — fires when work items have been in progress for more than 5 days without a state change

Digest

Weekly Sprint Digest — a once-per-week summary of sprint health and flow status sent to your channel

Configure in Tools → Configuration → Notifications. Enable each channel independently, paste your webhook URL, select the triggers you care about, and save. Webhooks use HTTPS only and are validated against official Teams and Slack endpoint formats.

In-session vs Background: The alerts above fire when a user opens the extension (at most once per browser session). For automated alerts that run without anyone having the browser open, see the Background Monitor section below.

Background Monitor — Alerts Without the Browser Open

Standard webhook alerts fire when a user has the extension open. The Background Monitor goes further: Configuration → WIP Settings generates a YAML file for your Azure Pipeline. After your admin adds that file to a repo and creates the pipeline, it runs on a cron schedule you choose (e.g., every weekday morning), checks WIP limits across your teams, and posts a notification to your Teams or Slack channel automatically — even if nobody has Azure DevOps open.

Zero external infrastructure — the pipeline runs entirely within your ADO organization
One-click setup — select a repo, click "Setup Background Monitor", done
Fully auditable — the YAML pipeline file is committed to your repo; you can inspect and modify it at any time
No PAT required — uses Azure Pipeline's built-in service account

The same pattern is now available for Sprint Alerts: create a scheduled pipeline from Configuration → Sprint Alerts to watch the current sprint for meaningful status transitions such as entered in progress, entered review, entered done, reopened, or blocked. Each run posts one grouped summary instead of spamming one message per work item.

Permissions Explained

We request only what we use:

Permission	Why
`vso.project`	Read your project list and team roster for the team selector
`vso.work`	Read work items, sprint iterations, and work item history for all analytics views
`vso.graph`	Search the ADO user directory only when an admin adds a user in Access Control — never used otherwise

Requirements

Azure DevOps Services (cloud) — any tier
Project Contributor access or higher
Modern browser (Edge, Chrome, Firefox)
Azure DevOps Server (on-premises) — not supported in this version

FAQ

Does this extension store my data anywhere? No. All data is read live from your Azure DevOps organization and rendered in the browser. The extension publisher has no server, no database, and receives no data at any time. Settings (WIP limits, preferences, access control) are stored in your org's Azure DevOps Extension Data Service — Microsoft-managed infrastructure.

Will my settings be lost when a new version of the extension is installed? No. As of v2.3.0, all settings (WIP limits, workflow mappings, notification webhooks, AI configuration, access control, and user preferences) are stored using the Azure DevOps Extension Data Service key-value API, which is version-agnostic. Upgrading the extension will never reset your configuration.

Does it slow down Azure DevOps? No. The extension makes the same REST API calls you would make manually — one view at a time, only when you navigate to it. There is no background polling, no persistent connections. The optional Background Monitor uses a standard Azure Pipeline scheduled trigger — the same mechanism any CI pipeline uses.

What is the Background Monitor and how does it work? It is an Azure Pipeline you add inside your own ADO organization using the YAML file downloaded from Configuration. The extension generates the YAML, your admin adds it to a repo, and Azure Pipelines runs it on your chosen schedule using System.AccessToken. Everything runs in your ADO tenant — nothing goes through publisher servers.

Why do I see no data on Cycle Time or Flow Metrics? These views require completed past sprints with items in a Done/Closed/Resolved state. If your team just started or uses custom "done" state names, visit Configuration → Workflow Mapping to map your states.

Do I need to configure anything before rollout? Yes. For correct behavior, an Azure DevOps admin should first claim admin access in Configuration → Access Control, then complete Configuration → Workflow Mapping for your process states. After that, teams can use Dashboard and Live Stats immediately while advanced analytics improve as sprint history grows.

How do I set up the AI Assistant? Go to Configuration → AI Settings. Select Claude, OpenAI, or GitHub Copilot, enter your own API key (or GitHub token for Copilot), set usage guardrails, then enable the assistant and save.

Can I control who sees what? Yes — through the built-in Access Control. Admins can choose open access for all project users or restrict the extension to assigned users only, then control which views regular users can see.

Does it work across multiple projects? The extension installs at the organization level and is available in every project. However, each project view loads data for that project only — there is no cross-project rollup in this version.

Is dark mode supported? Yes. Click the theme toggle button in the top-right of the navigation bar. Your preference is saved per user via Azure DevOps Extension Data Service.

What happens if I uninstall? Your ADO work items, sprints, and boards are completely unaffected — this extension only reads your data, never writes to work items. Extension Data (settings, access control, preferences) is deleted when the extension is uninstalled.

Data & Privacy

This extension collects zero telemetry. No usage events, no error reports, and no analytics are sent to the publisher. All settings and support diagnostics are stored exclusively in your Azure DevOps Extension Data Service unless you explicitly export and share them.

The only time data leaves your tenant is when you optionally enable the AI Assistant and send a prompt — in which case aggregated sprint metrics are sent to the AI provider you selected (never to the publisher).

Agile Analytics

Baytek