Your organisation’s breakdown in Investment Allocation
An app admin can select "Make this the organisation default" to share the current Break down by field and its renamed values. Everyone who has not picked their own field sees it, and anyone who picked a field keeps theirs. Choosing the built-in buckets is remembered as your own choice.
Related: Break down by your own field
Next Sprint Planning before capacity is set up
Next Sprint Planning plans the earliest upcoming sprint that has dates. A sprint with dates but no capacity set shows its forecast at full capacity with an "(assumed)" capacity card that links to the sprint's capacity page, and the view says so when capacity or days off could not be loaded. The reliability lens counts committed items completed and stays within 100%.
Numbers that agree
The Dashboard "How many?" tile now matches the Monte Carlo view exactly. Exec Report counts each bug once across its teams and ages only work in progress against the p85 cycle time. Retro Snapshot opens on the last finished sprint. Live Stats Total Effort shows "not estimated" when no item has an estimate, and Feature Analytics shows Progress by stories when a feature has no story points.
Also in this release
Views that say what they measured:
- WIP Monitor shows a team with no active sprint as not checked rather than within its limit. Sprint Capacity, Flow Efficiency and SLE Violations say what could not be loaded or how many items were measured. Delivery Signals ranges skip sprints with no baseline. The CFD "WIP climbing" verdict needs at least 5 items and a 25% rise, and the Cycle Time histogram includes items finished the same day.
- A customised Dashboard keeps two columns on wide screens. Feature Analytics hides the Pts, Size and Origin columns when no feature uses them. The Cycle Time heat map labels each band by its real edges and splits the first band for fast teams. Chart axes use round numbers, and Cycle Time, Monte Carlo and Live Stats offer "Download PNG".
- Team Benchmarks shows your project's teams when no custom scope is set, and Monte Carlo runs straight away when you switch to "When will it finish?". Multi-Team Aging chips name their age bands and your mapped stage names, the Live Stats goal tile explains its default, and Dashboard charts have text alternatives for screen readers.
What you need to do
Nothing. Azure DevOps updates the extension automatically. Some numbers can move on purpose: Exec Report bug counts are lower when teams share area paths, the Dashboard forecast tile now equals Monte Carlo, and the Cycle Time histogram includes items finished the same day.
Related: Investment Allocation guide · 6.66.0: one rule for cycle time and sprints