PSPO-I Practice Questions

• A product’s success is measured by the impact it has on the customers, the business, and the market. Different products may have different success criteria and metrics, depending on their vision, goals, value proposition, and target audience. However, some of the common and important aspects that can indicate a product’s success are:
• The other options are not valid or relevant measures of a product’s success. They are either too subjective, narrow, or unrelated to the product’s value proposition and goals. They are:

References:

• Product Success: https://www.productplan.com/glossary/product-success/
• Customer Satisfaction: https://www.agilealliance.org/glossary/customer-satisfaction/
• Cost: https://www.investopedia.com/terms/c/cost.asp
• Revenue: https://www.investopedia.com/terms/r/revenue.asp

 These are the best answers because they ensure that security concerns are addressed in a transparent and consistent way. By adding security criteria to the Definition of Done, the Scrum Team can make sure that every Increment meets a high standard of quality and security. By creating Product Backlog items for specific security concerns, the Scrum Team can prioritize and plan them in collaboration with the Product Owner and stakeholders. References:

• Scrum Guide, page 14: “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, page 15: “The Product Backlog is an emergent, ordered list of what is needed to improve the product.”

According to the Scrum Guide1, the Developers are responsible for selecting the amount of work they can do in a Sprint, based on their capacity and past performance2. If they realize that the workload may be greater than their capacity, they can either remove or change some of the selected Product Backlog items, or they can start the Sprint and monitor the progress, making adjustments as needed3. Recruiting additional Developers, canceling the Sprint, or working overtime are not valid actions, as they would disrupt the Scrum values of commitment, focus, and respect

The Daily Scrum is a 15-minute event for the Developers to synchronize activities and create a plan for the next 24 hours. This meeting is designed to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary. The intended outcomes are to identify any impediments that may prevent the Developers from achieving the Sprint Goal (D) and to foster a shared understanding among the Developers of what work is most important to undertake next in order to make the best possible progress toward the Sprint Goal (E). It is not a status update meeting for the Scrum Master or upper management, nor is it primarily about updating Scrum boards for stakeholder transparency.

References: The Scrum Guide and the resources provided by Scrum.org on the Daily Scrum emphasize these outcomes as essential to the effectiveness of the Daily Scrum event12.

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.