What is a Product Backlog? (Choose the best answer)

The Product Backlog is the single, authoritative source for all work that needs to be done on the product. It is an emergent, ordered list of features, functions, requirements, enhancements, and fixes. The term "living artifact" accurately describes its dynamic nature; it is never complete and evolves continuously as the product and its environment change. The Product Owner is responsible for managing this backlog, including its content, availability, and ordering, for the entire lifecycle of the product.

B. This describes a fixed-scope plan, which is contrary to the agile principle of embracing change. The Product Backlog is emergent, not a formally approved list for a set period.
C. Scrum mandates a single Product Backlog for a product to ensure all work is visible and prioritized against a common goal. A separate "Technology Backlog" is a common anti-pattern.
D. While a backlog item might reference external documents like Use Cases, the backlog itself consists of descriptive items (e.g., User Stories), not merely a list of references.

1. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. In the "Scrum Artifacts" section, the Product Backlog is described as "an emergent, ordered list of what is needed to improve the product... The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is a living artifact." (p. 11).

2. Pichler, R. (2010). Agile Product Management with Scrum: Creating Products that Customers Love. Addison-Wesley Professional. In Chapter 3, "Working with the Product Backlog," Pichler states, "The product backlog is a living artifact that is updated on a regular basis... As long as a product exists, its backlog is never complete." (p. 31).

3. University of Virginia, Darden School of Business. (2018). Agile Development: A Technical Note. Darden Business Publishing, UV7578. This note describes the Product Backlog as a "living document" that is "continuously updated by the product owner to reflect changes in the client’s needs, new ideas or insights, and a revised understanding of the product." (p. 4).