Velocity
What each sprint committed to, next to what it delivered. Plan the next one from history instead of optimism.
Burndown
How the remaining work actually melted, day by day — with the chart stating where the measurement started.
Cycle & lead time
How long after it was raised a piece of work finishes, and how long it takes once someone starts on it.
How it works
A sprint remembers what it promised
When a sprint starts, the points and task count it took on are stamped. This is necessary: because unfinished work is carried out of a sprint at close, nobody looking afterwards can reconstruct the commitment — and every sprint would draw as 100% forever.
Done is a moment, not a column
A task is stamped when it is finished, and the stamp is removed if it leaves that column. Because “where” and “when” are separate, reorganising your columns later does not rewrite your past charts.
Work with no start is left out of cycle time
Cycle time runs from the first move to completion. A task that never moved has no start — rather than quietly falling back to its lead time and skewing the average, it is excluded.
Estimation accuracy and point spread
Compare estimated hours against actual, and see how your team spreads its story points — if everything is a 5, estimation has become a ritual.
Which plan is this on?
Sprints, story points and the backlog are on every plan. Velocity and burndown live on the project insights page; flow analytics (cycle time, estimation accuracy, point distribution) and the time series require Pro.
Frequently asked questions
We do not use story points — is this still useful?
Yes. Velocity reads two ways, in points and in task count, and cycle time and lead time are independent of estimation entirely — you can measure your flow without ever assigning a point.
Will I see velocity for my past sprints?
The delivery side, yes: what closed sprints finished was computed from history. The commitment side is deliberately left empty — for a sprint that closed before the measurement existed, what was promised cannot be recovered, and inventing it would make the chart useless.
What work does the burndown count?
The chart states its own scope: whether it is measuring story points or task count, and where it started, is written on the chart. Reading the axis and reading the measurement boundary are two different things.