Which Scrum artifact provides transparency into requirements and work?

The Product Backlog serves as the primary artifact that provides transparency into requirements and work. It is a dynamic, ordered list of everything that might be needed in the product, and it is continuously updated and refined throughout the project. This artifact reflects the necessary work to be completed in order to meet the product's goals, capturing items such as user stories, features, enhancements, and bug fixes.

Because the items in the Product Backlog are prioritized by the Product Owner based on factors like value, risk, and dependencies, team members and stakeholders have a clear understanding of the current status of requirements and the overall direction of the project. This visibility enables effective planning and allows the Scrum Team to adapt to changes rapidly by revisiting and adjusting the backlog as needed.

While the other options, like the Burndown Chart and Velocity Chart, contribute to tracking progress and performance over time, they do not provide the same comprehensive view of requirements and ongoing work as the Product Backlog does. The Sprint Backlog, while also important for tracking work specific to a sprint, is a subset of the Product Backlog and doesn't encompass the entire scope of requirements needed for the project.