Burndown Charts: Read Remaining Work Without Hiding Scope Changes

A burndown chart plots how much work remains over a period. The horizontal axis is time. The vertical axis is the amount of unfinished work, measured in one consistent unit such as story points or hours.

The line is useful when it starts a specific conversation: what is waiting, what changed and what can the team finish in the time left? It becomes misleading when people lower estimates just to make it slope down.

A 40-point, 10-day example

Suppose a team starts a ten-day planning period with 40 points of agreed work. A straight ideal line falls by four points per day. That is a reference for the example, not a promise that a team will finish the same amount every day.

The workbook includes the complete day-by-day sample through day seven. Later actuals are blank because those observations have not been recorded. A future blank must not be entered as zero: zero says that no work remains.

The simple ideal-line formula

Ideal remaining = Starting work × (1 − Elapsed intervals ÷ Total intervals)

For day five in this example: 40 × (1 − 5 ÷ 10) = 20 points. Keep the start and end convention consistent. Ten daily intervals need an initial day-zero observation plus ten later observations.

The actual line comes from the work record. If your team counts an item only when it meets the agreed completion rule, keep using that rule. Do not switch between completed-task counts, points and recorded hours halfway through the period.

What a flat or rising line can mean

A flat line may mean that work is waiting for review, tasks are too large to finish within the period, records have not been updated, or the team is blocked. Ask which explanation fits before changing the plan.

A rising line can reflect added scope or a revised estimate. Record the change and its reason. If another eight points enter the plan, the team has a different commitment from the one it started with. A burnup chart, which can show completed work and total scope separately, may make that situation easier to explain.

Download the worked burndown example

Download the project planning workbook (.xlsx). The Burndown sheet has an editable starting estimate, a planning period of up to ten intervals, daily remaining-work inputs and a chart linked to those cells. Amber cells are inputs. The Schedule sheet also includes a simple Gantt view.

Replace the fictional observations with your own. Leave unobserved actuals empty, and use the note column to explain a blocker or scope change. The ideal line uses the starting estimate; it does not automatically revise the baseline when scope changes.

Use the chart alongside the assignments

A burndown chart cannot show whether the right result was delivered or whether one person is carrying all the review work. Read it alongside the tasks, acceptance criteria and current blockers. Avoid treating points completed as an individual performance score.

In Taaskyz, keep those assignments and updates in the project tracking workflow. The downloadable chart is a separate planning workbook; it is not a claim that Taaskyz has a built-in burndown chart.

For Jira-specific chart behaviour, refer to Atlassian’s burndown chart guide. For a starting delivery routine, read the small-team agile planning guide.