Sprint reports
A sprint report shows how a board, a project or your whole organization delivered over a period: a one-line summary, headline numbers and charts, ready to share with leadership as a PDF or in a wiki as Markdown.
Opening a report
- A board: open its Past sprints and choose Sprint report. Anyone in your organization.
- A project: Sprint report at the top of the project page: all its sprint boards together. Anyone in your organization.
- The organization: Settings → Sprint report: every project. Organization admins only.
Pick a period: the last 30 or 90 days, this quarter, last quarter, or your own dates. Days follow your own time zone. The page’s address holds the report and its period, so you can send the link to someone in your organization.
What the numbers mean
| Measure | What it is |
|---|---|
| Planned | What a sprint held when it started. |
| Delivered (done) | What it finished by the time it closed. |
| Predictability | Delivered as a share of planned. 80–100% is on target: under means the team took on more than it finished; well over means more was added along the way than planned. |
| Velocity | Delivered per sprint, averaged over that sprint and the two before it. |
| Scope change | Work added after sprints started, as a share of what they planned. |
| Added / Removed | Tickets that joined a sprint after it started, or left it before it closed. |
| Carried over | What was unfinished at the end and moved on to the next sprint. |
| Work mix | What got done, by type: bugs, features and tasks, so you can see how much went on fixing versus building. |
| Goals met | A sprint with a goal met it when nothing carried over. |
The headline cards compare against the period just before, of the same length, with an arrow up, down or level. A sprint still running shows as “so far” and isn’t counted in the totals.
Points, tickets and different boards
- Boards that estimate count in points (T-shirt sizes are converted to points); boards that don’t count tickets.
- Project and organization reports never add points and tickets together: each has its own total. Predictability is a share, so it compares fairly across both.
- Different boards’ sprints don’t start on the same days, so project and organization trends are by calendar month. Each board or project links to its own report for the same period.
Sprints from before reports
Reports record what each sprint starts and ends with. For sprints that finished before that began, planned is what the sprint held when it closed, and what was added or removed isn’t known; they’re marked with an asterisk.
Why there are no per-person figures
Reports are about how teams deliver, never who did the most or least. Without knowing who was on holiday or off sick, numbers per person would be unfair and misleading, so reports only ever show boards, projects and the organization.
Presenting it
- Export → Save as PDF (presentation): a landscape document with a cover page, the summary and headline numbers, one chart per page, then the sprint goals and the detail. It always prints in the light theme.
- Download Markdown or Copy as Markdown: the same report as text for a wiki, Notion, GitHub or Confluence. Its charts are Mermaid diagrams, which those tools (and Obsidian) draw as graphs; each has a table of its numbers underneath, so it reads anywhere.
For AI agents
Agents can fetch the same reports with get_board_sprint_report and get_project_sprint_report, as data or with format: markdown (Connect an AI agent). The organization report is for organization admins in the app.