Scrum Updated PSPO-II Exam Questions and Answers by roisin

A. To influence the Total Cost of Ownership of the product: Adhering to the Definition of Done ensures that the product meets the required quality standards, which can influence the Total Cost of Ownership1.

B. To have transparency into what has been done at the end of each Sprint: The Definition of Done provides a shared understanding of what work was completed and what standards were met as part of the Increment2. This creates transparency and allows the Product Owner to understand what has been accomplished at the end of each Sprint12.

Personas are fictional characters that represent the different user types that might use your product or service in a similar way1. Personas can help you to2345:

Understand the needs of a set of users by creating empathy and insight into their goals, behaviors, and pain points.

Formulate hypotheses about product value by identifying the problems and opportunities that your product can address for each user type.

Understand market potential by estimating the size and characteristics of each user segment and their willingness to pay for your product.

Discover key buying triggers by exploring the motivations, influences, and decision-making processes of each user type.

Design and test your product features and user experience by using personas as a guide and a reference point. References:

1: Personas – A Simple Introduction

2: The Complete Guide to User Personas and How They Can Help Your Marketing Strategy (With Examples)

3: Personas | Usability.gov

4: The importance of personas for digital experience

5: Personas | Definition and Overview

 In Scrum, there is no separate artifact called a project plan. The Product Backlog is the plan for the product development, and it contains all the features, requirements, enhancements, and fixes that are needed to deliver a valuable product. The Product Backlog is not a static or fixed document, but rather an emergent and dynamic one. It is constantly updated and refined by the Product Owner and the Developers as they learn more about the product, the users, the market, and the technology. The Product Backlog is updated whenever new information and insights emerge, which can happen at any time during the product development process. Therefore, option C is the best answer.

Option A is not correct because the Daily Scrum is not a status meeting, but rather a time-boxed event for the Developers to inspect their progress towards the Sprint Goal and adapt their Sprint Backlog accordingly. The Product Owner does not need to update the Product Backlog after the Daily Scrum, unless there is a significant change in the product vision, strategy, or value proposition that affects the Product Backlog items.

Option B is not correct because the Sprint Retrospective is not a time to update the Product Backlog, but rather a time-boxed event for the Scrum Team to inspect their way of working and identify potential improvements. The Product Owner does not need to update the Product Backlog before the Sprint Retrospective, unless there is a need to communicate a change in the Product Goal or the product roadmap that affects the Product Backlog items.

Option D is not correct because the Sprint Planning is not a time to know how much work will have to be done in the Sprint, but rather a time-boxed event for the Scrum Team to collaborate on selecting and planning the Product Backlog items that will deliver the Sprint Goal. The Product Owner does not need to update the Product Backlog before the Sprint Planning, unless there is a need to reorder or clarify the Product Backlog items that are the most valuable and relevant for the upcoming Sprint. References:

Professional Scrum Product Owner II Assessment

Understanding and Applying the Scrum Framework

Managing Products with Agility

What is a Product Backlog?

Product Backlog Explained

A. Increase transparency: The Definition of Done (DoD) creates transparency by providing everyone a shared understanding of what work was completed and what standards were met as part of the Increment1.

C. Create a shared understanding of when work is complete: The DoD is a shared understanding among the team members of when a product increment is ready for release2.

D. Describe the work that must be done before the Sprint can be declared complete: The DoD includes all of the characteristics and standards an Increment needs to meet in order to be released1. Once the Definition of Done is met, the Increment is Done and can be delivered1.