Reports

The Reports screen

NeedsView view

Open the project. Click Reports, under Retrospective. On a phone, the tab bar has no Reports tab: open the Sprint Review and follow the link under the title, This sprint’s burndown and the team’s velocity.

A row of sprint names runs under the title, newest first. It lists every sprint that started and was not cancelled. Click one to see its health and burndown. The screen opens on the Active sprint, or on the most recent one when none is Active. A project with no such sprint shows Nothing to report yet.

Sprint health

The first card names the Sprint Goal and the sprint's dates, then shows up to five tiles.

• Done: the size of the sprint's Done items, out of the size of all its items, and how many items are Done. While the sprint is Active, this changes the moment an item moves.
• Working days: how many of the sprint's working days have ended.
• Health, while the sprint is Active: On track, At risk or Off track. It compares the share of the work that is Done with the share of the working days that have ended. More than 20 percentage points behind is At risk, and more than 40 is Off track. It is the same rule, and the same word, as the project card on Projects and the The Overview. A sprint with nothing in it has no Health tile.
• Against the ideal line, while the sprint is Active: how much more remained at the end of the last working day than the burndown's ideal line, for example 2 points above, or At or below. It is a figure to read with the chart, not a second verdict.
• Scope since the start: the size added to the sprint, or taken out, since its first Monday.

Needs attention lists the unfinished items that are blocked, not started (Draft or Final), or not sized. A closed sprint has no such list: closing it moved its unfinished items out. Items in this sprint opens the full list.

The burndown

The chart has three lines. The legend above it names them.

• Remaining: the size of the sprint's items that are not Done. The latest point carries a label, for example 12 left.
• Scope: the size of everything in the sprint. It rises when an item joins the sprint, and falls when one leaves.
• Ideal: a straight line from the scope at the start to zero on the last day.

The first point is Start, Monday at midnight. Then there is one point at the end of each working day, Monday to Friday, in the time zone of the sprint's team. Weekends have no point. A day that has not ended yet has no point either.

Point at the chart, or select it with Tab and use the left and right arrow keys, to read one day's three values. Show the numbers opens a table with every value.

Velocity

Velocity shows the last six sprints that ended, oldest on the left. Cancelled sprints are left out. Each sprint has two columns: Committed at the start, the sprint's scope on its first Monday, and Done at the end, the size of its items that were Done when it stopped counting. The Done value sits on top of its column. When the project has more than one team, each sprint name also names its team.

The product offers no forecast. Velocity is history, and the team decides what it means for the next sprint in Sprint planning.

Save as PDF

Save as PDF, beside the title, prints the screen as a sprint report: the health, every item in the sprint, the burndown and velocity, and each table of numbers. It prints in the light theme, without the menus and the row of sprints. Pick the sprint first. See Exporting a project.

How the numbers are worked out

The reports keep no numbers of their own. Each one is worked out, when you open the screen, from each item's history: its status changes, its size changes, and its moves in and out of sprints. See Backlog items. So a report always agrees with the backlog, and it changes if the history does.

A sprint stops counting at the end of its last Friday. It stops earlier if somebody ended it earlier, and just before it was closed if it was closed earlier. Work finished after that is not the sprint's, and the close returning unfinished items to the backlog is not shown as progress.