Sprint reports and charts

You will learn how to read Tixio sprint reports, capacity summaries, velocity, burnup, burndown, and related cycle analytics.

Sprint reporting is most useful when the team starts cycles deliberately, estimates consistently, and keeps issue statuses current.

For step-by-step review guidance, read Close and review a sprint.

Capacity summary

Cycle cards, cycle detail, and Sprint Reports show a capacity summary. The summary compares completed work with total work in the cycle.

When issues have estimates, the summary uses points. When estimates are absent, it falls back to issue counts. For active cycles, the summary can also show days left, ends today, or overdue.

Use the capacity bar as a quick signal, not the whole story. Always check scope changes and incomplete work before judging a sprint.

Sprint Report

The Sprint Report is available for active and closed cycles. Planned cycles do not have a report yet because no sprint has started.

The report includes:

Cycle name, number, date range, and description.
Completed points vs total points.
Carried issue count and carry-over destination for closed cycles.
Burnup chart.
Commitment and scope-change sections when a start snapshot exists.

Committed

Committed shows the issues that were in scope when the sprint started. This is the baseline for sprint review.

Use it to ask:

Was the original commitment realistic?
Did the team understand the work at start?
Did committed issues have owners, estimates, and enough context?

Completed during sprint

Completed during sprint shows issues that finished inside the sprint window.

Use it to distinguish work that actually completed during the sprint from work that was merely in the cycle at close.

Incomplete carried

The incomplete section explains what happened to unfinished issues when the cycle closed:

Incomplete (moved to backlog).
Incomplete (moved to next sprint).
Incomplete (kept on this sprint).
Incomplete (carried) when the exact policy is not available.

Use this section during retrospective to understand what did not finish and why.

Added and removed during sprint

Added during sprint shows issues added after sprint start. Removed during sprint shows issues removed after start.

These sections make scope change visible. A sprint can miss its original plan because work took longer than expected, because scope grew, or because priorities changed. Scope-change sections help separate those explanations.

Estimate changes

Estimate changes shows issues whose point estimate changed after sprint start.

Estimate changes are not automatically bad. They can reflect learning. They are worth reviewing when they happen often, happen late, or hide major scope growth.

Burnup

Burnup shows total sprint scope vs completed points. It is especially useful when scope changes during the sprint because it shows both completed work and scope growth.

Use burnup to answer:

Did completed work increase steadily?
Did total scope grow after start?
Did scope growth explain missed commitments?

Burndown

Burndown shows remaining sprint points vs an ideal burn line.

Use burndown to answer:

Is the active sprint trending toward completion?
Did work remain flat for too long?
Did a late change add too much remaining work?

Burndown is most useful when issue estimates are current and done statuses are updated promptly.

Velocity

Velocity shows completed vs committed story points per closed sprint.

Use velocity as planning context, not a target. It helps the team choose future scope based on recent delivery patterns.

Historical sprint picker

Insights includes a cycle picker. When no cycle is selected in the URL, Tixio defaults to the active cycle, then the newest closed cycle if no active cycle exists.

Use historical cycle selection to compare recent sprint reports, burnup, burndown, and velocity patterns.

How to interpret sprint data

Ask these questions in review:

Did we commit the right amount of work?
How much scope changed after start?
Did incomplete work move to the right place?
Were estimates stable enough to plan from?
Did blockers show up in status and comments?
What should change before the next sprint starts?