Sprint Health Dashboard

Five sprint metrics, calculated automatically from your Azure DevOps data, on one widget. Click any metric to see how it has trended over your last 5 sprints.

No spreadsheets. No manual tallying. The numbers update as work items move.

What the widget shows

The widget pulls live data from your team's current sprint and computes five things:

Sprint Health (the big number)

A single percentage that answers: "Are we delivering at the pace we should be?"

It compares how much work is actually done versus how much should be done by today. The number sits in one of four bands:

• Above 90% → Healthy 🟢
• 70 to 90% → Slightly behind 🟡
• Below 70% → Sprint at risk 🔴
• Above 120% → Work was underestimated, or scope was added 🔵

Predictability

Of the work the team committed to at the start of the sprint, how much of it actually got finished by the end (or by today, for an in-progress sprint)?

This answers: "How reliably does the team deliver what it commits to?"

Carry-over

Of the work the team committed to at the start, how much won't be finished by the sprint's end?

This answers: "How much committed work is likely to slip into the next sprint?"

Scope change

How much work was added or removed from the sprint after it started?

• A positive number means scope grew (new work was pulled in).
• A negative number means scope shrank (work was removed).
• Zero means the team stuck to its original commitment.

This answers: "Did mid-sprint changes affect the team's ability to deliver?"

Flow stability

Of the work that the team started during the sprint, how much of it actually got finished during the sprint?

This answers: "Once we begin work, do we finish it, or do things pile up half-done?"

A healthy team has high flow stability. A team with lots of work in progress but few completions has low flow stability.

The trend view

Click any of the four metric tiles and the widget expands to show that metric's history across the last 5 completed sprints, plus the current sprint marked as in-progress.

This turns the widget from a snapshot into a story. A team with predictability dropping over the last 3 sprints knows it has a real problem; a team with one bad sprint after four good ones knows it's likely just a blip.

The widget computes a small one-line trend summary like "Trend: declining over last 3 sprints. Average across 5 completed sprints: 47%."

How to use

1. Install the extension into your Azure DevOps organization.
2. Open any team dashboard. Click Edit, then Add a widget.
3. Search for Sprint Health and drop it on the dashboard.
4. Click the gear icon to configure:
   • Which team to track
   • What states count as "Done" (default: Resolved, Ready for deploy, Closed)
   • What states count as "Started" (default: Active and any Done state)
   • Sprint length in working days (default: 10)
5. Save. The widget loads and shows live numbers.

What you need

• Azure DevOps Services (cloud) or Azure DevOps Server with Analytics enabled — this is on by default for new organizations.
• A team with iterations configured and a current sprint that covers today's date.
• Work items (User Stories, Bugs, or whatever types you configure) with story points assigned. Items without points are counted as zero, which can distort the metrics. The widget warns you if more than 20% of committed items are unpointed.

Sizing

The widget supports sizes from 1×1 (just the health score) up to 8×8 (full layout with breathing room). The recommended size is 4×4 or larger to see all five metrics with their captions. Sizes below that progressively hide details to keep the tile readable.