What is the product backlog?

• A. A prioritized list of user stories from which developers pull work
• B. list of criteria for unit and user acceptance testing
• C. list of criteria a user story must meet before it can be considered complete
• D. a list of high level features or characteristics that will drive the product value

Answer: (A)

In Agile product development, the product backlog is a dynamic, ordered list of work items that define what the team will build next. It’s typically made up of user stories, bugs, and other work, and it’s prioritized by value, risk, and dependencies. The Product Owner keeps this backlog refined and up-to-date, so the items at the top represent the most valuable work to tackle first. During sprint planning, the team pulls the highest-priority items that fit their capacity into the sprint, turning them into concrete work for that iteration.

This idea isn’t about testing plans, acceptance criteria, or a simple catalog of features. Testing criteria and acceptance criteria live with individual backlog items, and a high-level feature list describes goals or vision rather than the actionable queue the team commits to delivering.