Tutorial
Close a sprint and read the burndown
End the sprint cleanly, carry open cards over, and read from the burndown what actually happened — including where the chart honestly guesses.
Last updated:
Closing is the moment a sprint turns into data: what got done, what did not, and what that says about the next one. Zuuna turns it into a report and a burndown — and is more honest in one spot than most tools. Sprints belong to the Developer plan.
What you need
- A running sprint whose time is up — or whose work is done.
- Two decisions: which column counts as done, and where does the rest go?
1. Close the sprint
At close, Zuuna asks two things: the done column (whatever stands there counts as finished) and the carry-over destination — unfinished cards go back to the backlog or straight into the next planned sprint. Nothing is silently counted as done.
2. Know what happens to the board
The sprint board is archived, never deleted. The difference carries weight: deletion would take the cards with it; the archive keeps every card, comment and move — read-only. Six months later you can still see what actually happened in sprint 9.
3. Open the burndown
Two lines: the ideal (even burn from start to end) and the actual. The gap between them is the real information — persistently above means over-committed, persistently below means planned too cautiously.
4. Understand upward spikes
When remaining work rises mid-sprint, the team did not slow down — scope was added. The burndown makes visible what stays invisible day to day: the "just this one more card" decisions. Three such jumps in three sprints are not a chart detail; they are a retro topic.
5. Switch the unit
The same chart in three views: story points, hours, task count. Teams that do not estimate use the count — a burndown without story points beats no burndown.
6. Read velocity and the projection
Closed sprints yield the velocity — what the team actually finishes per sprint. In the running sprint Zuuna projects a likely finish at the current pace. And one piece of honesty worth knowing: dots before the first daily snapshot are reconstructed from the activity log and drawn hollow — the chart guesses visibly, never silently. Likewise: for cards still standing on the archived board the state is exact; for carried-over ones, only up to the carry-over.
7. Look up past sprints
Every closed sprint keeps its report and burndown. Three of them side by side answer the question planning actually needs: how much do we honestly finish?
Troubleshooting
- The done total looks too low. The wrong column was chosen as done. Correct it at the next close.
- The burndown only turns solid mid-sprint. Not a bug: earlier days are reconstructed (hollow dots); measurement starts with the first snapshot.
- The projection is missing. It needs closed sprints as a basis — after the first sprint there is no velocity yet.
Next steps
- Plan the next sprint — now with a real velocity.
- Plan sprint capacity.
- Project management for developers.
FAQ
Where do I see old sprints?
In the group's sprint overview. Every closed sprint keeps its report and its burndown — none of it expires.
Why are some dots in the chart hollow?
Because they are reconstructed, not measured. For days before the first daily snapshot, Zuuna rebuilds the state from the activity log and marks those dots as approximate — the chart guesses visibly, never silently.
What happens to unfinished cards?
You decide at close: back to the backlog, or straight into the next sprint. Nothing is lost and nothing is silently counted as done.
Is the board deleted?
No — archived. The difference matters: deleting a board would take its cards with it; the archive keeps everything, read-only.
How is velocity calculated?
From what closed sprints actually finished, in the unit you plan in. It is the basis of the projection in the running sprint.