Scrum Updated PSPO-II Exam Questions and Answers by kiera

Option B is the best answer because it reflects the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is a living artifact that represents the current understanding of what the product needs to be most valuable for the customers and the stakeholders1. The Product Backlog is not a fixed or static document, but rather an emergent and dynamic one that adapts to the changing environment, needs, and feedback. The Product Owner is accountable for managing the Product Backlog and ensuring that it is transparent, ordered, and refined2. The Product Owner collaborates with the Scrum Team and the stakeholders to inspect and adapt the Product Backlog items based on the new insights, opportunities, and learnings that arise from the changing environment34. The Product Owner also uses various techniques, such as product vision, value proposition, user stories, experiments, and evidence-based management, to define, validate, and prioritize the Product Backlog items5 .

Option A is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a requirements specification document, but rather a list of hypotheses and assumptions that need to be tested and validated in the real world5. The Product Backlog items are not detailed or fixed upfront, but rather refined and clarified as they get closer to implementation2. Updating the requirements specification document to ensure stability implies a plan-driven and predictive approach that does not embrace change and feedback, and that does not optimize value delivery.

Option C is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a project plan, but rather a product roadmap that guides the development of the product. The Product Backlog does not have a predefined end date or scope, but rather evolves and changes as the product grows and matures1. Keeping the Product Backlog the same until the end of the project implies a plan-driven and predictive approach that does not embrace change and feedback, and that does not optimize value delivery.

Option D is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a disposable artifact, but rather a cumulative and iterative one that builds on the previous work and learnings1. The Product Backlog items are not discarded or replaced, but rather refined and updated as the product evolves and changes2. Archiving the Product Backlog and creating a new one implies a disruptive and wasteful approach that does not leverage the existing knowledge and feedback, and that does not optimize value delivery.

References:

1: Product Backlog

2: Product Backlog Management

3: Empiricism

4: Stakeholders & Customers

5: Product Vision

: Product Value

: Evidence-Based Management

: [Agile Manifesto]

: [Product Roadmap]

: Product Owner Accountabilities

: Sprint Review

: Product Backlog Refinement

: [User Stories]

: [Value Proposition]

: [Experiments]

The Sprint Goal is a summary statement of the Sprint objective, which ideally has a cohesive theme. The Sprint Goal also gives the Scrum Team guidance and flexibility on how to achieve the objective. The Sprint Goal is crafted by the entire Scrum Team during the Sprint Planning, based on the Product Owner’s proposal of the most valuable Product Backlog items and the Development Team’s forecast of the work that can be done in the Sprint. The Product Owner collaborates with the team to write the Sprint Goal and defines it on the basis of the value being sought. The Product Owner does not define the scope or the solution for the Sprint, but rather the outcome and the benefit. The Product Owner also does not work with stakeholders to set the Sprint Goal, but rather represents their interests and needs. The Product Owner has a role in crafting the Sprint Goal, but not the sole responsibility for it. References:

Professional Scrum Product Owner II Assessment

Understanding and Applying the Scrum Framework

Managing Products with Agility

The Role of the Product Owner during the Sprint

Sprint Goal – An Essential Ingredient in Scrum Recipe

As a Product Owner, you are accountable for maximizing the value of the product and the work of the Scrum Team. To do this, you need to collaborate with various stakeholders, user communities and other Product Owners to understand their needs, expectations and feedback, and to align them with the product vision and strategy. You also need to work with the Developers on Product Backlog refinement, which is an ongoing activity to add detail, estimates and order to Product Backlog items. This helps the Developers to understand what is valuable and feasible to deliver in the upcoming Sprints, and to plan and execute their work accordingly. These are typical and essential work for a Product Owner in a Sprint.

The other options are not typical or effective work for a Product Owner in a Sprint. Attending every Daily Scrum is not necessary, as the Daily Scrum is an event for the Developers to inspect their progress and plan their next steps. The Product Owner can attend the Daily Scrum if invited by the Developers, but should not interfere or answer questions that are not related to the Sprint Goal or the Product Backlog. Creating financial reporting upon the spent hours reported by the Developers is not a valuable activity, as it does not reflect the outcome or the value delivered by the product. It also goes against the Scrum values of trust and respect, as it implies that the Developers are not self-managing or committed to their work. Updating the work plan for the Developers on a daily basis is also not a good practice, as it undermines the autonomy and creativity of the Developers, and reduces their ability to inspect and adapt their work based on the empirical evidence. The Product Owner should not tell the Developers how to do their work, but rather focus on what is the most valuable outcome for the product.

References:

Professional Scrum Product Owner™ II Certification

Understanding and Applying the Scrum Framework

Managing Products with Agility

A. Reorder items in the Product Backlog: The Product Owner is responsible for ordering the Product Backlog to maximize value12.

B. Answer questions from the Developers about items in the current Sprint: The Product Owner is engaged throughout the sprint, answering questions on how things are supposed to function & look4.

E. Gather information and opinions from stakeholders: Gathering information and opinions from stakeholders is a key activity for the Product Owner, as it helps in understanding the value and ordering the Product Backlog