Skip to main content
Compass

Sprint Health

Track velocity, completion & carry-over

Scrum Master Guide: Sprint Metrics & Health

Use team_sprint_summary to pull committed vs. completed story points and issue counts per sprint for a given team and date range. This endpoint surfaces carry-over items and velocity trends that power your sprint retrospectives.

Pair with team_metrics for broader engineering health signals — PR cycle time, review depth, and commit frequency — giving you leading indicators of whether your velocity numbers reflect sustainable delivery or unseen bottlenecks.

Avg Velocity
56.3
story points / sprint
Trending up: +12% vs last quarter
Completion Rate
88%
committed vs completed
Trending up: +5% improvement
Carry-Over
3.0
avg items / sprint
Trending down: watch threshold
Sprint Cadence
2w
consistent cadence
Trending up: stable

Sprint History

SprintCommittedCompletedCarry-OverVelocity
Sprint 241816262
Sprint 231514154
Sprint 222016451
Sprint 211715258

Velocity Trend — Scope vs Effort

W1
W2
W3
W4
W5
W6
W7
W8
ScopeEffort
W1: Scope: 54.285714285714285%, Effort: 45.714285714285715%. W2: Scope: 60%, Effort: 57.14285714285714%. W3: Scope: 50%, Effort: 51.42857142857142%. W4: Scope: 71.42857142857143%, Effort: 64.28571428571429%. W5: Scope: 57.14285714285714%, Effort: 60%. W6: Scope: 78.57142857142857%, Effort: 71.42857142857143%. W7: Scope: 67.14285714285714%, Effort: 70%. W8: Scope: 85.71428571428571%, Effort: 78.57142857142857%

API Explorer

MockMock

How to Use This in Your Sprint Ceremonies

Sprint Planning

Query team_sprint_summary before planning to baseline your team's historical velocity. Use the last 3–4 sprints to set a realistic commitment ceiling and avoid over-promising.

Daily Standup

Use team_metrics mid-sprint to spot PR bottlenecks or review delays that could threaten completion. An uptick in cycle time is an early warning before carry-over materialises.

Sprint Review

Pull team_sprint_summary at sprint close to present committed vs. completed to stakeholders. Highlight carry-over items with context from person_metrics if individual blockers contributed.

Retrospective

Combine team_sprint_summary, team_metrics, and unlinked_pull_requests to run a data-driven retro — correlate carry-over spikes with PR hygiene gaps and identify systemic patterns across sprints.