Sprint Velocity

The Sprint velocity source charts committed vs completed work for your recent closed sprints, as grouped bars - one pair per sprint.

Configuring it

Two fields:

Field	Behavior
Project key (optional)	Uses that project’s Scrum board. Left empty, Spotlight uses the site’s first Scrum board.
Closed sprints to show	Last 3, 6, 9, or 12 closed sprints.

Or just ask the AI: “Committed vs completed story points per sprint for the last 6 sprints” - it’s also one of the quick-start templates.

What the numbers mean

Committed - the work that was in the sprint when it closed.
Completed - the portion of that work that is done (resolved, or in the Done status category) when the chart loads. Work finished after the sprint closed still counts toward that sprint’s Completed bar.

The chart’s subtitle always states the board name and the unit, so the chart is self-describing.

Story points, with an honest fallback

Spotlight sums story points, discovering your site’s field automatically - both the company-managed Story Points field and the team-managed Story point estimate, so mixed sites aggregate correctly.

If the site has no story points field, the chart falls back to issue counts - and says so directly in the chart subtitle. You’ll never mistake counted issues for pointed work.

Requirements

The project (or site) has a Scrum board - Kanban boards have no sprints to read.
At least one closed sprint. With none, Spotlight shows a clear “No closed sprints yet” message instead of an empty chart.

Reading the chart

Pattern	What it usually means
Completed ≈ Committed, stable across sprints	Predictable team; velocity is a good forecasting input.
Committed ≫ Completed, repeatedly	Over-committing at planning, or heavy mid-sprint scope additions.
High variance sprint-to-sprint	Shifting scope or noisy estimates.

Issue Charts - for sprint-agnostic breakdowns.
Troubleshooting - board and sprint requirements.