Delivery Signals
The scorecard for the team's most recently finished sprint — not a live number — checked against your organization's own cutoffs.
What you see
- The sprint's name, and a caption noting how many of the most recently finished sprints (up to 6) it's compared against.
- A caption saying whether the thresholds shown are the shipped defaults or your organization's own configured cutoffs, and when they were last changed.
- Eight figures: Reliability, Carryover, Throughput (completed items per week), Cycle Time (median and 85th percentile), Time to Start, Flow Efficiency, Blocked (average days), and Scope Change.
- A Healthy / Watch / Low badge on six of those eight — Carryover, Throughput, Cycle Time, Time to Start, Flow Efficiency and Blocked. Reliability and Scope Change are shown as plain numbers, never graded.
- A "Throughput trend" bar chart — the only figure on this page shown as a trend rather than a single sprint's value.
How we calculate it
- Throughput
- Completed items ÷ the sprint's length in weeks. Healthy at 3 or more items a week, Watch at 1 or more, otherwise Low.
- Carryover
- Healthy at 10% or under, Watch at 25% or under, otherwise Low.
- Cycle Time
- Healthy at a median of 5 days or under, Watch at 10 or under, otherwise Low. Needs at least 10 finished items in the sprint to grade at all; below that it shows as too small a sample to grade rather than a number.
- Time to Start
- Healthy at 3 days or under, Watch at 7 or under, otherwise Low. Same 10-item floor as Cycle Time.
- Flow Efficiency
- Healthy at 40% or more, Watch at 20% or more, otherwise Low. Needs at least 10 items with usable stage history.
- Blocked
- Healthy at 0 average blocked days, Watch under 1 day, otherwise Low — this is the one graded figure never withheld for a small sample, since an item that was never blocked is a real, meaningful zero.
- Reliability and Scope Change
- Shown for information, never graded against a threshold on this view.
- Thresholds
- All six graded figures' good/watch cutoffs are configurable by an organization admin in Configuration; until changed, the shipped defaults above apply.
A perfect-looking Reliability or Carryover reading isn’t always good news
When Azure DevOps holds no real start-of-sprint snapshot for a sprint, Reliability and Carryover are replaced with a warning rather than a number — because the only way to compute them without that snapshot makes a team that simply rolled unfinished work forward look like it delivered everything. If you see this warning, treat both figures as unavailable, not as a good result.
What you can click through to
Nothing — none of the tiles on this view are clickable. To see the items behind a figure, open the view that figure belongs to (Sprint Summary for Reliability/Carryover/Scope Change, Cycle Time, or Flow Metrics for Flow Efficiency).
Known limits
- Only looks at the single most recently finished sprint for its headline figures — the trend chart covers Throughput only, not the other five graded figures.
- No drill-down from any figure on this page.
- Needs at least one finished sprint to show anything at all.