Measure whether a process change works. Set goals on your team's pull-request and work-item metrics, freeze the
targets, and watch each goal move from its baseline after you adopt the change.
What it does
Initiatives with goals and guardrails. Pick metrics such as PR open-to-merged time, review rework or work-item
cycle time, set a target for each, and add guardrails that must not get worse.
Baselines from your own history. Each goal's baseline is computed from the weeks before adoption, so you start
from real numbers, not guesses.
Frozen targets. Freeze the targets when you adopt the change; later edits need a reason and stay visible.
Weekly trends. Every goal gets a trend chart (baseline, before and after adoption) and an 8-week sparkline.
Where an item's time goes. See how work-item time splits between coding, review, and test and release.
Getting started
Install the extension in your organization.
Open Boards → Improvements in a project. A project administrator runs the setup wizard once and starts the
first sync.
Create an initiative (a ready-made PR-flow initiative is filled in to start from), set targets, and save.
Data and permissions
The extension reads Git pull requests, work items and Analytics in your organization. It stores the facts it computes in
the extension's own data storage in your organization; nothing leaves Azure DevOps. Everyone who can open the project
can view the hub; only project administrators can change settings and initiatives.
