Question 1

Which activities will a Product Owner likely engage in during a Sprint? (choose the best three answers)

Accepted Answer

* 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

Question 2

A separate Product Backlog is needed for every: (choose the best answer)

Accepted Answer

According to the Professional Scrum Product Owner™ II certification guide1, a Product Backlog is an ordered list of what is needed to improve the product. It is the
single source of work undertaken by the Scrum Team. The Product Backlog is owned by the Product Owner, who is accountable for maximizing the value of the
product resulting from the work of the Scrum Team. Therefore, a separate Product Backlog is needed for every product, not for every Scrum Team, portfolio,
program, or all of the above. Multiple Scrum Teams can work on the same product and share the same Product Backlog2. A portfolio or a program may consist of
multiple products, each with its own Product Backlog3. References: 1: Professional Scrum Product Owner™ II Certification | Scrum.org 2: What is a Product
Backlog? | Scrum.org 3: Product Backlog Explained [+ Examples] | Atlassian

Question 3

Managing a Product Backlog involves which of the following activities? (choose all that apply)

Accepted Answer

Product Backlog involves the following activities12:
* Reducing or eliminating dependencies between Product Backlog items. This helps to increase the flexibility and adaptability of the Product Backlog, and enables
the Developers to select the most valuable and feasible items to work on in each Sprint3.
* Reviewing the Product Backlog with stakeholders. This helps to ensure that the Product Backlog reflects the needs and expectations of the customers and users,
and that the Product Owner receives feedback and input from various perspectives4.
* Breaking large Product Backlog items into multiple smaller Product Backlog items. This helps to create a more granular and transparent Product Backlog, and
allows the Product Owner to prioritize and refine the items more effectively5.
* Ordering the Product Backlog. This helps to communicate the relative importance and urgency of the Product Backlog items, and guides the Developers to select
the most valuable items for the next Sprint.
Forecasting the effort of Product Backlog items is not an activity that is explicitly required for managing a Product Backlog. The Product Owner is mainly
responsible for maximizing the value of the product, not the effort or cost of development. The effort of Product Backlog items may be estimated by the
Developers, but
this is not a mandatory practice and it does not affect the ordering of the Product Backlog. References
: 1: Product Backlog Management, 2: Managing Products with Agility, 3: Reducing Dependencies, 4: Reviewi the Product Backlog, 5: Breaking Down Product
Backlog Items, : Ordering the Product Backlog, : The Produc Owner, : Estimating Product Backlog Items

Question 4

Complete this sentence: The more uncertain you are about customer needs or market desires (choose the best two answers)

Accepted Answer

Verified

Question 5

Your stakeholders are very demanding and each of them has at least one feature that they say is essential for the next release. As the Product Owner, you have
validated that the feature
requests are all valid requests and would likely add value to your product. What should you do? (choose the best answer)

Accepted Answer

* Focus on Value: Scrum emphasizes delivering increments of value early and often. Each release should focus on a clear outcome for users, even if it doesn't
encompass every desired feature.
* Iterative Approach: Releasing a smaller, focused increment lets you gather feedback, course-correct, and add features incrementally based on what provides the
most value.
* Stakeholder Management: Involve stakeholders in the prioritization process, explaining the rationale behind focusing on a specific outcome to gather input and
secure buy-in.

Question 6

Which of the following are characteristics of a Product Goal? (choose all that apply)

Accepted Answer

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. References :
* 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

Question 7

If a Scrum Team uses Product Backlog refinement, when should it occur? (choose the best two answers)

Accepted Answer

Product Backlog refinement is an ongoing activity that can occur at any time during a Sprint, as needed. The Product Owner and Developers collaborate on this
task, ideally in advance of the upcoming Sprint to ensure clarity and readiness of the work ©. If refinement has not been done in preceding Sprints, it should be
done in the current Sprint to maintain the flow of valuable work (E). This approach is consistent with the Scrum principle of continuous improvement and the
iterative, incremental nature of Scrum12.

Question 8

What are the attributes of a good Product Vision and Strategy? (choose all that apply)

Accepted Answer

A good Product Vision and Strategy should have the following attributes12:
* It describes who will use the product and what they would like to achieve. This helps to define the target market, the customer segments, and the user personas,
as well as their needs, goals, and problems.
* It describes how people will use the product to achieve potential outcomes. This helps to articulate the value proposition, the benefits, and the features of the
product, as well as the assumptions and hypotheses that need to be validated.
* It describes what value means in the context of the product, and how it can be measured. This helps to establish the objectives, the key results, and the metrics
that will guide the product development and evaluation.
It is not necessary for a good Product Vision and Strategy to describe how the product compares to competitor products. This may be part of the market analysis
or the competitive advantage, but it is not a core attribute of the Product Vision and Strategy. Moreover, focusing too much on the competitors may distract from
the customer needs and the product value. References: 1: Product Vision, 2: Product Strategy

Question 9

Which of the following might the Scrum Team discuss during a Sprint Retrospective? (choose the best answer)

Accepted Answer

According to the Scrum Guide, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the
last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done1. Therefore, all of the options A, B, C, and D are possible
topics that the Scrum Team might discuss during a Sprint Retrospective, as they relate to the aspects that the team can improve or adapt. For example, the team
might discuss how to communicate better, how to plan the Sprint more effectively, how to acquire new skills or knowledge, or how to update their Definition of
Done23. The Sprint Retrospective is a formal opportunity for the team to focus on inspection and adaptation, and to identify the most helpful changes to implement
in the next Sprint1.

Question 10

When should the Product Owner update the project plan? (choose the best answer)

Accepted Answer

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