Sprint reports
Committed, completed and carryover, the burndown and velocity — what each number is and when it is taken.
A sprint keeps a record of itself as it goes: what was committed when it started, what was completed when it closed, and a daily line in between. This page is about those numbers. Planning a sprint and working its board are on Your first project.
Committed and completed
- Start sprint freezes the sprint’s committed points: the story points of every task in it at that moment. Work added later never changes the number.
- While the sprint is active its page reads “N pts committed · M done”, where done is live — the points of the tasks that are in a done status right now.
- Close sprint, on the sprint’s own page, freezes its completed points: the points of the done tasks at that moment. If tasks are unfinished, you choose one destination for all of them — the next planned sprint, or the product backlog — and they move with their status untouched. Done tasks stay on the sprint as its record.
- Cancel sprint sends every task in it back to the backlog. A cancelled sprint freezes no completed points and is left out of velocity; one that had started keeps its committed number and the daily points it already took.
Done means the status category, whatever the status is called — see Project overview for the rule and what it does with a Cancelled status.
The report
Select a closed sprint under Sprints and its report opens with four tiles:
| Tile | What it is |
|---|---|
| Committed | the points frozen at start |
| Completed | the points frozen at close |
| Carryover | committed minus completed, never below zero — when scope was added mid-sprint it understates what moved |
| Velocity | the completed points again, with “vs avg” against the project’s current average |
Under the tiles sit the two charts described below. They also sit on every sprint’s own page, whatever its state.
Burndown
The burndown draws the points remaining in the sprint, day by day, from its start date to its end date, against an ideal line that runs from the committed points down to zero. A day on which the scope grew is marked “+N scope”. A shrink gets no label: removing unfinished work shows as a drop in the line, and removing work that was already done does not show at all. A marker shows today while the sprint is in its dates.
When a point is taken matters for reading it. Once per calendar day, in the project’s timezone, a background pass records the sprint’s state — and the pass runs about once an hour, so each day’s point is the state shortly after that day began. Today’s work shows on tomorrow’s point. A sprint started a moment ago reads No snapshots yet until the first pass; a sprint that stays open past its end date keeps recording; a closed sprint records nothing more, so there is no final point at close. Weekends are days like any other.
Velocity
A sprint’s velocity is its completed points, frozen at close and never recomputed — reopening or trashing a task afterwards changes nothing. The project’s average is the plain mean over its last five closed sprints, or fewer while there are fewer; cancelled sprints are not in it.
The velocity chart shows those last five closed sprints as bars, oldest first, with the average as a dashed line. While a sprint is active it appears as an outlined In flight bar with its live done points, never part of the average.
The same average, rounded, is the capacity hint in sprint planning once the project has a closed sprint: the sprint pane’s footer reads “P / ~C pts” and adds “over capacity” when the plan exceeds it. It is a hint — nothing is refused.
Reading the numbers honestly
- Points are a task’s own. An epic carries its own estimate, and a task without one counts as zero.
- “Days left” and the today marker follow the day in your browser; the daily points follow the project’s timezone.
- Your assistant can read every sprint and its report over MCP — the burndown series and the velocity window included — and can move a task into or out of a sprint. Starting, closing and cancelling a sprint are a person’s acts: there is no tool for them.
- There is no per-person capacity and no forecast of sprints to completion; the one hint is the average above.