Answering: “Why would you expect a Product Owner to care that the Scrum Team adheres to its Definition of Done?”

Why would you expect a Product Owner to care that the Scrum Team adheres to its Definition of Done?
(choose the best two answers)
A. The Product Owner should not concern themselves with meeting the Definition of Done, it is the Developer’s responsibility.
B. To forecast the team’s productivity over time.
C. The Definition of Done can affect the product’s total cost of ownership.
D. To be able to punish the team when they don’t meet their velocity goal for the Sprint.
E. To have complete transparency into what has been done at the end of each Sprint.

Answering: “Why would you expect a Product Owner to care that the Scrum Team adheres to its Definition of Done?” Read More »

Answering: “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 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?”

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 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. 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.

Answering: “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 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?” Read More »

Answering: “Your management has asked you to take the lead in the development of a new product. Six teams new to Scrum will build this product.”

Your management has asked you to take the lead in the development of a new product. Six teams new to Scrum will build this product.
You have gathered a number of requirements and ideas into an early form of a Product Backlog. How would you minimize dependencies between the Scrum Teams?
(choose the best answer)
A. You create an independent Product Backlog per Scrum Team.
B. You identify the dependencies and re-order the Product Backlog for them.
C. You work with the Developers on how to best analyze and break apart the work.
D. You divide the Product Backlog items among the six Product Owners.
E. You raise this as an impediment with the Scrum Master.

Answering: “Your management has asked you to take the lead in the development of a new product. Six teams new to Scrum will build this product.” Read More »

You cannot copy content of this page