October 28, 20262 min read
Agile Analytics 6.65.9: AGAN AI links the views it mentions, and its button has a new mark
AGAN AI links the views it mentions, and its button has a new mark.
Release Notes · Featured
Blog
Guides, best practices, and deep-dives on sprint metrics, flow analytics, and data-driven agile coaching for Azure DevOps teams.
Filter:AnnouncementsConfigurationRelease NotesFlow AnalyticsProductSprint HealthGetting StartedAI FeaturesFeaturesSprint AnalyticsForecastingAgile Coach
October 28, 20262 min read
AGAN AI links the views it mentions, and its button has a new mark.
Release Notes · Featured
October 28, 20263 min read
AGAN AI now explains the numbers on the view you are on, and asking it a question is the first thing you see.
October 28, 20262 min read
During a free trial, every member of the organisation gets straight into the hub, and the AGAN AI button now says what it is.
October 26, 20269 min read
An epic is a large initiative, a feature is a shippable piece of it, and a user story is one unit of value a team finishes in a sprint. Here is the hierarchy with an example, the rules Azure DevOps enforces, and why Epics go missing.
October 26, 20268 min read
Only the Agile process has a field called Story Points: Scrum calls it Effort and CMMI calls it Size. Here is where each lives, why tasks carry hours instead, and the four built-in ways to add points up.
October 26, 20268 min read
A WIP limit in Azure DevOps is a number you type into a board column. When the column holds more, the count turns red; nothing is blocked. Setting one takes a minute. Keeping a team to it is the real work.
October 26, 20269 min read
Every Azure DevOps workflow state belongs to one of five categories, and the category, not the name, decides how cycle time, velocity and forecasts count it. Here is how to pick one for each custom state.
October 26, 20268 min read
The Azure DevOps burnup chart plots completed work rising toward a total scope line, so progress and added scope show up as two separate things. Here is how to set it up, including for an epic or release.
October 26, 202610 min read
Azure DevOps has one built-in forecast: you type in a velocity and it draws sprint lines down your backlog. It can't tell you how likely a date is. A Monte Carlo forecast can.
October 26, 20269 min read
The Azure DevOps velocity chart shows how much work a team finished in each past sprint. Here are Microsoft's rules for each bar, the seven reasons velocity looks wrong, and how to check the chart yourself.
October 26, 20269 min read
Azure DevOps ships four system processes. They differ in work item types, workflow states and the estimate field, and those differences decide where your cycle time starts and what your velocity sums.
October 26, 20262 min read
When a free trial ends, the screen now gives the end date and what is paused, team members can press "I want Agile Analytics back", and Ask Henry is one click away.
October 26, 20261 min read
On a new organisation, Workflow Mapping now shows the mapping Agile Analytics set up for you, ready to review. Organisation admins who hold their rights through a Microsoft Entra group are recognised as admins.
October 25, 20261 min read
On Team and Business plans, when an admin opens the hub, anyone with a seat in your Access settings is now added to our server copy if they are not in it yet. Nothing changes on screen and nobody loses a seat.
October 25, 20263 min read
New organisations get "Your first week" in AGAN AI: three steps that decide whether their numbers are right. A Configuration tab open beside the panel now shows a change the Setup advisor saves straight away.
October 25, 20262 min read
When a suggested WIP limit is for a team that is not in WIP Rules yet, the Setup advisor now also says it adds the team there, before you confirm. After you confirm a change AGAN AI prepared, the panel names it.
October 25, 20267 min read
AGAN AI is a helper panel inside Agile Analytics. It checks your setup, finds stuck and blocked work, answers questions about the app, and prepares setup fixes that are only saved when you confirm them. Workflow Mapping can also leave abandoned states such as Cancelled out of every number, and organisation admins are recognised more reliably.
October 19, 20263 min read
Ask a question about Agile Analytics on any page of this website and get an answer in seconds, with a link to the page it came from. AGAN AI is an AI, it only uses our public pages, and Ask Henry is always one click away.
October 19, 20267 min read
A sprint whose end date has passed now counts as finished in every view, so some averages and forecasts move. Monte Carlo can size a backlog from an Epic, the Exec Report has Copy email text, and many numbers, dates and labels now agree from view to view.
October 17, 20264 min read
Monte Carlo can now forecast from weekly throughput, for teams that do not run sprints. Open an Epic that has Features in Epic Analytics to see its burn-up, with the same 50% and 85% landing dates as the table.
October 15, 20268 min read
Leaders ask four questions: when, what might slip, are we improving, and are we shipping safely. Here is how to answer each from Azure DevOps data, and how the Exec Report in Agile Analytics packs the answers into one page.
October 15, 20269 min read
A mid-sprint dashboard should tell a Scrum Master what to do tomorrow morning. Five signals cover most of it: aging and blocked work, WIP against limits, scope churn, carryover and commitment reliability.
October 15, 20267 min read
Power BI is a strong choice for custom Azure DevOps reporting, but it comes with credentials, refresh schedules and OData to maintain. Here is what that costs and when a browser-based extension is the simpler answer for sprint reporting.
October 15, 20267 min read
The real reasons an Azure DevOps sprint burndown shows nothing or shows numbers that feel wrong, a short checklist to fix each one, and how a count-based burnup in Agile Analytics avoids the hours trap.
October 15, 20263 min read
Monte Carlo Sprint Forecast is a new, free Azure DevOps extension that puts a next-sprint forecast on your dashboard, with two read-only scopes, no account and nothing sent to Baytek.
October 15, 20266 min read
Teams with sub-teams get a new Sub-teams view and a switch that decides whether the parent’s numbers include its sub-teams’ work. Sprint Summary and Cumulative Flow now count that work by default for these teams, so committed goes up and scope change goes down. Exec Report and Cycle Time can include teams from other projects, and Sprint Burnup counts only the Story Points your team has set.
October 14, 20263 min read
Feature Analytics and Epic Analytics now show when work started and when it ends, and each Epic roadmap card shows the same dates. Work in progress now leaves out Removed items, and Aging & Blocked ages a reopened item by the days it was worked. Cycle Time is unchanged.
October 12, 20265 min read
Exec Report now opens with a one-page summary for leadership, built in your browser and shared as a PDF, an email draft or copied text. The Sprint Forecast dashboard widget is free for every organisation. In sprints shared by several teams, commitment reliability and carryover now count only your own team’s work. AI Metrics reads Copilot usage from GitHub’s current reports, and Auto-detect from ADO follows Azure DevOps’ own work item categories.
October 8, 20265 min read
In a brand-new Azure DevOps project the first sprints have no start or end date. Cumulative Flow, Sprint Burnup and the Current Sprint card now say clearly when a sprint has no dates yet. Projects on the default Basic process have their Issues counted, Export Sprint CSV works for teams with undated sprints or no sprints at all, generated pipelines handle unusual team and project names safely, and “View all release notes” opens this page.
October 5, 20266 min read
Two numbers can move for some teams: averages of commitment reliability and carryover now skip sprints where nothing was committed, and flow efficiency on Flow Metrics and Delivery Signals now agrees with the Flow Efficiency view. Empty and ended sprints say so instead of showing zeros and red verdicts, forecast confidence uses one set of blue shades, the Snapshot buttons on Cycle Time and Monte Carlo download their picture, and every view now shares the same header, filter strip and empty state, with larger small text.
September 30, 20267 min read
How to get a sprint burndown chart in Azure DevOps using the built-in tools, how to read the shape without fooling yourself, and where a burndown alone stops being enough.
September 25, 20265 min read
A forecast across several teams used to behave roughly like one team, whatever the team count. It now adds up what each team delivers, and forecasts use each sprint’s real calendar length, so totals are higher and finish dates a little later. Service Level Expectation results count items that skipped the active state, and the Little’s Law panel on Flow Metrics is now labelled as a rough check. When a trial ends, anyone on the team can now pass a ready-made message to the person who buys, and the screen says who can buy and where the licence key goes.
September 16, 20263 min read
Very occasionally Azure DevOps extension storage answers a read with nothing, the same answer it gives when a document does not exist. Until now that could make a licensed organisation look unlicensed for a minute and show the lock screen. The hub now confirms a blank answer a second way, keeps its state and retries when it cannot, and remembers the last successful licence check in your browser. The same blip no longer re-records the administrator email or resets a trial start date, and the Sprint Forecast tile says forecasts start after your first completed sprint instead of showing an error. Updated 22 September for 6.53.1, which makes the Throughput and Sprint Forecast dashboard tiles load for teams with a long sprint history.
September 14, 20265 min read
Time an item spends in a Waiting or Blocked state now counts as wait time on Flow Metrics, Delivery Signals, the Cumulative Flow Diagram and the Aging tab, so flow efficiency can read lower for teams that use those states. A view that cannot load now says what went wrong and what to do, in your language. The Privacy tab states exactly what leaves your tenant, a licensing blip no longer locks anyone out, and exported charts carry a small line saying where they came from. Updated 16 September for 6.52.1, which keeps at least one view ticked for members.
September 3, 20265 min read
Your Azure DevOps tags now decide what Investment Allocation counts as maintenance, and a new exploration list adds a bucket that was never there before. This release also fixes how a reopened item is measured on Flow Efficiency and the service level tables, so those figures can move for teams with rework, and it catches this blog up on the releases in between.
August 30, 20265 min read
A brief connection problem could quietly replace your saved settings, or your organisation’s workflow mapping, with the built-in defaults, and the next automatic save wrote those defaults over the real thing. 6.48.4 closes that gap, tells you when a mapping could not be loaded, fixes dashboard customization, and clears the last language inconsistencies.
August 18, 20266 min read
Organisation-wide default settings with a one-click, undoable rollout to every user, settings locks that are finally visible everywhere, admin control over who sees individual user metrics, forecasts that speak in confidence ranges, a redesigned aging chart, a built-in metrics glossary, and dashboard widgets you can now actually configure. Plus everything that shipped since our last post here.
August 3, 20262 min read
Team and Business subscriptions are now billed once a year: $300/year for Team and $1,200/year for Business, the same total as before. Premium is unchanged. Existing monthly subscribers keep their current price and billing exactly as they are.
July 28, 20268 min read
Most change failure rate numbers are a ratio of bugs to delivered work, a proxy that answers a different question than the one DORA asks. Here is how to compute CFR from actual deployments in Azure DevOps: which deploy broke, what counts as evidence, and why an honest number has to say when it does not know.
July 27, 20265 min read
Finished sprints were being judged by where work sits today, so a team with good hygiene watched its own history drain towards zero. 6.34.8 reconstructs each past sprint as it actually stood at the time. The Cumulative Flow Diagram also stops leaving out work items whose change history Azure DevOps declines to return, and every dashboard now states which work item types its figures count.
July 27, 20264 min read
TF400813 is the error we see most often, and it is almost never a fault in the extension. Azure DevOps Stakeholder access cannot read work item data, so any analytics tool built on it returns empty. Here is how to confirm that is what you are hitting, and exactly what to ask your administrator for.
July 25, 20264 min read
DORA Metrics gains a change failure rate attributed to actual deploys, sitting beside the defect proxy rather than replacing it, with everything it cannot attribute disclosed rather than counted. Plus clearer messages when access levels or a GitHub connection are the real problem, and a privacy page that states exactly what leaves your organisation.
July 24, 20264 min read
A live status page at /status shows whether the website, checkout, licence activation, and telemetry are actually up, checked in real time rather than hand-updated. Alongside it: a published support commitment of one business day, ninety days' notice before any visible feature is removed, and VAT-ready invoices from the first purchase.
July 21, 20265 min read
DORA lead time can now be measured to the moment a pipeline run actually shipped each item. It is opt-in, shown beside the work-item measure you already use, never replacing it, with its coverage always disclosed. A pipeline picker keeps CI-only pipelines out of your deploy numbers. Plus: a notice when your installed version falls behind, a straighter path to Next Sprint Planning, a grown-up SLE Violations page, and a fix for the refresh that forgot your team.
July 20, 20265 min read
A Count / Points toggle lands on Flow Metrics and the WIP Monitor. Points are read from your existing estimates, so there is nothing new to configure. Large organisations may see DORA lead-time and restore-time figures shift once: the sample behind them is now genuinely representative instead of biased to the oldest items. And 6.31.1 teaches Service Level Expectations to match work you categorize with a custom field or a tag, so a "No data" target can finally report.
July 20, 20266 min read
Investment Allocation now breaks down by any field you choose, with rename-and-merge value mapping. A new SLE Violations page lists the exact items behind every missed target. And the biggest change is honesty: commitment reliability and carryover now measure against a start-of-sprint snapshot. Teams that roll unfinished work forward were reading 100% and ~0% forever. Expect those figures to shift once to the truth. And 6.32.2 adds a guard rail to the new SLE editor: it warns when a customized target counts something different from what its name says, and fixes it in one click.
July 17, 20266 min read
Three releases in one post. The Monte Carlo forecast cards had confidence inverted, and 95% now means the safe number, so expect commitments to change. Work imported from Jira or CSV no longer reads as hundred-day cycle times. Sprint Alerts installs correctly and stops announcing month-old transitions. And every chart got a consistent, more scannable redesign. It is visual only, and the numbers underneath are unchanged.
July 7, 20265 min read
One definition of "done" everywhere: every view now uses your Workflow Mapping, including custom state names. Nothing fails silently anymore: unavailable teams are named, caps say "showing N of M", and estimated dates are labelled. And two metrics got more truthful: WIP history and flow efficiency may shift after this update. That is the correction, not a change in your delivery.
July 6, 202610 min read
A practical guide to DORA metrics in Azure DevOps: what each of the four metrics means, which pipeline and work item data feeds it, how to compute it honestly, and how to set it up and read it in the Agile Analytics DORA Metrics view.
July 6, 20264 min read
Three new views arrive in the Measure group: DORA Metrics computed natively from your own Azure DevOps data, an Exec Report you can print to PDF or deliver as a scheduled email digest, and Investment Allocation, the features / bugs / maintenance split per team, with unplanned work called out. One heads-up: this update asks an organisation admin for a one-time approval of a new read-only Pipelines permission.
June 29, 20265 min read
Testaro brings native test case management to Azure DevOps. It is an Azure Test Plans alternative that keeps your test cases, runs, and history inside your own ADO tenant. Early access, free.
June 25, 20266 min read
Agile Analytics now reads your Azure DevOps states and maps them to flow stages automatically, so cycle time, throughput, and aging are accurate from the first time you open the hub. Here is how it works and how to fine-tune it.
June 24, 20264 min read
The entire Agile Analytics interface (navigation, every view, configuration, and dialogs) is now available in English, German, Spanish, French, Italian, and Portuguese. Pick the language your team thinks in.
June 21, 20263 min read
Make the Dashboard yours by rearranging and showing or hiding widgets, plan your Epic Roadmap by setting Target Dates, export any dashboard to CSV (now including Live Stats), jump straight into Azure DevOps from your lists, and, on Enterprise, span multiple projects in Epic Analytics. Plus: the Dashboard’s cycle time now matches the Cycle Time view exactly. No new permissions, no re-authorisation, every setting and mapping preserved.
June 14, 20264 min read
A lot has landed since 6.16: clickable drill-through on every chart, Multi-Team Aging as a risk radar, Epic Analytics with quarter heatmaps, Monte Carlo forecasts that grade themselves against actual delivery, a weekly digest that reads like a coach’s note, and plainer-English coaching. v6.20 brings it all to the public Marketplace and rewrites the in-product release notes to be short and scannable.
June 5, 20263 min read
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.
June 4, 20263 min read
v6.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.
June 1, 20264 min read
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, so there are no more page reloads to confirm an action worked.
May 29, 20265 min read
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, so there are 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.
May 23, 20264 min read
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, with 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.
May 22, 20266 min read
The 6.8.x line completes the move to seat-sized plans: 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 plans are sized by seat count but priced once per organisation, and how the product treats a two-person pilot the same way it treats a hundred-team enterprise rollout.
May 20, 20265 min read
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.
May 19, 20266 min read
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, with zero impact on existing data, mappings, or settings.
May 16, 20265 min read
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.
May 14, 20265 min read
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.
May 10, 20266 min read
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.
May 7, 20267 min read
Version 6.3.5 makes Next Sprint Planning available to every customer under Plan → Next Sprint Planning. It is 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.
May 5, 20269 min read
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.
May 4, 20267 min read
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.
May 4, 20268 min read
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.
May 3, 20269 min read
A practical guide to Azure DevOps dashboard widgets: the six that drive sprint conversations, what each one has to show to be useful, which built-in widgets cover them, and how to add Agile Analytics tiles to a dashboard.
April 29, 20266 min read
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.
April 27, 20266 min read
Major release: explicit N/A workflow mapping, smarter Blocked detection, deep-linked Sprint Capacity, and full dark mode coverage for configuration and capacity panels.
April 20, 20264 min read
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.
April 9, 20264 min read
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.
March 29, 20264 min read
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.
March 22, 20268 min read
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.
March 22, 20265 min read
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.
March 20, 20267 min read
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.
March 19, 20265 min read
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.
March 19, 20265 min read
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.
March 19, 20263 min read
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.
March 19, 20263 min read
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.
March 17, 20264 min read
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.
March 17, 20264 min read
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.
March 17, 20263 min read
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.
March 17, 20263 min read
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.
March 17, 20263 min read
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.
March 15, 202610 min read
Dashboard widgets, four new analytics views, a reorganised navigation, and 211 automated tests. Here is everything that landed in 3.1.5.
March 15, 20264 min read
The Data & Privacy view documents exactly what the extension accesses, what is sent to Baytek, and what never leaves your Azure DevOps tenant. Built for procurement reviewers and security-conscious rollouts.
March 15, 20267 min read
Azure DevOps keeps several kinds of audit trail, and they answer different questions. This guide covers what work item History and organization Auditing record, and how the Agile Analytics Audit Trail view turns state history into a per-sprint timeline for reviews, retrospectives and process checks.
March 15, 20268 min read
A cumulative flow diagram shows how many items sit in each workflow stage on each day. This guide covers how to read the bands, what widening bands and flat lines mean, how to build an Epic or Feature CFD in Azure DevOps, and how the built-in CFD compares with the sprint CFD in Agile Analytics.
March 6, 20268 min read
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.
March 4, 20268 min read
Carryover is one of the clearest signs that sprint commitments are drifting from delivery reality. This guide covers how to measure it honestly in Azure DevOps, the usual root causes, and how to reduce it without shrinking ambition or teaching teams to sandbag.
March 2, 20268 min read
A work item aging chart shows how long every in-progress item has been in flight, against how long work usually takes. Here is how to read one, how to run a standup from it, and how to watch aging across several teams in Azure DevOps.
February 20, 20265 min read
Agile Analytics turns your sprint history into a retrospective-ready summary, delivery signals and scheduled alerts, computed from your own Azure DevOps data in your browser.
February 5, 20266 min read
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.
January 22, 20269 min read
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.
January 8, 20269 min read
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.
December 18, 20257 min read
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.
December 10, 20258 min read
Agile Analytics is an Azure DevOps-native extension that gives your team real-time sprint and flow visibility, with your work item data queried and analysed in the browser. Learn how it works under the hood and exactly what does and does not leave your tenant.