Feature
Sprints & backlog: Scrum that stays out of the way
Backlog, sprint planning, capacity, planning poker and burndown — on the same board the work already lives on. Included in the Developer plan.
Zuuna's sprints sit as a layer above the board, not beside it. The same cards you drag in Kanban take story points, move into a backlog, get pulled into a sprint and show up again in the burndown. There is no second tool and no export in between.
The backlog
Its own view next to the board, ordered by dragging. You can create a card straight in the backlog without picking a board first — it lands on the right one as soon as it is assigned. For triage there are filters by assignee, epic, priority and free text, bulk actions, and a ready flag. Refinement happens on its own persistent board: pull in unready issues, resolve the questions, size them.
Planning against real capacity
Before a sprint starts you can see who is already over-committed — each member's capacity against the work they are actually carrying, with a load chip on the person. Absences come from the team planner instead of living in a second spreadsheet. When a ticket is shared, the effort can be split — seven hours backend, one hour frontend — so capacity stays honest instead of charging the whole card to one person.
Estimating together
You set story points during refinement or together in planning poker: the moderator starts a round, everyone votes on the same card behind a hidden ballot, and only the reveal shows the spread. That is the point of the exercise — not the average, but the question of why a 3 and a 13 landed on the same ticket.
And afterwards
The burndown shows the ideal line against the work actually remaining: it drops as cards reach the done column and spikes when scope is added. You decide which column means done — sprint completion and the backlog follow it. What is left at the end is velocity as a basis for planning the next sprint, not as a metric about people.
Honest about the plan
Sprints, backlog, planning poker, capacity and burndown are part of the Developer plan. The board itself needs none of them: a team working Kanban and steering flow rather than filling timeboxes does fine without this layer — and should not pay for it.
Estimating is part of it
A backlog only becomes plannable once the cards have a size — estimated blind, as a team, with planning poker. To see the capacity behind it, there is the team planner.
FAQ
Do I need sprints to use Zuuna?
No. Every board works as a plain Kanban board. Sprints are a layer you switch on if your team works in fixed iterations — and leave off if it does not.
Which plan includes sprints?
The Developer plan. Releases, the code graph, the REST API and webhooks are there too, because the same teams tend to need them together.
Do holidays and absences feed into capacity?
Yes. The team planner holds absences and each person's working week, and sprint capacity uses them — instead of somebody adjusting the number by hand.
What happens to unfinished cards at the end of a sprint?
They go back to the backlog and get re-assessed. You decide at completion what carries over, and the done column you chose determines what counted as finished in the first place.