All Scrum artifacts must be transparent to ensure sufficient accuracy of inspection. Which two measures ensure that the Product Backlog is transparent? (choose the best two answers)

Question

Options

• AThe Product Backlog is ordered.
• BThe Product Backlog is available to all stakeholders.
• CEach Product Backlog item has a MoSCoW priority.
• DThe Product Backlog only has work for the next 2 Sprints.
• EThe Product Backlog is managed using a web-based tool.

Explanation

A (ordered) and B (available to all stakeholders) are the two correct measures.

Ordering the Product Backlog ensures transparency by making priorities visible and unambiguous - anyone inspecting it can immediately see what is most important and why, which is a core requirement in the Scrum Guide. Availability to all stakeholders satisfies the definition of transparency itself: an artifact is transparent only when those who need to inspect it actually can inspect it. C is wrong because MoSCoW is an external prioritization technique not mentioned in Scrum - Scrum uses ordering, not labeling schemes. D is wrong because the Product Backlog intentionally holds all known future work, not just the next two Sprints; limiting it artificially hides information rather than making it transparent. E is wrong because the tool used to manage the backlog is irrelevant to transparency - a handwritten list shared openly is more transparent than a locked-down Jira board.

Memory tip: Link "transparency" to its two natural requirements - what is in it must be clear (ordered = priorities visible) and who can see it must be everyone (available to stakeholders). If an answer describes a specific tool, a capped scope, or a non-Scrum labeling method, it's a distractor.

No community discussion yet for this question.