QUESTION: 25

The Developers inform the Product Owner during the Sprint that they are not likely to complete everything they forecasted.
What would you expect a Product Owner to do?
(choose the best answer)

Reduce the scope of the Sprint, if possible, to still meet the Sprint Goal.
Skip Product Backlog refinement activities.
End the Sprint, since the goal cannot be achieved.
Change the Sprint Goal to match what the Developers can deliver.
Inform management that more resources are needed.

Answer(s): A

Explanation:

According to the Professional Scrum Product OwnerTM II certification guide1, the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. This means that the Product Owner should collaborate with the Developers and the Scrum Master to find the best way to deliver value in the current Sprint, even if the initial forecast is not met. The Product Owner should not change or abandon the Sprint Goal, as it is a commitment made by the Scrum Team during Sprint Planning. The Product Owner should also not skip Product Backlog refinement activities, as they are essential for preparing the Product Backlog for future Sprints. The Product Owner should not end the Sprint prematurely, as it may cause more disruption and waste than delivering a potentially releasable Increment. The Product Owner should not inform management that more resources are needed, as it may imply that the Scrum Team is not self-organizing and cross-functional. The Product Owner should respect the Developers' autonomy and professionalism and support them in finding the best solution to the problem. Therefore, the best answer is to reduce the scope of the Sprint, if possible, to still meet the Sprint Goal. This means that the Product Owner and the Developers should negotiate the scope of the Sprint Backlog within the Sprint, removing or adding Product Backlog items that are aligned with the Sprint Goal and the value delivery.

Reference:

1: Professional Scrum Product OwnerTM II Certification | Scrum.org

Reveal Solution Next Question

QUESTION: 26

Which of the following is true about Scrum?

(choose all that apply)

Each component of Scrum serves a specific purpose and is essential to the successful usage of Scrum for building complex products.
Scrum is a framework for generating value through adaptive solutions for complex problems.
Scrum is a methodology, where you can "pick and choose" which parts of Scrum you think will work for your environment.
Scrum is based on empiricism.
Scrum is like traditional processes but with self-management to replace Project Managers.

Answer(s): A,B,D

Explanation:

Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. Scrum consists of three roles (Scrum Master, Product Owner and Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective), and three artifacts (Product Backlog, Sprint Backlog and Increment). Each component of Scrum serves a specific purpose and is essential to the successful usage of Scrum. Scrum is not a methodology, where you can "pick and choose" which parts of Scrum you think will work for your environment. Scrum is a whole, and each part of Scrum complements the others. Scrum is based on empiricism, which means that knowledge comes from experience and making decisions based on what is observed. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Scrum is not like traditional processes but with self-management to replace Project Managers. Scrum is a different way of working that requires a shift in mindset and culture. Scrum promotes self-organization, collaboration, transparency, inspection and adaptation.

Reference:

Professional Scrum Product OwnerTM II Certification
Understanding and Applying the Scrum Framework
[The Scrum Guide]

Reveal Solution Next Question

QUESTION: 27

The environment in which a product will be used changes and emerges continually.
What is the effect on the Product Backlog?
(choose the best answer)

The requirements specification document, describing the Product Backlog items, must be updated to ensure stability.
The Product Backlog evolves to reflect what the product needs to be most valuable.
There is no effect, the Product Backlog must stay the same until the end of the project.
The Product Backlog is archived and a new Product Backlog is created to take its place

Answer(s): B

Explanation:

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 stakeholders. 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 refined. 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 environment. 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 items.
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 world. The Product Backlog items are not detailed or fixed upfront, but rather refined and clarified as they get closer to implementation. 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 matures. 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 learnings. The Product Backlog items are not discarded or replaced, but rather refined and updated as the product evolves and changes. 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.

Reference:

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]

Reveal Solution Next Question

QUESTION: 28

Which of the following are characteristics of a Product Goal?

(choose all that apply)

It communicates the target future state of the product.
It enhances focus.
It is a commitment contained in the Product Backlog.
It has the approval of all stakeholders.
It provides a long-term objective for the Scrum Team to plan against.
It forms a contract with the business, allowing change to be better managed.

Answer(s): A,B,C,E

Explanation:

A Product Goal is a summary statement of the desired outcome or value that the product should deliver. It communicates the target future state of the product, which is aligned with the product vision and strategy. It enhances focus by providing a clear direction and purpose for the Scrum Team and the stakeholders. It is a commitment contained in the Product Backlog, which means that it is transparent, visible, and understood by everyone involved in the product development. It provides a long-term objective for the Scrum Team to plan against, which helps them to prioritize and refine the Product Backlog items and to craft the Sprint Goals.
Option D is not correct because the Product Goal does not need to have the approval of all stakeholders. The Product Owner is accountable for the value of the product and the Product Backlog, and therefore has the authority to define and communicate the Product Goal. The Product Owner may collaborate with the stakeholders to discover and validate their needs and expectations, but does not need to seek their consensus or permission for the Product Goal. Option F is not correct because the Product Goal is not a contract with the business, but rather a flexible and adaptable guide for the product development. The Product Goal is not fixed and immutable, but rather emergent and dynamic. It can be changed or updated as the product evolves and the market conditions change. The Product Goal does not limit or constrain the changes that may occur during the product development, but rather enables and supports them.

Reference:

Professional Scrum Product Owner II Assessment
Understanding and Applying the Scrum Framework
Managing Products with Agility
Scrum Guide 2020 Update - Introducing the Product Goal The Product Goal explained

Reveal Solution Next Question

Free PSPO-II Exam Braindumps (page: 7)

QUESTION: 25

Explanation:

Reference:

QUESTION: 26

Explanation:

Reference:

QUESTION: 27

Explanation:

Reference:

QUESTION: 28

Explanation:

Reference: