Plan in story points
Next Sprint Planning has a Count / Points switch in its toolbar. In Points, the recommended commitment, its range and the bucket breakdown are in story points, read from Story Points, Effort or Size on your completed items. Count stays the default, your choice is remembered, and Configuration, Enterprise can set and lock it for the whole organisation. Completed items with no estimate are left out of the points and counted in a note under the forecast. Commitment reliability stays in items, and the view says so.
Related: Documentation
Opens faster, asks Azure DevOps for less
When the hub opens, the views now wait briefly for the project’s revision history instead of reading each work item one by one, so the hub makes far fewer Azure DevOps calls on the way to its first numbers. The Configuration screen’s text downloads with that screen rather than with every hub open, and in a language other than English the screen appears once its text has loaded instead of flashing English first.
Smaller download after an update
The What’s New dialog and the Help page carry only the recent releases. The full history stays here on the website, so each update downloads less.
Related: Full release history
What you need to do
Nothing. Azure DevOps updates the extension automatically. If your team plans in story points, open Next Sprint Planning and switch the toolbar to Points once; the view remembers it.