If 5 Scrum Teams are working on the same product, how many Product Owners are needed?

  • As decided by the self-organized Scrum Team

  • As decided by the management

  • Five Product Owners

  • One Product Owner

Overall explanation

  • There must be one Product Owner per product.
  • The Product Owner is one person, not a committee.

Question 16 - As a Product Owner, which of the following would be a valid point of focus? (choose the best two answers)

  • Frequently work with customers and stakeholders in identifying potential work that could deliver the most value.

  • Always being near the Scrum Team just in case they need Product Owner support.

  • Ensuring the project and release status is transparent to customers and stakeholders.

  • Creating User Stories.

Overall explanation

  • The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful.
  • The Product Owner works diligently to identify these needs.
  • The Product Owner is responsible for ensuring that the status of the project is visible, transparent, and clear to all.
  • At any point in time, the total work remaining to reach a goal can be summed and information is made transparent to all stakeholders.

Question 24 - The Product Owner must release each Increment to production?

  • To make sure the Development Team is done every Sprint
  • When it makes sense
  • Without exception
  • Whenever the product is free of defects

Question 28 - Choose the 2 true statements

  • Product users are the most important stakeholders

  • The main priority of the Product Owner is to maximize the value of the product

  • Development Team can’t act on directions from anyone other than Product Manager

  • Product Owner’s decisions are visible in the Sprint Backlog content

Question 45 - A Scrum Team has been working on a product for nine Sprints. A new Product Owner comes in, understanding he is accountable for the Product Backlog. However, he is unsure about his responsibilities. Which two activities are part of the Product Owner role according to Scrum ?

Choose 2 answers.

  • Creating detailed functional test cases

  • Interacting with stakeholders

  • Describing features as Use Cases

  • Ensuring that the most valuable functionality is produced at all times

  • Providing the Development Team with detailed technical specifications

Overall explanation

  • The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes:

    • Clearly expressing Product Backlog items;

    • Ordering the items in the Product Backlog to best achieve goals and missions;

    • Optimizing the value of the work the Development Team performs;

    • Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,

    • Ensuring the Development Team understands items in the Product Backlog to the level needed.

  • The Product Owner role is to tell the Development Team what to do, not how to do it. Hence, he or she must come up with functional inquiries, not technical one.

Question 60 - What areas of focus can help a Product Owner make sure that the product is delivering value? (choose the best three answers)

  • How much can the customer absorb and use the product.

  • The size or quantity of the User Stories delivered.

  • Direct customer feedback.

  • The level of accuracy between the done Increment and the original requirements.

  • How much of the functionality of his product is being utilized.

Overall explanation

  • Customer Satisfaction, Customer Usage Index, and Customer or user satisfaction gap are Key Value Measures defined in the Evidence-Based Management (EBM) approach. It is an empirical approach that provides organizations with the ability to measure the value they deliver to customers.

Question 75 Which of the following statements is not correct?

  • Only the Development Team can finalize the estimate of the Product Backlog Items

  • The Product Owner only orders the Product Backlog Items on their value

  • Multiple Development Teams working for the same product should have only one common Product Backlog

  • The Development Team can write a Product Backlog item at the Product Owner’s discretion

Overall explanation

  • Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog. Also the dependencies between Product Backlog items may be taken into consideration.

Question 89 - The Product Owner may consider the dependencies of the software tools the Development Team uses when ordering the Product Backlog

  • True
  • False

Overall explanation

  • The Product Owner may consider the dependencies between Product Backlog Items but not the dependencies of the software tools used by the Development Team.

Question 105 - The number one priority of the Product Owner is

  • Maximizing the value of Development Team’s work

  • Testing the Development Team’s work against detailed requirements

  • Managing the development work

  • Guarding the Development Team from any interruption

Overall explanation

  • The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes:

    • Clearly expressing Product Backlog items;

    • Ordering the items in the Product Backlog to best achieve goals and missions;

    • Optimizing the value of the work the Development Team performs;

    • Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,

    • Ensuring the Development Team understands items in the Product Backlog to the level needed.

Question 106 - What impact does technical debt have on the Product Owner? (choose the best two answers)

  • More time and money is spent maintaining the product when you have technical debt.

  • Technical debt can reduce the velocity in which new functionality can be created.

  • Technical debt has no impact on the delivery of value.

  • Technical debt is only a concern of the Development Team as the Product Owner should not be distracted by technical aspects.

Overall explanation

  • Technical debt is a concept in programming that reflects the extra development and testing work that arises when 'quick and dirty' solutions result in later remediation.
  • It creates an undesirable impact on the delivery of value and an avoidable increase in waste and risk.