Follow a sprint
Read a sprint's details with its commitment, progress, burndown, burnup, scope changes, points per person and QA bounces.
On this page
A sprint's details tell you whether the team will make it: how much it committed to, how much is done, how the scope has changed and who has what.
Before you start
Anyone who can see the desk can open a sprint's details.
Open the details
Go to Sprints.
Click the sprint's name. From the Backlog, you can also press View on the sprint's block.
At the top you see the sprint's status, its dates and its goal. To go back to the list, use the Sprints link in the breadcrumb.
The sprint's numbers
Indicator | What it is |
|---|---|
Committed | The points the sprint had when it started |
Done | The points of the items that are already in Done or Released |
Current scope | The points the sprint has today, after the changes |
Capacity | The sum of the capacity entered when starting. It turns an alert color if the scope exceeds it |
Avg. velocity | The points the team completed on average in the last 3 sprints |
Days left | Only in the active sprint. It turns an alert color when 2 days or less are left |
Only stories, tasks and bugs add points. Epics and subtasks don't count.
Burndown and burnup
Burndown: the Remaining line shows the points left each day, and the dotted Ideal line, the pace that would finish just in time. If Remaining is above Ideal, the team is behind.
Burnup: the Done line shows what's completed, and the dotted Scope line, the sprint's total. It helps you see whether the delay comes from slow work or from scope that grew.
The charts are built from a daily snapshot. If the sprint just started, you see No snapshots yet: the first one is taken at the end of the day.
Below each chart, Show data shows the same values in a table. It's useful for copying the numbers or reading them with the keyboard or a screen reader. Hide data closes it.
Scope changes
The table shows everything that changed after the sprint started, with When, Item, Change, Points and Who. The changes are:
Added: an item was added to the already started sprint.
Removed: an item was taken out of the sprint.
Points changed: an item was re-estimated; the Points column shows the previous and the new value.
If nothing changed, you see The scope didn't change after starting.
By person
The table shows, for each assignee, the Committed and Done points and their Capacity. Items without an assignee appear as Unassigned.
QA bounces
Below By person, the QA bounces list shows the sprint's items that QA rejected, with the number of rejections (↺). An item that bounces several times usually has unclear acceptance criteria.
Lead actions
If you are the Lead, at the top you have Edit and, depending on the status, Start sprint or Close sprint.