Guides, best practices, and deep-dives on sprint metrics, flow analytics, and data-driven agile coaching for Azure DevOps teams.
v6.16 removes a step from the trial-reminder signup flow. The prompt previously asked you to retype the email Azure DevOps already knows about you and click Send; v6.16 subscribes that address for you and shows a 60-second visible Undo banner instead. v6.16.1 also removes a duplicate feedback card from the dashboard so there's one clear path to reach us.
Read articlev6.15.6 is a small UX release that makes it easier to reach us from inside the extension. A persistent 👋 Ask Henry button now lives in the dashboard top bar, and the Help & Support page got reorganised from four cards into three clearly distinct paths: Ask Henry, Book a Call, Rate Us. Same CTA is now on the homepage and pricing page of the website too.
v6.15 is a focused release of customer-asked-for refinements. A new "Limit to current project" toggle on Live Stats and Sprint Summary scopes metrics to one project instead of every team across the org. The Cycle Time view's empty-state on brand-new ADO setups now reads as a friendly welcome instead of suggesting your workflow mapping might be broken. And Configuration sidebar badges clear in real time the moment an admin approves a user or saves a mapping change — no more page reloads to confirm an action worked.
6.14 is the release where workflow auto-discovery stops being an English-only tool. Italian, German, and French now classify out of the box, alongside the English / Spanish / Portuguese we already had. We also added a clear, in-product signal the moment a state name doesn't fit — no more silently wrong dashboards — and a one-time "want to re-run discovery?" prompt for teams already on an older mapping. Most of this came directly from customer feedback over the last six weeks.
v6.11.2 ships two reporting fixes customers raised during evaluation and adds zero new Azure DevOps permissions. Feature Analytics now respects the team scope you save in Configuration → Feature Filters end-to-end — the feature list itself trims to scope, not just the per-team aggregate table and Completed-SP totals. User Metrics gains a new Linked PRs column that counts pull requests attached to each user's assigned work items, populated from work-item relations so the upgrade is silent — no admin re-authorisation prompt. PR comment counts remain unavailable in this build and now render as an em-dash instead of a misleading zero.
The 6.8.x line completes the move to per-seat pricing — Team, Business, and Premium tiers that scale with your team count, not against it. The philosophy underneath is simple: every plan ships every feature, the trial is fully unlocked from day one, and we want to be on your side for years — not at a renewal cliff every twelve months. This is a longer read about what changed, why we chose per-seat over flat-rate, and how the product treats a two-person pilot the same way it treats a hundred-team enterprise rollout.
v6.7.0 brings the in-product side of the per-seat pricing model we rolled out on the website in May: a soft seat-usage banner appears in the hub when an org is over the limit for its tier, with the existing license remaining fully active. Behind the scenes, every license and telemetry call now travels with a JWT signed by the extension's own certificate (Microsoft's recommended auth model), and a stack of resilience fixes since 6.6.1 — chunk-error recovery on stale tabs, tighter input handling at every license endpoint, and a three-layer migration safety net. Founding / Annual / Monthly customers keep their existing plans byte-for-byte; nothing about your subscription changes.
v6.6.1 brings four flow-metrics upgrades at feature parity with the analytics suites coaches use in Vacanti / Wheeler workshops — without changing where you go or what you click. Cycle Time and Aging gain shaded percentile bands so the distribution is legible at a glance, and two new views land in Measure: Process Behavior (Wheeler XmR / SPC chart that separates routine variation from genuine process signals) and Cycle Time Heat Map (2D density of completion week × cycle band). Every change is additive — zero impact on existing data, mappings, or settings.
v6.5.9 lands three things customers asked for: a GitHub Copilot tab under Configuration → Admin so AI Metrics auto-connects on load (no more per-session Connect click), low/high AIIP thresholds with an optional Slack/Teams webhook, and a one-time, org-scoped admin email auto-capture (disclosed in the welcome modal, opt-out via Privacy). Plus a stack of behind-the-scenes licensing reliability fixes since 6.5.3.
v6.5.3 makes Workflow Mapping smarter: it reads your project's actual ADO state names (Agile "Active", CMMI "Resolved", Basic "Doing"/"To Do") and seeds the mapping accordingly, so Cycle Time, Flow Efficiency, and Monte Carlo render real data the first time you open them. Plus quieter handling of transient licensing-service hiccups in Configuration → License.
Versions 6.4.0 and 6.4.1 land the privacy-safe usage telemetry we've been talking about for a while: ten allow-listed event names, allow-listed property values, no work-item content, no user identities. The extension records what was used — not what was in it. The server rejects anything that isn't on the allow-list, so even a future bug in the client can't leak content.
Version 6.3.5 makes Next Sprint Planning available to every customer under Plan → Next Sprint Planning — a capacity- and Monte-Carlo-aware forecast that answers "what should we commit to next sprint?" from the team's own history and the upcoming sprint's Azure DevOps Boards capacity. The release also tightens Cycle Time so the chart admits when the data is unreliable instead of reporting a false floor, and bundles three customer-feedback features for AI Metrics.
Most Azure DevOps dashboards stop at work-item queries. Here is how to build a real delivery dashboard inside ADO that covers sprint health, flow metrics, and forecasting in one view your engineering managers will actually open.
Version 6.2.3 adds per-type filtering inside Cycle Time when multiple Azure DevOps work item types share an analytics category, renames the categories to Planned Work, Bugs, and Exploration, and shows a warning when work items have ADO types that aren't mapped into any category. Since 6.2.0 we've also shipped first-install auto-detection of work item types and a simpler Workflow Mapping tab.
A practical comparison of three Azure DevOps (ADO) reporting paths — the built-in reports, Power BI with the Analytics service, and Marketplace extensions like Agile Analytics — with rollout time, audience fit, and ongoing maintenance cost for each.
A guide to the Azure DevOps dashboard widgets that actually drive sprint conversations — sprint summary, velocity, burndown with commitment line, cycle time, throughput, and flow signals — and what to look for when choosing a widget set.
Version 6.1 ships a new Flow Efficiency view, Service Level Expectations on the Dashboard, and auto-discovery of custom Azure DevOps workflow states. Patches 6.1.1 and 6.1.2 add lenient state-name matching, a heuristic fallback for fresh installs, and clearer empty-state diagnostics.
Major release: explicit N/A workflow mapping, smarter Blocked detection, deep-linked Sprint Capacity, and full dark mode coverage for configuration and capacity panels.
Agile Analytics is expanding for Jira users with the same focus on sprint reporting, flow visibility, forecasting, and practical rollout clarity that Azure DevOps teams already use today.
Every engineering leader using GitHub Copilot Enterprise is being asked the same question right now: is it actually working? Here's how to get adoption metrics directly inside Azure DevOps — where your engineering workflow already lives.
Agile Analytics now uses a simpler org-level pricing model: one plan for your whole Azure DevOps organisation, a 30-day free trial, and a license key after purchase.
Version 4.0 is the first major release of Agile Analytics. It adds company-wide AI adoption analytics (AI Metrics), an admin-only AI Improvement & Intervention Panel (AIIP), and three Azure DevOps dashboard widgets. The largest feature drop since launch.
Version 4.0 adds company-wide AI adoption tracking and an admin intervention panel directly inside Azure DevOps. Monitor Copilot and AI tool usage across every team, surface at-risk users automatically, and route Teams alerts — all without leaving ADO.
Version 3.8 ships a complete UI overhaul: a collapsible sidebar replaces the horizontal tab strip, a sticky 48px header bar consolidates controls, a full-screen command palette lands on Ctrl+K, and the Configuration panel moves to a vertical side-nav. Every new element is fully dark-mode covered.
Version 3.7.2 ships configurable Item Type Mapping for any ADO process template, Sprint Summary dark mode, and two commitment-lock accuracy fixes in the Sprint Summary scope change tile.
Version 3.7.2 introduces Item Type Category Mapping — a new configuration tab that lets you tell the extension which of your ADO work item type names count as stories, bugs, and research. Works with Scrum, CMMI, SAFe, Agile, and fully custom process templates.
In 3.7.2, all Sprint Summary metric tiles, breakdown cards, team card headers, and state panels are now correctly themed for the Azure DevOps dark colour scheme. No more light-on-dark clash in your sprint views.
Two edge cases in the Sprint Summary commitment lock (end of Day 2) have been fixed in 3.7.2. The scope change tile no longer shows a false +1 before Day 2 ends, and the removed-items panel no longer shows items that were removed before the lock was set.
Version 3.6.0 brings rich interactive tooltips to the Cycle Time Scatterplot, smarter setup-banner behaviour for returning users, org-wide workflow-mapping recognition, and accurate cycle/lead-time values in every tooltip mode.
Every dot on the Cycle Time Scatterplot now opens a rich detail card on hover — work item title, type, cycle time, lead time, active date range, and a direct link to Azure DevOps. No more squinting at axis values.
In 3.6.0, admins and approved users no longer see the "Required Setup" banner when switching between projects in the same Azure DevOps organisation. Onboard once, work freely across all your projects.
The setup checklist in 3.6.0 now recognises workflow mapping configured in any project across your organisation. Admins no longer need to re-acknowledge the mapping step every time they switch to a new project.
A subtle display issue in 3.6.0 is fixed: when the Cycle Time Scatterplot was in Lead Time axis mode, the tooltip was labelling lead days as "Cycle Time". Both values are now always independently correct, regardless of which mode the chart is in.
Access control is now available across all plans. Starter and Pro include admin claim plus access-request approvals, while Business and Enterprise continue to add role-based view permissions.
Three new widgets — Team Health, Cycle Time, and Throughput — let you see the state of your sprint without opening the analytics hub. Here is how they work and how to set them up.
Sprint Summary gives your team a complete, accurate picture of each sprint — commitment, scope change, carryover, and removed items — derived from revision history rather than current board state.
The new Cumulative Flow Diagram replays your work item state history day by day to produce a stacked area chart that reveals WIP accumulation, throughput drops, and queue build-up across six workflow stages.
Multi-Team Aging shows aging work-in-progress across all your teams on a single screen — purpose-built for agile coaches and delivery managers who oversee more than one squad.
The Audit Trail view shows a per-sprint, per-work-item timeline of every state change — with timestamps, durations, and expandable event detail. Built for sprint reviews and retrospectives.
The new Data & Privacy view documents exactly what the extension accesses and stores — no external data transmission, no backend server, read-only ADO access. Built for procurement reviewers and security-conscious rollouts.
Dashboard widgets, four new analytics views, a reorganised navigation, and 211 automated tests. Here is everything that landed in 3.1.5.
Version 2.5.1 is a major redesign of Feature Analytics — individual feature list, live filter bar, quarterly heatmaps by team and product area, SP trend chart, and process-agnostic field mapping configuration.
Version 2.4.0 improves multi-team scalability, team selection UX, Agile Coach visibility, and cross-view performance for larger Azure DevOps organizations.
Version 2.3.2 of Agile Analytics adds two new Configuration tabs that make it easier to validate a new install and diagnose issues — Customer Readiness and Support Diagnostics.
If your sprint and flow numbers feel off, workflow mapping is usually the root cause. Here is how to map Azure DevOps states so Agile Analytics reports match how your team actually works.
Carryover is one of the clearest signs that sprint commitments are drifting from delivery reality. Learn how to reduce it without shrinking ambition or teaching teams to sandbag.
Daily standups get much more useful when the team focuses on aging work instead of reciting every ticket. Here is how to use item age as a practical delivery signal inside Azure DevOps.
P50, P85, and P95 forecasts answer different business questions. This guide helps Azure DevOps teams choose the confidence level that fits the decision instead of defaulting to one date for every audience.
The AI Agile Coach feature uses GPT-powered analysis to turn your sprint data into actionable coaching insights, retrospective summaries, and proactive alerts — without any manual data interpretation.
A step-by-step guide to installing Agile Analytics from the Visual Studio Marketplace, configuring it for your Azure DevOps project, and getting your first sprint metrics in minutes.
Monte Carlo simulation gives you probabilistic delivery forecasts based on your team's actual historical throughput. Learn how Agile Analytics uses it to answer "when will we be done?" with confidence.
Cycle time and WIP (Work In Progress) are the two most powerful flow metrics for identifying bottlenecks and improving delivery throughput. Here is how to read and act on them.
Sprint velocity and burndown are the two most fundamental agile metrics. Learn what they measure, why they matter, and how Agile Analytics enhances them beyond the built-in Azure DevOps reports.
Agile Analytics is an Azure DevOps-native extension that gives your team real-time sprint and flow visibility without sending data to any external server. Learn how it works under the hood.