Free Scrum PSPO II Exam Questions (page: 2)

The most important thing a Product Owner can do is: (choose the best answer)

  1. Determine the release schedule and contents.
  2. Ensure that all stakeholder needs are met.
  3. Function as the single source of truth for all requirements.
  4. Maximize the value delivered by the product.

Answer(s): D

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 is responsible for defining, ordering, and validating what the Scrum Team works on, and ensuring that the product delivers value to the customers, users, and the organization. The other options are not the most important thing a Product Owner can do, because they are either too narrow (A), too unrealistic (B), or too prescriptive ©.


Reference:

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



You are a Product Owner for a product that publishes customer usage rates by feature.

An influential stakeholder does not believe the data showing the usage rates, and insists that a particular feature is essential, despite data showing low usage rates. The stakeholder believes that measuring feature usage is a waste of time.

As Product Owner you have confirmed that the data is accurate and believe that the data is valuable to help you and your team.
What should you do?

(choose the best answer)

  1. Continue measuring feature usage and use it to inform your decisions, but do not publish it.
  2. Continue to measure and publish the data, to provide openness and transparency, and use it to inform your decisions.
  3. Stop measuring feature usage to appease the stakeholder.

Answer(s): B

Explanation:

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 have a clear understanding of the product vision, the product value, and the product backlog management. Measuring feature usage is one way to gather empirical evidence of the value delivered by the product and the feedback from the customers and users. This data can help you validate or invalidate your assumptions, prioritize the product backlog items, and inspect and adapt the product strategy. Therefore, measuring feature usage is not a waste of time, but a valuable practice for agile product management.

Moreover, as a Product Owner, you are also responsible for engaging with the stakeholders and customers, and providing them with transparency and openness. This means that you should share the data and the insights you gain from it with them, and invite them to collaborate with you and the Scrum Team. This can help you build trust and alignment, and foster a culture of experimentation and learning. Therefore, you should not hide the data or stop measuring it, but rather use it as a basis for constructive dialogue and decision making.


Reference:

Professional Scrum Product OwnerTM II Certification

Managing Products with Agility

Evidence-Based Management



A separate Product Backlog is needed for every:

(choose the best answer)

  1. Product.
  2. Scrum Team.
  3. Portfolio.
  4. Program.
  5. All of the above.

Answer(s): A

Explanation:

According to the Professional Scrum Product OwnerTM 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 Backlog. A portfolio or a program may consist of multiple products, each with its own Product Backlog.


Reference:

1: Professional Scrum Product OwnerTM II Certification | Scrum.org 2: What is a Product Backlog? | Scrum.org 3: Product Backlog Explained [+ Examples] | Atlassian



What is the role of the Product Owner in crafting the Sprint Goal?

(choose the best answer)

  1. The Product Owner defines the scope for a Sprint and therefore also the Sprint Goal.
  2. The Product Owner must work with stakeholders to set each Sprint's Goal.
  3. The Product Owner collaborates as a member of the Scrum Team to define a Sprint Goal.
  4. The Product Owner has no role in it. This is the Developers responsibility.
  5. The Product Owner should come to the Sprint Planning with a clearly defined Sprint Goal.

Answer(s): C

Explanation:

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.


Reference:

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



The leading revenue-producing product in your portfolio has:

. High Current Value

. Low Unrealized Value

The product has been losing customers for several years and revenues are down. Using those two data points and the options below, what is the first action you should take?

(choose the best answer)

  1. Increase investment in the product to create greater interest and bring old customers back.
  2. Maintain the product, but begin reducing investment; seek other opportunities for future growth.
  3. Drop the price for the product to attract new customers.
  4. Increase marketing for the product.

Answer(s): B

Explanation:

According to the PSPO II resources, a product with high current value and low unrealized value is in the harvest stage of the product lifecycle. This means that the product has reached its peak and is facing increasing competition and decreasing customer demand. The best strategy for this stage is to maintain the product quality and customer satisfaction, but reduce the investment in new features or enhancements. The product owner should seek other opportunities for future growth, such as developing new products or exploring new markets.


Reference:

1: Product Lifecycle Management

2: Product Strategy

3: Evidence-Based Management



How much of the Sprint Backlog must be defined during Sprint Planning?

(choose the best answer)

  1. Enough so the Developers can create a forecast of what they can do during the Sprint.
  2. All of the potential work. Sprint Planning is not over until 100% of the work is identified and estimated.
  3. Just enough to understand design and architectural implications.
  4. Just enough tasks for the Scrum Master to be confident in the Developer's understanding of the Sprint.

Answer(s): A

Explanation:

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Developers about what functionality will be in the next Increment and the work needed to deliver that functionality into a "Done" Increment. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Developers work through the plan and learn more about the work needed to achieve the Sprint Goal. The Sprint Backlog is not a commitment to deliver a fixed scope of work, but rather a forecast of what the Developers believe they can do in the Sprint. Therefore, the Sprint Backlog does not need to be fully defined during the Sprint Planning, but only enough so the Developers can create a realistic forecast of what they can do during the Sprint.


Reference:

1: Sprint Backlog, 2: The Scrum Guide, 3: Commitment vs. Forecast



When the Product Owner is too busy to work with all of the teams in a multi-team product development effort, which strategy will help them?

(choose the best answer)

  1. Add component team Product Owners.
  2. Communicate a clear Product Goal and delegate some activities to the Developers.
  3. Enlist the Program Management Office to help coordinate work.
  4. Assign sub-Product Owners to each Scrum Team.
  5. All of the above.

Answer(s): B

Explanation:

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are also accountable for effective Product Backlog management, which includes clearly expressing Product Backlog items, ordering them to best achieve goals and missions, ensuring that the Product Backlog is transparent, visible and understood. The Product Owner may do the above work or may delegate the responsibility to others. However, the Product Owner remains accountable.

When working with multiple Scrum Teams on the same product, the Product Owner should ensure that there is a shared understanding of the Product Goal among all the teams and stakeholders. The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next. The Product Owner should also collaborate with the Developers to create and refine Product Backlog items that are valuable, feasible, and testable. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog. The Product Owner should trust the Developers to self-organize and deliver the most valuable increments possible.

The other options are not recommended strategies for the Product Owner, as they may introduce unnecessary complexity, confusion, and waste. Adding component team Product Owners, enlisting the Program Management Office, or assigning sub-Product Owners may create silos, dependencies, and conflicts among the teams and stakeholders. These roles may also undermine the authority and accountability of the Product Owner, and reduce the transparency and alignment of the Product Backlog. The Product Owner should work with the Scrum Master and the Developers to find ways to optimize the value delivery and collaboration across the teams, rather than creating intermediaries or proxies.


Reference:

1: Scrum Guide 2: Understanding and Applying the Scrum Framework 3: Managing Products with Agility 4: Evolving the Agile Organization



Who is accountable for creating a plan for the Sprint and adhering to the Definition of Done?

(choose the best answer)

  1. The Scrum Team.
  2. The Product Owner.
  3. The Scrum Master.
  4. The Developers.
  5. All of the above.

Answer(s): D

Explanation:

According to the Scrum Guide, the Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint. They are accountable for creating a plan for the Sprint, the Sprint Backlog, and for adhering to the Definition of Done. The Product Owner and the Scrum Master are not accountable for these activities, but they may support the Developers as needed. The Scrum Team as a whole is accountable for delivering a valuable, useful, and potentially releasable Increment each Sprint, but the Developers have the specific accountability for planning and building it. Reference := Scrum Guide, Understanding and Applying the Scrum Framework, Managing Products with Agility






Post your Comments and Discuss Scrum PSPO II exam prep with other Community members:

PSPO II Exam Discussions & Posts