THE BURN-UP CHART PLAYBOOK
A step-by-step guide to tracking project progress with real data
What Is a Burn-Up Chart?
A burn-up chart tracks two things over time: the total scope of your project as you understand it today, and how much of that scope is actually done. Plotted together, the two lines tell you at a glance whether you’re on pace, whether scope is growing faster than the team can absorb it, and where risk is building — early enough to do something about it.
It runs on four data points you likely already have: the expected outcome, a sized backlog, story status, and dates. Everything else is built from there.
| Fun Fact: My friend and mentor, Rodney, introduced this to me. He provided the initial template and instructions. It’s really all him. It’s always great to have someone who helps bring you to the next level. |
Why It Works
- Runs on the backlog your team already maintains — no extra reporting work.
- Forces real discovery: sizing stories surfaces open questions and technical unknowns before they become blockers.
- Reflects actual work, not a translated summary — easy to explain and easy to defend to stakeholders.
- Updates itself as scope changes (new stories) or work completes (status changes).
- Works with Scrum, Kanban, or a waterfall mindset.
The Playbook
Follow these steps in order the first time you build a burn-up. After that, steps 3–7 repeat every sprint.
Step 1: Define the outcome
Start with a clear charter — the North Star for what you’re building — and back it up with specific, testable requirements.
- Charter example: “build a website to sell my pottery.”
- Requirement example: “As a user, I need to filter by product type (plate, cup, mug, gravy boat) so I can see only what I’m looking for.”
| PRO TIP: Bring an authoritative product person into backlog-building sessions so questions get resolved on the spot instead of stalling refinement. |
Step 2: Decide what you need to track
Before you size anything, settle how you’ll categorize it:
- Do stories need to be flagged by workstream or critical path (e.g., a Jira Component or Label)?
- What does each status on your board actually mean?
- How are you structuring epics?
Step 3: Build and size the backlog
Break the project into stories and size each one.
- It’s normal to end up with several large stories (5+ points) on the first pass — you can split those later.
- Expect this to take more than one refinement session. Work through it.
| PRO TIP: AI can help draft or size stories, but you’re accountable for the outcome — stay closely engaged with the actual work. |
Step 4: Execute in sprints
Close stories as they’re completed and keep the board current. The burn-up is only as accurate as the board behind it.
Step 5: Refine every sprint
Treat refinement as ongoing, not a one-time setup step.
- Break down large stories as you learn more about them.
- Watch for anything that should change your approach — a surprise from the last sprint, or new product feedback.
- Update the backlog to reflect scope changes as soon as you know about them.
Step 6: Move the data into a reporting structure
Export the backlog into a spreadsheet or similar reporting tool so it’s ready to chart.
Step 7: Generate the chart
Feed the exported data to an AI tool (or a manual template, if you don’t use AI) to build the graph. Automate this on a schedule or run it manually each sprint.
| SAMPLE AI PROMPT Context: This project is tracking the points burn-up in an agile project. It sums story points and tracks completed stories against the total. This project must be done by [date]. Process instructions: First, sum the size column — this is the total points needed to complete the project. Then summarize each week (from the week-ending column) where status is ‘done.’ Create a trend line based on the average points completed per week needed to finish the work. Finally, plot a line of total points in the ‘done’ state. The x-axis must be the Friday of each week. Put this into an easy-to-read graph. |
Quick-Reference Tips
- Keep a product decision-maker in every backlog session — it’s the single biggest time-saver.
- Don’t stall on big, unrefined stories early. Log them, size them roughly, and revisit later.
- For multi-team or multi-critical-path projects, tag stories with metadata so you can slice the burn-up by workstream.
- Treat the burn-up as a living document — revisit and correct it every sprint, not just at kickoff.
Know Its Limits
A burn-up chart is not a dependency-management tool. It can hint at risk building up along a critical path, but it won’t map dependencies between stories for you — pair it with a separate dependency view if your project needs one.