Agile Analytics 6.63.5: ended sprints count as finished, a better Exec Report, and numbers that agree

A sprint that has ended now counts as finished

If your last sprint has ended and no newer sprint exists yet, Azure DevOps still calls it the current sprint. Agile Analytics now treats it as finished in every view, so some averages and forecasts can move, usually down when that sprint delivered little.

• Views that now include the ended sprint: Dashboard, Sprint Velocity, Flow Metrics, Delivery Signals, Monte Carlo, Retro Snapshot, Sprint Capacity, Team Leaderboard, Cycle Time and the Sub-teams forecast.
• Views that show the current sprint still open on it, and now say "· ended Oct 16" instead of "(Current)", "(in progress)" or "so far".
• Next Sprint Planning says that no next sprint is defined yet, instead of offering the ended sprint to plan.
• The Monte Carlo view with several teams, the free Monte Carlo Sprint Forecast and the Sprint Forecast dashboard widget work as before.
• On the Dashboard, the "How many?" Forecast now uses the same 6 finished sprints as the Monte Carlo view. While a sprint was running it used only 5, so for teams with a running sprint its numbers can move to match Monte Carlo.
• The Cycle Time, Flow Efficiency and Lead Time captions now say "Last 6 finished sprints". Sprint Velocity’s "Last 6 Sprints" can include the sprint that is still running.

Exec Report

The Exec Report is clearer about what it shows, and its email button now does what you need.

• It opens on the sprint that just ended and says how long ago it ended ("ended 2 days ago"), on screen and in the printed report.
• Email draft is now Copy email text. It copies a ready-to-send email, a subject line and the summary, that you paste into a new email in your email app, and the report no longer goes blank.
• The support and billing email addresses now show with a Copy button. On the screen shown when a trial has ended, Copy message replaces Email this message.
• When nothing was committed, the headline says "No commitment baseline for this sprint", even when aging or bug figures are shown. The team card shows a dash for Commitment reliability and Scope churn instead of 0% and 100%, and its insight no longer says to review planning.
• "Avg reliability (recent sprints)" shows a dash instead of 0% when none of the recent sprints had anything committed.
• A team card whose Throughput is higher than Delivered says how many items were completed but not against the commitment.
• The carryover insight now reads "Carryover is elevated: 6 committed items were not delivered by sprint end."
• The forecast says its window in days, "in the next 4 weeks (28 days)". If the forecast and risk figures take longer than 15 seconds, the headline says "Forecast unavailable right now." instead of loading forever.
• "Open items older than the p85 cycle time" now also counts still-open work carried over from the previous sprint.
• The leadership report (PDF) prints your own date.

Monte Carlo

Monte Carlo has three changes in When will it finish? and one in Weeks.

• Under Backlog from, choose An Epic or Feature to pick one of the Epics Epic Analytics shows, or one of its Features, by title or ID. The backlog becomes its stories not done yet, counted the same way as the Epic Analytics row.
• A note explains that Monte Carlo assumes the team spends its whole throughput on that item, while Epic Analytics’ Landing forecast uses the Epic’s own recent pace, so the two dates can differ. With several teams selected, enter the backlog as a number.
• The Completion Timeline’s "Today" showed yesterday’s date for anyone east of UTC. It now shows your own date, and forecast dates start on your own calendar day around midnight.
• In Weeks, a note now says the forecast moves one whole week at a time from today, so two confidence levels can share a date.
• In How many?, the chart’s description for screen readers now gives the same 95% and 50% numbers as the cards. On longer forecasts it could read one or two lower.

Flow Metrics

"Median Cycle Time" is now a true median: the average of each finished sprint’s median cycle time, the same figure Delivery Signals shows under the same name. Before, Flow Metrics averaged each sprint’s average cycle time, so the figure may shift slightly, usually down.

• The Cycle Time column, the Cycle & lead time trend and the Little’s Law estimate (rough check) still use each sprint’s average.
• The Little’s Law card now works for teams with imported history, which used to see it empty.
• Flow Metrics and Delivery Signals now say their Flow Efficiency is the "average of sprint medians". The Flow Efficiency view pools every item of its sprints into one figure, so its number can differ.
• On the Flow Efficiency view a figure above 40% now reads "Better than typical (above 40%)", and the description says what each side of the 15 to 40% band means. The Flow Metrics tile now reads "Industry average is about 25%. This is elite (40% or more)."
• The Flow Trend charts leave a gap for a sprint with no data, as the table row does, instead of plotting it as 0d or 0%.

Multi-Team Aging: Stalled and Blocked are now separate

"Blocked" used to mean 5 days or more with no state change. That rule is now called "Stalled 5d+", and "Blocked (recorded signal)" counts the items your Blocked signals mark as blocked, the same way Aging & Blocked and Delivery Signals count them. The risk score and "Teams At Risk" use the recorded count, so risk scores drop for teams with work that is stale but not blocked.

• Age and Stuck now use one day count and the item’s state history. Stuck can read one day more than before, and on imported history it follows the real history instead of the import date.
• Aging & Blocked now includes still-open items carried over from the previous sprint, as Multi-Team Aging does, and says how many.
• An ended sprint is labelled with its end date, the dates read "Oct 5, 2026 - Oct 16, 2026", and a sprint whose items are all still in New says "7 items are still in New. Aging starts when work begins."

Sprint Summary for teams with imported history

For teams whose history was imported, for example from Jira or a CSV file, a story that was in the sprint on day one and moved out later now counts as committed, as the Dashboard, Flow Metrics and Delivery Signals already counted it. Commitment reliability can go down for these teams, and the moved story shows as carried over. Teams with their full Azure DevOps history see no change.

• Once a sprint has ended, Planned Work, Bugs and Research say "1 not done by sprint end" instead of "1 open".
• When the team picked in the sidebar is not on the view’s own team list, a note says so and offers "Add Payments Team".

Reliability colours follow your target

The Commitment colours in Sprint Velocity and the Avg Reliability tile in Flow Metrics now follow your reliability target, as Delivery Signals does. With the default target, green is from 85%, amber from 70% and red below 70%, so a sprint at 75 to 84% can now show amber and one at 60 to 69% red. Admins set the target in Configuration → Enterprise, under Dashboard thresholds. Sprint Velocity’s Avg row now averages only the sprints that show a number, and shows a dash when there are none, instead of 0%.

DORA

Build failure rate now says what it is based on, for example "4 of 4 completed runs failed", and shows "No data" when no run finished. When every run in the window failed, Deployment frequency says so instead of saying that none of the selected pipelines ran. Screen readers now hear "4d P85 7.2d" with a space.

Phone layout

The Dashboard fits a phone screen without sideways scrolling.

• The Sprint Velocity table scrolls inside its own card, and the Current Sprint figures and the Sprint Burnup footer wrap.
• In Customize on a phone, the "Hidden" tag no longer covers a widget’s checkbox, so tapping the checkbox works.

Privacy wording

The Industry Benchmarks snapshot is linked only to your organisation ID, and usage telemetry events are linked to your organisation and user ID, never work item content, names or titles. A few texts called these anonymous. They now say exactly this, here and in Configuration → Privacy. Nothing that is sent has changed.

Help texts corrected

Help and descriptions across the app were checked against how the numbers are actually worked out, and corrected where they differed, for example Cycle Time, DORA, Aging, Next Sprint Planning and Little’s Law.

• In How These Metrics Work: aging colors come from your team’s own history, not from a setting. A title with just "block" in it is not marked blocked (a "block" tag is). Commitment reliability counts items, not points.
• In Configuration → Readiness, the Workflow Mapping note now says that without a saved mapping, cycle time, lead time and Flow Efficiency use built-in default state names, which may not match your process.
• Help & Support no longer offers to book a call. Ask Henry is still there.

Other fixes

Smaller changes that make numbers and labels agree.

• A sprint with a damaged or open-ended date in Azure DevOps no longer stops a team’s views from loading, Cumulative Flow included. It is treated as a sprint with no dates yet. Sprint Capacity and Next Sprint Planning also cope with a damaged days-off date.
• Cumulative Flow shows "Flow: No movement (nothing started or finished)" instead of a green "Steady" for a sprint where nothing moved, its window stops at the end of an ended sprint, and west of UTC its date labels no longer read one day early.
• The Forecast Scorecard keeps one row per team, window and day, as it says. Duplicates clear themselves.
• Industry Benchmarks puts "best" on the better end of each bar.
• The Sprint Burnup footer also shows removed items ("−1 scope removed"), so its numbers add up.
• Sub-teams says how many sprints its delivered trend shows, and when a sprint could not be read. Investment Allocation explains when team rows add up to more than All teams.
• Exec Report and WIP Monitor dates use the "Sep 21, 2026" format. Cycle Time dots read "2.9 days" to screen readers, and the month axis no longer repeats a month.
• WIP Monitor: the History tab now opens on the team picked in the sidebar, and the Current tab has an "Edit WIP teams" button.
• Next Sprint Planning’s "longer than sprint" warning now compares a bucket’s median cycle time with the sprint’s calendar length, weekends included. No forecast number moves.
• Epic Analytics: when an Epic’s Landing forecast is a single pace date (such as "~Feb 11, 2027 at 0.3/wk"), the note under its burn-up says that date is a simple pace projection, and that 50% and 85% landing dates need more recent history.

What you need to do

Nothing is required. Azure DevOps updates the extension automatically. Because ended sprints now count as finished, some averages and forecasts may look different after the update. If a figure looks different and you want to know why, use Ask Henry in the top bar.

Related: Service status