A Product Backlog is: (choose the best three answers)

Question

Options

• AAn exhaustive list of upfront approved requirements to be implemented.
• BManaged by the Product Owner.
• CAn inventory of things to be done for the Product.
• DOrdered based on priority, value, dependencies, and risk.
• EOnly visible to the Product Owner and stakeholders.

Explanation

B, C, and D are the correct answers.

B is correct because the Scrum Guide explicitly states the Product Owner is accountable for managing the Product Backlog - including its content, availability, and ordering. C is correct because the Product Backlog is defined as an emergent, ordered list of everything needed to improve the product - essentially an inventory of work. D is correct because the PO orders backlog items considering multiple factors: business value, risk, dependencies, and priority, not just importance alone.

A is wrong because the Product Backlog is never exhaustive or upfront-approved - it's a living artifact that evolves continuously throughout the project. Treating it as a fixed requirements list is a waterfall concept, not Scrum. E is wrong because the Product Backlog is fully transparent and accessible to the entire Scrum Team and stakeholders - transparency is a core Scrum pillar.

Memory tip: Think of the Product Backlog as a living shopping list - the Product Owner writes and reorders it (B), it lists everything you might need (C), and items are ranked by what gives you the most value for your effort (D). It's never locked, never secret.

No community discussion yet for this question.