Scrum Professional Scrum Product Owner II Exam Practice Test

Answer : A, B

= As a Product Owner, you are accountable for maximizing the value of the product and the work of the Developers. To do this, you need to collaborate with the Developers and the Scrum Master to ensure that the Product Backlog is clear, ordered, and refined, and that the Sprint Goal and the Sprint Backlog are aligned with the product vision and strategy. You also need to provide feedback and guidance to the Developers throughout the Sprint, and to inspect and adapt the product based on the Sprint Review and the stakeholders' input.

One of the challenges that the Developers may face is to forecast the amount of work that they can complete within a Sprint, and to deliver a potentially releasable Increment that meets the Definition of Done. This requires the Developers to have the skills and the tools to estimate the complexity and the effort of the Product Backlog items, to plan and manage their work effectively, and to adhere to the quality standards and the technical practices that enable them to build a valuable and usable product increment.

To help the Developers improve their ability to deliver a done Increment, the Product Owner can take the following steps:

Ask the Scrum Master to help the Developers learn techniques for improving their ability to forecast work. The Scrum Master is accountable for establishing an environment where the Developers can work effectively, and for coaching the Developers on self-organizing and cross-functionality. The Scrum Master can also help the Developers to apply empirical process control, to use various estimation methods, to monitor and visualize their progress, and to inspect and adapt their plan based on the Sprint Backlog and the Sprint Burndown Chart.

The Product Owner can spend more time with the Developers. The Product Owner can support the Developers by clarifying the Product Backlog items, providing the acceptance criteria, explaining the customer needs and the business value, and answering any questions that the Developers may have. The Product Owner can also participate in the Sprint Planning, the Daily Scrum, and the Sprint Retrospective, to share their insights, expectations, and feedback, and to collaborate with the Developers on creating and refining the Sprint Goal and the Sprint Backlog.

The other options are not the best steps to take, because they either do not address the root cause of the problem, or they may have negative consequences. Ensuring that all Developers are top performers may not be realistic or feasible, and it may also create a culture of blame or competition, rather than collaboration and learning. Adding more people to the team may not necessarily increase the productivity or the quality of the work, and it may also introduce communication and coordination challenges, as well as additional costs and risks.Reference:=Scrum Guide,Understanding and Applying the Scrum Framework,Managing Products with Agility

Answer : A

A burndown chart is a graphical tool that shows the amount of work remaining versus time. It is often used to track the progress of a Sprint or a release. The work remaining is usually measured in terms of effort, such as hours or story points, and it is plotted on the vertical axis. The time is measured in terms of days or weeks, and it is plotted on the horizontal axis. The burndown chart starts with the total amount of work at the beginning of the Sprint or release, and it ideally ends with zero work at the end.The slope of the burndown chart indicates the rate of progress, or the velocity, of the Scrum Team12.

The other options are not what burndown charts track. Accumulated cost, accumulated business value, and individual worker productivity are not relevant or useful metrics for Scrum Teams, as they do not reflect the value or the quality of the product.Scrum Teams focus on delivering potentially releasable increments of the product that meet the Definition of Done, and they use empirical feedback to inspect and adapt their work13.Reference:1:Understanding and Applying the Scrum Framework2:Burndown Chart3:Managing Products with Agility

Answer : B, C, D

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.Reference:1: Product Vision,2: Product Strategy

Answer : E

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.Reference:

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

Answer : C

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.Reference:

Professional Scrum Product Owner II Assessment

Understanding and Applying the Scrum Framework

Managing Products with Agility

What is a Product Backlog?

Product Backlog Explained

Answer : A

Option A is the best answer because it reflects the agile and empirical nature of Scrum and Product Ownership.The Product Vision is a concise and inspiring statement that describes the purpose, direction, and value proposition of the product1. The Product Vision 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 creating and communicating the Product Vision to the Scrum Team and the stakeholders2.The Product Owner collaborates with the Scrum Team and the stakeholders to inspect and adapt the Product Vision based on the new insights, opportunities, and learnings that arise from the changing environment34.The Product Owner also uses various techniques, such as product discovery, user research, market analysis, and experiments, to validate and refine the Product Vision5.

Option B is not the best answer because it contradicts the accountability of the Product Owner. The Product Owner is the sole person responsible for managing the Product Backlog and maximizing the value of the product and the work of the Scrum Team.The Product Owner is also the sole person responsible for creating and communicating the Product Vision to the Scrum Team and the stakeholders2. The Product Owner may seek input and feedback from the Scrum Team and the stakeholders, but the final decision and authority on the Product Vision belongs to the Product Owner. The Scrum Team and the stakeholders are not accountable for developing and evolving the Product Vision, but they are expected to understand and support it .

Option C is not the best answer because it contradicts the reality and complexity of product development.The Product Vision is not a technical specification, but rather a strategic and business-oriented statement that guides the development of the product1. The Product Vision does not prescribe how the product should be built, but rather why and what the product should achieve. However, the Product Vision is not completely detached from the technical aspects of the product, as the technology choices may have an impact on the feasibility, desirability, and viability of the product. The Product Owner should be aware of the strategic technology choices and their implications, and discuss them with the Development Team and the stakeholders, as part of the product discovery and validation process .

1:Product Vision

2:Product Owner Accountabilities

3:Empiricism

4:Stakeholders & Customers

5:Product Discovery

:Product Backlog Management

:The Scrum Guide

:Scrum Team

:Product Value

:Product Feasibility

:Product Validation

: [Agile Manifesto]

: [User Research]

: [Market Analysis]

: [Experiments]

Answer : D

A ''cone of uncertainty'' is a graphical representation of the evolution of the amount of uncertainty during a project. It shows that at the beginning of a project, there is a high degree of variability and unpredictability in the estimates of the scope, cost, time, and value of the product. As the project progresses, more information and feedback are gathered, and the uncertainty decreases, reaching zero when the product is delivered and validated. A ''cone of uncertainty'' can be used to visualize the uncertainty of the potential value that a Scrum Team delivers over time, and to guide the empirical process of inspection and adaptation. By using a ''cone of uncertainty'', a Scrum Team can:

Align the expectations of the stakeholders and customers with the reality of the complex and dynamic environment.

Avoid making premature or unrealistic commitments based on inaccurate or incomplete estimates.

Embrace change and experimentation as opportunities to learn and deliver more value.

Inspect the actual value delivered and the feedback received, and adapt the product vision, strategy, and backlog accordingly.

Forecast the range of possible outcomes and the level of confidence for each Sprint and release.

The other options are not valid uses of a ''cone of uncertainty''. A ''cone of uncertainty'' does not represent the relative level of difficulty for predicting the velocity of individual team members, as velocity is a measure of the amount of work done by the whole Scrum Team, not by individuals. A ''cone of uncertainty'' does not rapidly identify and prioritize all uncertainties, as uncertainties are not always known or quantifiable, and may change over time. A ''cone of uncertainty'' does not determine whether to cut quality, similar to the ''Iron Triangle'' of project management, as quality is not a variable that can be traded off in Scrum, but a non-negotiable aspect of the Definition of Done and the value proposition of the product.

Professional Scrum Product Owner II Certification

Managing Products with Agility

Cone of Uncertainty - Wikipedia