Release Notes · November 12, 2026 · 3 min read · By Baytek

Agile Analytics 6.77.4: Flow efficiency reads the same on every view

Flow Metrics, Delivery Signals, Team Benchmarks and Process Behavior now work out flow efficiency the same way as the Flow Efficiency view and the Dashboard. Aging & Blocked counts each working day once, and averages use the same six finished sprints on every view.

  • #release notes
  • #6.77
  • #6.77.4
  • #azure devops
  • #flow efficiency
  • #flow metrics
  • #aging
  • #sprint history

One flow efficiency on every view

Flow Metrics, Delivery Signals, Team Benchmarks and Process Behavior now work out flow efficiency the same way as the Flow Efficiency view and the Dashboard: all active time over all cycle time. The lines that judge flow efficiency follow the new figure: Delivery Signals reads good from 15% and medium from 10% unless an admin chose other values, and Team Benchmarks flags it under 15%. Time in a stage is the real time spent there, so a short visit counts as the time it took, not a whole day. Flow Metrics averages each stage over all finished items, so the stages add up; Quality & Rework shows time in review for the items that were reviewed, with their count.

What this means for your numbers

Some of these views will show a lower flow efficiency figure than before; for 30 days each carries a short note saying so. There is now one default history: the six newest finished sprints on the Dashboard, Exec Report, Team Benchmarks, Retro Snapshot, Sprint Capacity, Sprint Velocity, Flow Metrics and Delivery Signals, whether or not a sprint is running. The running sprint is still shown as "in progress" and left out of every average.

Aging & Blocked counts each working day once

"Days in flow" counts each working day once, however many stages an item passed through that day. Ages and the thresholds from your finished work move together, in the chart, Sub-teams, AGAN AI and the local AI connector. An item is "over p85" only once it is older than p85. When your items usually finish within a day, the fixed bands are used (over 3 days, over 6 days), so a fast team sees only the items past those bands flagged. On the Exec Report, "Open items older than the p85 cycle time" is now the Aging & Blocked view’s own count for each team.

Improvements

Sprint Summary, the Exec Report and Retro Snapshot add one line when a sprint’s commitment was under a quarter of its items, for example "The commitment covered 4% of this sprint’s work (6 of 149 items)"; the reliability figure itself is unchanged. A team or project picked inside Flow Metrics, Cumulative Flow, Aging & Blocked, Cycle Time, Monte Carlo, Delivery Signals, Retro Snapshot and the other single-team views is now the sidebar’s too, so the next view opens on the same team; "All teams" stays inside the view. Sprint Summary, WIP Monitor, Live Stats, Team Benchmarks and Multi-Team Aging keep their own list of teams, and when the sidebar team is not on it they say so with one notice and a button to add the team or edit the list. When the hub shows a different project from the Azure DevOps page it was opened on, a line under the project picker names that project, with a button to show it. The note under each view and the SLE panel list only the work item types your project has, and when none of your SLE targets match the project’s types the Dashboard panel says so in one line. Live Stats: the goal tile reads "Goal: 40% done by sprint end" and "on pace today", and a "Show all teams" button appears when "Limit to current project" hides every team. The Dashboard’s Sprint Velocity card matches the other cards, and Aging & Blocked and Sprint Summary wait less on Azure DevOps when they open. The CSV exports from Flow Metrics and Delivery Signals mark the running sprint in a new last column, and the Flow Metrics trend chart shows your team’s own flow efficiency line. AGAN AI answers "What is aging past normal?" in days when the fixed bands are in use.

What you need to do

Nothing; Azure DevOps updates the extension automatically. If a view shows a lower flow efficiency than you remember, that is the same calculation the Flow Efficiency view and the Dashboard use, and the view says so in a short note for 30 days. This update also brings 6.76.2, which made sprint reliability read the same on every view.

Related: 6.76.2: Reliability reads the same on every view · Full release history

Compare your Azure DevOps reporting options before you commit

See how built-in ADO reporting, Power BI, and Marketplace extensions stack up, then start the 30-day trial to evaluate the extension path inside your own organisation.

Related reading

Find our articles faster: add Agile Analytics as a preferred source in Google Search.Add preferred source →