Agile Analytics 6.0.0 Release Notes
Major release: explicit N/A workflow mapping, smarter Blocked detection, deep-linked Sprint Capacity, and full dark mode coverage for configuration and capacity panels.
Read articleGuides, best practices, and deep-dives on sprint metrics, flow analytics, and data-driven agile coaching for Azure DevOps teams.
Major release: explicit N/A workflow mapping, smarter Blocked detection, deep-linked Sprint Capacity, and full dark mode coverage for configuration and capacity panels.
Read articleAgile 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.4 is a hardening release focused on correctness, accessibility, CI quality gates, safer defaults, and developer-tooling cleanup across the extension.
Version 2.5.2 redesigns the Feature Configuration tab by replacing the legacy visual filter builder with a focused Enterprise Scope picker, simplified Team Scope controls, and preserved field mappings.
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.9 improves Feature Analytics scope matching for multi-team environments and reinforces the required setup path that protects dashboard data accuracy.
Version 2.4.5 expands enterprise multi-team analytics across projects, improves team-activity clarity, and aligns portfolio metrics with configured Live Stats scope.
Version 2.4.2 improves workflow-stage clarity, hardens cycle-time data quality, and adds cross-project multi-team scope usability.
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.