What describes the role of the Product Backlog in the Scrum framework?

• A. It is the single source of requirements for any changes to be made to the product
• B. It is the primary plan that never changes
• C. It is solely used for the next sprint
• D. It is managed by the developers without PO input

Answer: (A)

The main thing this question tests is who owns and how the backlog is used in Scrum. The Product Backlog is the single source of requirements for any changes to the product. It holds everything needed to deliver the product, including features, improvements, fixes, and technical work, all ordered by value and priority. It’s a living document that the Product Owner continually refines, reprioritizes, and updates based on feedback, learning, and market changes. It isn’t a fixed plan; it evolves as more is learned, and items can be added, removed, split, or re-prioritized over time. The Development Team pulls work from this backlog during sprint planning to create the sprint backlog for the upcoming sprint, but the backlog itself remains the authoritative source for what could be built, not just what will be built in the next sprint.

That’s why the other options don’t fit: Scrum treats the backlog as a dynamic, comprehensive list that can change as circumstances change, not a rigid, never-changing plan. It’s not solely used for the next sprint, since items at various levels of detail exist to guide future work as well. And while developers collaborate and contribute to refinement, the backlog’s content and its ordering are owned by the Product Owner, not managed exclusively by the developers.