A burndown chart answers "will we finish this sprint?" by showing the work left day by day. A velocity chart answers "how much should we take on next sprint?" by showing how much the team completed in each recent sprint. Watch burndown during the sprint and velocity when planning the next one. Never use velocity to compare one team with another.
The burndown chart: today's sprint
A burndown chart plots work remaining against days left. It starts at everything committed and should reach zero on the last day. The useful part is not the line itself but the shape it makes.
- A steady slope means work is finishing throughout the sprint. This is what you want.
- A flat line, then a cliff means everything was started at once and finished at the end. It works until the week something goes wrong, and then nothing ships.
- A line that rises means work was added mid-sprint. Occasionally that is a genuine emergency. Often it is scope arriving through a side door.
- A line that stalls above zero means the last items were bigger than anyone thought.
Read it daily, in standup, in ten seconds. Its job is to prompt a conversation on Wednesday rather than a surprise on Friday.
The velocity chart: the next few sprints
A velocity chart shows how much the team actually completed in each past sprint, measured in whatever unit you estimate in. One sprint tells you nothing. Three to five sprints tell you what this team, in these conditions, can reliably take on.
Use it in planning as a sanity check: if the last four sprints delivered around twenty units and somebody proposes thirty-five, the conversation that follows is the point of the chart.
How they differ
| Burndown | Velocity | |
|---|---|---|
| Question it answers | Will we finish this sprint? | How much can we take on next sprint? |
| Time covered | The current sprint | The last several sprints |
| When to look | Daily | At planning |
| Who it helps | The team, during the sprint | The team and whoever sets priorities |
| Reliable after | Immediately | Three to five sprints |
| Main failure | Updated too late to act on | Treated as a productivity score |
The mistake that ruins velocity
Velocity is a planning aid that describes one team. It is not productivity, and it is not comparable between teams, because it depends entirely on how that team sizes work. A team that calls something eight and a team that calls the same thing three will show very different numbers while delivering identical software.
The moment velocity becomes a target, estimates inflate. The chart keeps rising, the team looks faster, and nothing ships sooner. If a manager wants a number, give them delivered outcomes or cycle time instead.
What to watch when neither chart helps
Both charts assume work is estimated and batched into sprints. Teams running continuous delivery often find two other measures more useful:
- Cycle time: how long an item takes from start to done. It shows where work waits.
- Throughput: how many items finish per week. Simple to count, hard to game.
If your team has drifted away from sprints, these are the honest alternatives.
Getting both without extra work
Charts only help if they are current, which means they have to come from the work itself rather than someone updating a spreadsheet on Thursday.
In WeTa loopin, burndown and velocity update as tasks move, so the sprint picture is accurate without anyone maintaining it. Blocked work is flagged while there is still time to act, and the cycle from idea to release stays visible in one place. There is more on running the sprint itself in our guide to sprint planning for small teams.
Frequently asked questions
What is the difference between burndown and velocity?
A burndown chart shows work remaining inside the current sprint, so it answers whether you will finish. A velocity chart shows how much a team completed in each past sprint, so it answers how much to plan next time.
Is a flat burndown line bad?
It usually means work is in progress but nothing has finished. Flat for a day or two is normal. Flat until the last two days suggests items are too big or everything was started at once.
Can we compare velocity between two teams?
No. Velocity depends on how each team sizes work, so one team's eight is another team's three. Comparing teams on velocity encourages estimate inflation and tells you nothing useful.
How many sprints before velocity is reliable?
Three to five sprints with a stable team. Change the team or the sprint length and the number resets, because the figure describes that team in those conditions.
Should we show these charts to management?
Show the burndown for the current sprint and the trend of velocity, never the velocity number as a performance target. The moment it becomes a target, the team raises its estimates and the chart stops meaning anything.
Run your next sprint in WeTa loopin
Boards, sprints, burndown and releases in one place. Free for up to 3 users, so you can try a full sprint first.
Request a Demo Download the WeTa loopin brochure