PMP · Question #1035
A product owner is trying to understand how many of the user stones have been completed within a 2-week sprint. How should the project manager approach this situation?
The correct answer is D. Share the burndown chart with the product owner. To provide the product owner with a clear understanding of sprint progress and completed user stories, the project manager should share the burndown chart.
Question
A product owner is trying to understand how many of the user stones have been completed within a 2-week sprint. How should the project manager approach this situation?
Options
- AUse retrospectives to deliver the finished products.
- BInvite the product owner to regular standup meetings.
- CHave a face-to-face conversation with the product owner.
- DShare the burndown chart with the product owner.
How the community answered
(48 responses)- A4% (2)
- B6% (3)
- C2% (1)
- D88% (42)
Why each option
To provide the product owner with a clear understanding of sprint progress and completed user stories, the project manager should share the burndown chart.
Retrospectives are for process improvement and reflection, not for tracking or delivering finished products; finished products are typically demonstrated in a sprint review.
While product owners can attend standups, the standup itself is for team synchronization and not primarily designed for detailed reporting on the completion status of all user stories.
A face-to-face conversation can provide qualitative updates, but a burndown chart offers a quantitative, objective, and continuously updated visual representation of progress, which is more efficient and accurate for tracking multiple items.
A burndown chart is a key agile metric that visually represents the amount of work remaining versus time in a sprint. It effectively shows the progress of completing user stories and provides a transparent way for the product owner to track how many items have been completed and the overall likelihood of achieving the sprint goal.
Concept tested: Agile progress tracking; Burndown charts
Source: https://www.scrum.org/resources/what-is-a-burndown-chart
Topics
Community Discussion
7
Brenda K.May 24, 2026D is correct and it is a 10-second answer. The burndown chart is the tool that shows exactly how many user stories are completed versus remaining in a sprint, so the product owner can see progress at a glance without eating up your time.
Mateus R.May 25, 2026Spot on, and the burndown chart is the dashboard gauge on your car, the sprint backlog is the gas tank, so when that line trends down toward zero you know the team is burning through stories at a sustainable pace.
Lena V.Jun 23, 2026D. Burndown chart literally shows completed work vs sprint scope.
Olusegun A.May 21, 2026I first leaned toward B since bringing the PO to standups seems logical for visibility, but the question is specifically about tracking completed work against the sprint scope. D is the right call because a burndown chart is the artifact that visually shows exactly how many story points are done and what remains, which is what the PO is asking for.
Mateus R.May 31, 2026D. Tempted by B, but the burndown chart literally counts completed work.
Luis F.Jun 11, 2026Picking C, the PO just needs a quick verbal status check, not a chart.
Olusegun A.Jun 12, 2026D is correct here, Luis. The PO asking for a quick status check is exactly the kind of lightweight, in-person communication the PMBOK favors for fast informal updates, whereas C implies a formal artifact the scenario does not call for.