Mark is the Product Owner and he asks you, the Scrum Master what burndown charts actually track. What's the best response for Mark?

A burndown chart is a graphical representation of the work remaining to be done over time. The vertical axis represents the amount of work left (typically measured in story points or hours), while the horizontal axis represents time (e.g., days of a Sprint). The chart's primary purpose is to provide a transparent visualization of progress, showing whether the team is on track to complete the planned work within the specified timeframe, such as a Sprint or a release. It is a forecasting tool that tracks the completion of remaining work.

B. Burndown charts track effort or work units, not the business value delivered. Value is a separate metric managed by the Product Owner.

C. This statement is incomplete. A burndown chart doesn't just show the amount of work left; it crucially tracks this remaining work against time.

D. Burndown charts are used to track remaining work or effort, not the financial cost associated with that work. Cost is a separate project management concern.

1. SCRUMstudy™. (2021). A Guide to the Scrum Body of Knowledge (SBOK® Guide) (4th ed.). Section 8.5.2.1

Burndown Chart. The guide states

"A Burndown Chart is a graph that shows the amount of remaining work in a Sprint on a day-to-day basis." It explicitly links "remaining work" with a "time" dimension.

2. University of Virginia

Department of Computer Science. (n.d.). CS 4740: Software Engineering: Process and Product - Agile Methods. Course materials. The course defines a burndown chart as "a graphical representation of work left to do versus time

" directly supporting the concept of tracking remaining work across a time period.

3. Hohl

P.

et al. (2018). Backlog Refinement in Large-Scale Agile System Development. In Product-Focused Software Process Improvement (PROFES 2018). Springer. p. 12. The paper describes burndown charts as a tool to "monitor the progress within a sprint by showing the remaining work." This reinforces the focus on "remaining work." (DOI: https://doi.org/10.1007/978-3-030-03673-71)