What Is Burndown Chart? Meaning, How to Read One and a Worked Example
For project managers, product owners and team leads running sprints: what a burndown chart is, how to read it and what to do when the line goes flat.
What is burndown chart? It is a simple line chart of how much work is left in a sprint, drawn day by day against an ideal straight line to zero. It shows at a glance whether the team will finish what it committed.
Indian software, agency and product teams often run sprints on sticky notes and chat. Status is discussed daily, but nobody sees the trend until the last two days, when it is too late to rescope.
This page explains the chart, works through an illustrative example and shows how Apragya draws it from the tasks the team already updates.
Burndown chart meaning and how to read it
A burndown chart plots the work remaining in a sprint or project against time. The vertical axis is remaining work, in tasks, story points or hours. The horizontal axis is days. An ideal line runs straight from the total at the start to zero at the end.
The actual line shows what is really left each day. Above the ideal line means the team is behind; below means ahead. A flat stretch means nothing is being finished, and a jump up means work was added mid-sprint.
A worked example: a two-week sprint of 10 working days starts with 40 story points. The ideal line drops 4 points a day. On day 5, the ideal is 20 but 28 remain, so the team is 8 points behind and must either speed up or move work out.
A burnup chart shows the same story upside down: work completed rising towards a total scope line, which makes scope changes easier to see.
- Fix the sprint's start and end dates.
- Total the work committed at the start.
- Draw the ideal line from that total to zero.
- Plot remaining work at the end of each day.
- Discuss the gap at the daily stand-up and act early.
An example: a Pune product team's sprint
Take an illustrative six-person team building a billing feature in a two-week sprint with 24 tasks.
The sprint, read from the burndown
Day 1
24 tasks committed; ideal line drawn to zero.Day 4
Line flat; two tasks blocked on an API.Day 5
Stand-up agrees to unblock and move one task out.Day 8
Actual line back near the ideal.Day 10
22 done; two carried to the next sprint.
Because the flat line was noticed on day four, the team fixed the blocker and moved one task out calmly. The sprint closed with 22 of 24 tasks done and no weekend work.
How Apragya shows an agile burndown chart
Step 1 of 5
Sprints
Group tasks into sprints with start and end dates.
- Sprints: Group tasks into sprints with start and end dates.
- Task status: Tasks move across the board as the team works.
- Burndown view: Remaining open tasks in a sprint against an ideal line.
- Story points and velocity: Estimate in points and read the velocity trend across sprints.
- Scope creep check: A sprint can be checked for work added after it started.
Burndown vs burnup chart, and why the source matters
Both charts are only as good as task updates. When the chart reads the same board the team uses every day, nobody has to redraw it, and the picture in the stand-up matches the work.
A hand-drawn burndown, against Apragya
| Feature | Whiteboard or spreadsheet | Apragya |
|---|---|---|
| Data | Counted each evening | From task status on the board |
| Ideal line | Drawn by hand | Drawn from the sprint dates |
| Scope changes | Easy to miss | Scope creep check per sprint |
| Across sprints | Separate sheet | Velocity trend |
| Retrospective | From memory | Recorded on the sprint |
Checked against public information on 16 September 2026.
What sets Apragya apart for project teams
Time logs
Hours logged against tasks feed project cost and billing.
Gantt and calendar
The same tasks in board, list, calendar and Gantt views.
Critical path
Scheduling shows which tasks set the finish date.
AI you can put to work
An agent can summarise sprint risks for the stand-up.
Access by role
Clients and contractors see only what they should.
Project financials
Budget, cost and billing on the same project.
See sprints, backlog and tasks. Related terms: critical path and change request.
Getting started with a sprint burndown
- Create a sprint with start and end dates.
- Move the committed tasks into it.
- Ask the team to update status daily.
- Open the burndown view at each stand-up.
- Review velocity at the retrospective.
Two sprints are usually enough for the team to trust the line.
What it costs to start
Agile burndown charts, answered
Should we burn down tasks, points or hours?
Why does our line stay flat and then drop?
Is a burndown only for software teams?
What if scope changes mid-sprint?
What does it cost to start?
See the sprint before it slips
Set up one sprint, move tasks into it and open the burndown at tomorrow's stand-up.