Answering: “Scrum is based on empiricism. All of its artifacts must be transparent to ensure sufficient accuracy of inspection. How can the Scrum Team maintain the Product Backlog to maximize its transparency?” (PSM I)

The Scrum Team keeps the Product Backlog transparent by updating it continuously as new insights appear. Restricting updates to certain meetings or fixing item sizes does not help.

Exam Question

Scrum is based on empiricism. All of its artifacts must be transparent to ensure sufficient accuracy of inspection. How can the Scrum Team maintain the Product Backlog to maximize its transparency? (choose the best answer)

• A. The Product Backlog items must be sized such that the highest ordered items are no bigger than a Sprint.
• B. Product Backlog is only updated at the Sprint Review, when both the Scrum Team and the stakeholders are available.
• C. Product Backlog is only updated at a release planning meeting with the stakeholders and the change control board present.
• D. The Product Backlog is continually kept up to date with the most recent insights.
• E. Product Backlog items should hold no more than 8 points of work, which is average in the range of acceptable sizes of 1, 2, 3, 5, 8, and 13.

Correct Answer

D. The Product Backlog is continually kept up to date with the most recent insights.

Why This Is the Correct Answer

The Product Backlog is emergent. It changes whenever the Scrum Team learns something about the product, the market or the users. The Scrum Guide describes refinement as “an ongoing activity to add details, such as a description, order, and size.” If the backlog only reflects what was known at the last Sprint Review or the last release meeting, inspection is based on stale information. The Guide warns that “Low transparency can lead to decisions that diminish value and increase risk.” Keeping it current is what lets the Product Owner and stakeholders make sound decisions at any time.

Why the Other Options Are Wrong

A. Highest ordered items must be no bigger than a Sprint. Items at the top should be small enough to be Done in a Sprint, but that is about readiness, not transparency. On its own it does not keep the backlog accurate.

B. Only updated at the Sprint Review. The Sprint Review is one input, not the only time changes are allowed. Waiting lets the backlog drift from reality.

C. Only updated at a release planning meeting with a change control board. Scrum has no change control board. Formal gates slow learning and keep the backlog out of date.

E. Items hold no more than 8 points. Story points and size caps are not part of Scrum. A size rule says nothing about whether the content is current.

Exam Tip

Watch for the word “only” in Product Backlog questions. Scrum does not restrict when the backlog may change.

Key Takeaways

• The Product Backlog changes as the team learns.
• Refinement is ongoing, not tied to one event.
• Stale information weakens every inspection.