Burnup Chart

A visual chart showing the cumulative amount of work finished as a product release progresses toward delivery.

Key Points

  • Plots completed work over time to show progress toward a release.
  • Usually includes a total scope line, making scope changes visible.
  • Supports forecasting completion by projecting current progress trends.
  • Differs from a burndown chart, which tracks remaining work instead of completed work.

Example

A Scrum team tracks story points delivered each sprint. The burnup chart shows the cumulative points completed rising each iteration, while the total scope line adjusts when new stories are added. By comparing the slope of completed work to the scope line, the product owner estimates when the team will reach the release goal.

PMP Example Question

Which artifact best displays cumulative work completed over time against a target scope line to reveal progress and scope changes for a release?

  1. Burnup chart
  2. Burndown chart
  3. Cumulative flow diagram
  4. Velocity chart

Correct Answer: A — Burnup chart

Explanation: A burnup chart shows cumulative completed work and often includes a total scope line, making it ideal for visualizing progress and scope changes toward a release.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Launch your Agile career!

HK School of Management and Technology helps you learn Agile and Scrum with practical playbooks, AI-powered prompts, and real-world workflows for planning and delivery. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More