Are all of the following types of requirements acceptable on a Product Backlog?

A Scrum Team has been working on a product for 9 Sprints. A new Product Owner who is new to Scrum joins the team and understands she is accountabile for the Product Backlog. However, she is unsure about the purpose of the Product Backlog. She has read that the Product Backlog should be a list of all user features for the product. She goes to the Scrum Master asking where to put the other types of requirements that are going to be taken into account.

Are all of the following types of requirements acceptable on a Product Backlog? (choose the best answer)

– Stability requirements

– Performance requirements

– Product Functionality

– Documentation

– Fixes
A . Yes, they all belong on the Product Backlog. The Product Backlog is supposed to be the "single source of truth” for all the work for the product.
B . No. Product Backlog is a tool for the Product Owner. The Product Owner represents the users and stakeholders. Other types of requirements should be managed separately by the Developers. They are not the Product Owner’s concern.

View Answer

Answer: A