Which document serves as a living artifact of product requirements?

The Product Backlog is recognized as a living artifact of product requirements because it continuously evolves based on changing needs, stakeholder feedback, and insights gained throughout the development process. It is essentially a prioritized list of all the work that remains to be done in the project, encompassing both functional and non-functional requirements. As items are added, removed, or reprioritized, the Product Backlog reflects the most current understanding of what is necessary to deliver a successful product. This adaptability makes it crucial for guiding the development team and ensuring alignment with stakeholder expectations.

While documents like the Sprint Backlog detail the work planned for a specific Sprint and the Definition of Done provides criteria for quality, neither serves as a comprehensive and evolving list of product requirements. Similarly, the Sprint Review document captures insights and feedback from the Sprint but does not function as a living requirements artifact. Thus, the Product Backlog is the appropriate choice for representing an ongoing and adaptive account of what requirements need to be addressed over time.