One rule for every sprint view
Sprint Summary, Sub-teams, the Dashboard, Sprint Velocity, Sprint Detail, Exec Report, Retro Snapshot, Team Benchmarks, alerts and the local AI connector now share one rule for committed, delivered, added and removed, so the same sprint reads the same everywhere. Every view starts from the same day 1 snapshot, the same for every viewer, so team members and organisation owners see one commitment. Reliability percentages round the same way on every view.
What this means for past sprints
Each item is judged by what it was at the sprint deadline, or when it left the sprint. Work that was done in the sprint and reopened or moved later still counts as delivered, so some past sprints will read a little higher on the Dashboard, Exec Report and trends. When Azure DevOps has no day 1 snapshot for a sprint, Added and scope change show "not available" instead of an estimate, and the health grade leaves them out. On Sprint Summary, the Removed list shows every item its number counts, including work handed to another team.
Investment Allocation: choose your teams, open the items
Choose which teams to show with the new Teams filter, or pick Only beside a team or sub-team to see it alone. Your choice is remembered in this browser, the team picked in the sidebar is listed first, and All teams still counts the whole project. Click a value or a bucket in any row to open exactly those items in Azure DevOps.
Improvements
On the Dashboard, the Sprint Burnup footer shows the same "scope added" count as Sprint Summary, including work pulled in from the backlog; tiles with nothing measured yet show a dash, and Lead Time says it is the median. Live Stats and WIP Monitor say when a sprint has ended. Opening a project with no saved team lands on its default team in Azure DevOps. Configuration → General names the plans as they are, the Aging view’s title matches the menu ("Aging & Blocked"), and every view can be scrolled clear of the Ask AI button. The local AI connector (@baytekdev/agile-analytics-mcp 6.76.2) reports a refused sign-in as a sign-in problem, and its set-up guide now shows the token in the Claude Desktop entry’s "env" block.
What you need to do
Nothing; Azure DevOps updates the extension automatically. If a past sprint now reads a little higher than you remember, that is work done in the sprint and reopened or moved later, which now counts as delivered on every view.
Related: Set-up guide: the local AI connector · 6.75.1: A local AI connector for your numbers