What does the Product Backlog contain?

• A. A list of completed features
• B. An ordered list of everything known to be needed in the product
• C. A fixed plan
• D. A list of tasks for Developers

Answer: (B)

The Product Backlog is an ordered list of everything known to be needed in the product. That ordering matters because it guides what the team should tackle next, prioritizing by value, risk, and dependencies so the most important work is considered first. It’s a living artifact that evolves as new information emerges, requirements change, and feedback arrives.

This explains why the backlog isn’t just a list of completed features, a fixed plan, or a simple set of tasks for developers. It represents all work needed to deliver and maintain the product, including new features, enhancements, fixes, technical work, and even research spikes. Individual backlog items are typically described in a way that makes them understandable and estimable, often as user stories or similar units, and they can be refined and split as needed so they can be delivered within a sprint if possible. The Product Owner is responsible for maintaining and ordering the backlog to maximize value, while the team collaborates through backlog refinement to ensure items are ready for sprint planning.