What PSPO-I Questions and Answers feature?

If a stakeholder is unhappy with the quality of the product, the Scrum Master can coach the Product Owner on how to effectively communicate this concern to the Developers1. The Scrum Master can also encourage the Product Owner to put quality specifications on the Product Backlog1. This allows the Developers to understand the stakeholder’s expectations and work towards meeting them1. The Developers are responsible for building quality into the product, but the stakeholders (through the Product Owner) are responsible for setting what is expected in terms of product and process quality1.

The Product Owner should care that the Scrum Team adheres to its Definition of Done because:

• It helps to forecast the team’s productivity over time. By having a clear and consistent Definition of Done, the Product Owner can measure the amount of work that the team can deliver in each Sprint and plan accordingly.
• It affects the product’s total cost of ownership. By ensuring that the work done by the team meets the quality standards and expectations of the stakeholders, the Product Owner can reduce the risk of technical debt, rework, defects, and maintenance costs in the future.

References:

• Scrum Guide 2020, page 10: “The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.”
• Scrum Guide 2020, page 11: “The Product Owner is accountable for effective Product Backlog management, which includes … ordering Product Backlog items; and, ensuring that the Product Backlog is transparent, visible and understood.”
• Scrum Guide 2020, page 14: “The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration.”

 The Product Owner must spend enough time with the Developers so that they are confident the Increment will meet the intended value. This is because:

• The Developers are accountable for creating a “Done” Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
• The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They must inspect the Increment at the end of each Sprint and assess how it delivers value and contributes to the Product Goal.
• The Product Owner and the Developers must collaborate closely throughout the Sprint to ensure that they have a shared understanding of what they are building and why. The Product Owner must provide clarifications, feedback, and guidance to the Developers as needed to help them create a valuable Increment.
• The amount of time that the Product Owner must spend with the Developers may vary depending on the context, complexity, and uncertainty of the product development. However, it should be enough so that both parties are confident that the Increment will meet the intended value.

Other options, such as 40%, as much time as the Developers tell them to be present, or 100%, are not valid answers as they imply a fixed or arbitrary amount of time that does not reflect the actual needs and dynamics of the product development.

References:

• [Scrum Guide], page 7, section “Developers”
• [Scrum Guide], page 6, section “Product Owner”
• [Scrum Guide], page 10, section “Definition of Done”
• [Scrum Guide], page 10, section “Increment”
• [Scrum Guide], page 10, section “Product Goal”