The Developers track the remaining work toward the Sprint Goal. They own the Sprint Backlog, so they are the ones who know what is left and adapt the plan.
Exam Question
Who is accountable for tracking the remaining work toward the Sprint Goal? (choose the best answer)
- A. The Scrum Master.
- B. The Project Manager.
- C. The Product Owner.
- D. The Developers.
Correct Answer
D. The Developers.
Why This Is the Correct Answer
The Scrum Guide describes the Sprint Backlog as “a plan by and for the Developers.” It calls the Sprint Backlog a highly visible, real-time picture of the work the Developers plan to accomplish to achieve the Sprint Goal. Because they own that plan, they keep track of the work remaining. The Daily Scrum is their daily check: it exists to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. Tools such as burn-down charts are optional. The Scrum Master may coach on how to make progress visible, but does not track it for the team.
Why the Other Options Are Wrong
A. The Scrum Master. The Scrum Master helps the team stay effective but is not accountable for tracking Sprint work.
B. The Project Manager. Scrum has no Project Manager accountability.
C. The Product Owner. The Product Owner tracks progress toward the Product Goal, not the remaining work of the Sprint.
Exam Tip
Split tracking questions by scope. Sprint Goal progress belongs to the Developers; Product Goal progress belongs to the Product Owner.
Key Takeaways
- The Developers own the Sprint Backlog and its progress.
- The Daily Scrum inspects progress toward the Sprint Goal.
- Burn-down charts are optional techniques.

Get ready for the official PSM I exam
480 PSM I practice questions, each with an in-depth explanation like the one above.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 80 random questions in 60 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSM I exam fee ($200) is paid separately to Scrum.org.
More PSM I exam questions
- True or False: Cross-functional teams are optimized to work on one technical layer of a system only (e.g. GUI, database, middle tier, interfaces).
- What are the advantages of keeping component teams while starting Scrum?
- What are three things to consider when deciding to move away from such component teams toward feature teams?
- User documentation is part of your Definition of Done. However, there are not enough technical writers for all teams. Your Scrum Team does not have a Technical Writer. What should the Scrum Team do?” (PSM I)
- What does it mean for a Scrum Team to be cross-functional?” (PSM I)
