Question 11 - Select the true statements

  • The Product Backlog exists as long as the product exists
  • The Product Backlog increases transparency
  • The Product Backlog only contains the functional requirements of the product

Overall explanation

  • The Product Backlog can contain initiatives, functional and non-functional needs, enhancements, ideas or any other product needs.

Question 12 - How is the Product Backlog ordered?

  • The least risky items are at the top and the riskiest items at the bottom.

  • Whatever seems the best to the Product Owner.

  • Items are ordered by function (ie design, frontend, backend, database).

  • Highest priority items at the bottom and lowest priority items at the top.

  • Items with the fewest Story Points are at the top and the most at the bottom.

Overall explanation

  • For the Product Owner to succeed, the entire organization must respect his or her decisions.
  • The Product Owner’s decisions are visible in the content and ordering of the Product Backlog.
  • No one can force the Development Team to work from a different set of requirements.

Question 13 - It is good practice to maintain separate Product Backlogs for multiple Scrum Teams that work on one product

  • False
  • True

Overall explanation

  • Multiple Scrum Teams often work together on the same product.
  • One Product Backlog is used to describe the upcoming work on the product.
  • A Product Backlog attribute that groups items may then be employed.

Question 15 - All of the items on the Product Backlog must be written by the Product Owner before they are handed over to the Development Team.

  • False

  • True

Overall explanation

  • The Product Owner is responsible for the Product Backlog.
  • Who adds the items and how they are added to the Product Backlog vary widely across organizations, Scrum Teams, and individuals.
  • “Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion.”

Question 20 - All work to be done by the Development Team must come from the Product Backlog.

  • True

  • False

Overall explanation

  • All work to be done by the Development Team must ultimately come from the Product Backlog as it is the single source of product requirement.
  • How the work is done can change, evolve, and emerge as more is learned.

Question 29 - The Scrum Master observes the Product Owner struggling with ordering the Product backlog. What is an appropriate action for the Scrum Master to take?

  • Present the Product Owner with an ordered Product Backlog to use

  • Offer the Product Owner help in understanding that the goal of ordering the Product Backlog is to maximize value.

  • Suggest the Product Owner extend the Sprint, so he can have more time to order the Product backlog.

  • Encourage the Product Owner to work with the Development Team to see which items technically are fastest to implement

  • Suggest that the Development Team does the ordering to be sure that it is a feasible ordering of work

Overall explanation

  • The Scrum Master serves the Product Owner in several ways, including:

  • Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible;

  • Finding techniques for effective Product Backlog management;

  • Helping the Scrum Team understand the need for clear and concise Product Backlog items;

  • Understanding product planning in an empirical environment;

  • Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;

  • Understanding and practicing agility; and,

  • Facilitating Scrum events as requested or needed.

Question 38 - Which statement regarding the Product Backlog is FALSE?

  • It is a finalized list of requirements to be done for the Product.

  • Ordered based on value, priority, risk, and dependencies.

  • It is managed by the Product Owner.

  • It is an inventory of work to be done for the Product.

Overall explanation

  • The Product Backlog is a living artifact that evolves and changes as more is learned.

Question 39 - What should a Product Owner take in consideration when ordering the Product Backlog? (choose the best answer)

  • The newest items are added towards the bottom.

  • The highest priority items are always at the top.

  • The availability of the technical lead.

  • Whatever is the most appropriate to achieve the product's goals and to optimize the value delivered to the users.

  • How much time the Development Team is allocated to the project.

  • The items with the highest ROI are always at the top.

Overall explanation

  • While the Product Backlog must be ordered, ordering by priority is only one many techniques.
  • The Product Backlog indeed must be ordered: its ordering determines the Product Backlog items' (PBI) order of delivery.
  • The Development Team can discuss PBI ordering with the Product Owner but, in the end, the Development Team must take PBIs in Product Backlog order.
  • However, the Product Backlog is not guaranteed to represent an ordering of PBIs by either value or priority.
  • You can’t just assign priorities to PBIs — whether they come from ROI or importance to the business or anywhere else — and then prioritize the backlog on the basis of those relative values.
  • As a Product Owner, you must consider the entire backlog of PBIs together.
  • How this is done may vary widely across organizations, Scrum Teams, and individuals.

Question 43 - While Product Backlog Items can be re-estimated, reordered, modified, they can never be removed from the Product Backlog

  • False

  • True

Overall explanation

  • A Product Backlog Item can be removed if it turns out to be irrelevant or obsolete.
  • The Product Owner only focuses on value.

Question 73: How should multiple Scrum Teams, working from the same Product Backlog, select the Product Backlog items their teams plan to work on?

  • The Product Owner will present the work and the Development Teams will select the items they will work on.

  • The Product Owner creates separate Product Backlogs for each Development Team.

  • Each Scrum Team would select an equal number of items.

  • The Product Owner assigns the work to each team.

  • The Scrum Team with the highest productivity will select the items first.

Overall explanation

  • There is only one Product Backlog
  • The ones doing the work are the best ones to decide what they can do and how to do it.

Question 74: Which statement is true about the Product Backlog?

  • It is a living artifact that evolves as the product and the environment in which it will be used evolves.

  • It supplements the requirements document.

  • It is a complete project plan that the Scrum Team commits to completing.

  • It should not have more than 6 months of work.

Overall explanation

  • Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog.

Question 76 - What impact does an evolving environment have on the Product Backlog?

  • Identify a different market for the current Product Backlog.

  • A new Product Backlog is created to meet the needs of the users.

  • The Product Backlog is static as it is a commitment to the stakeholders.

  • The Product Backlog is a living artifact that evolves as the product and the environment in which it will be used evolves.

Overall explanation

  • The Product Backlog is a living artifact that evolves and changes as more is learned.

Question 78 : Multiple teams working on the same product should maintain separate Product Backlogs.

  • True
  • False

Overall explanation

  • For a single product there is one Product Backlog.
  • For a single Product Backlog there is one Product Owner.

Question 103 - The frequency of updating the product backlog is

  • At every Sprint beginning

  • Daily

  • Weekly

  • Anytime

Overall explanation

  • Requirements never stop changing, so a Product Backlog is a living artifact.
  • Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog.

1. Who has the final say on the order of the Product Backlog?

  • The Product Owner

  • The Development Team

  • The CEO

  • The Scrum Master

  • The stakeholders

Overall explanation

  • The Product Backlog is an ordered list of everything that is known to be needed in the product.
  • It is the single source of requirements for any changes to be made to the product.
  • The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.