ExamGecko
Question list
Search
Search

Question 44 - PSPO-I discussion

Report
Export

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 accountable 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?

* Stability requirements

* Performance requirements

* Product Functionality

* Documentation

* Fixes

(choose the best answer)

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.
Answers
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.
Answers
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.
Suggested answer: A

Explanation:

The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product.

All types of requirements are acceptable on a Product Backlog, as long as they are aligned with the product vision and goals, and they are transparent, clear, and valuable. The Product Backlog can include stability requirements, performance requirements, product functionality, documentation, fixes, or any other aspects that contribute to the quality and usability of the product.

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.

The Developers are accountable for creating a "Done" Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.

Scrum Guide: https://www.scrumguides.org/scrum-guide.html

Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog

asked 23/09/2024
Jelle Kamp
41 questions
User
Your answer:
0 comments
Sorted by

Leave a comment first