Domain 5 of 5

Working with the Product Backlog

The relationship between outcome and output, terms from product economics, value seen from several stakeholder groups, techniques for measuring value, and building a product backlog that supports the achievement of a Product Goal.

Concepts

~20%

Of the exam

Practice questions

Concepts in this domain

01Outcome and outputOutput is what the team produced. Outcome is what changed for someone because of it. A product owner is accountable for the second and is usually measured on the first.02Product economicsThe vocabulary a product owner needs to argue about value in the terms the business already uses. Cost of delay, sunk cost, opportunity cost, total cost of ownership and lifetime value.03Measuring valueValue is established by evidence rather than assertion, and the Increment is what makes it inspectable.04Ordering the Product BacklogOrder expresses strategy, not preference, and being accountable for it is not the same as doing it yourself.05Product Backlog refinementThe ongoing activity of breaking down and further defining Product Backlog items into smaller, more precise items. It is not an event.

Try a question from this domain

A team reports that it delivered forty-two items last quarter, up from thirty-one. The product owner is asked whether the product improved. What is the accurate way to describe the relationship between these numbers and the answer?

AForty-two items is output. Whether anything improved depends on what changed for users and for the organisation, and output and outcome are not proportional.
BMore items delivered means more value, so the product improved.
CThe comparison is invalid because item sizes differ between quarters.
DThe product improved if the items met the Definition of Done.

15 questions on this domain.

One per page, with a worked explanation.

Start the set

Not affiliated with or endorsed by Scrum Alliance.