Sign in Subscribe

Domain 3 of 3

Managing Products with Agility

Product vision and the Product Goal, ordering and refining the Product Backlog, working with stakeholders, forecasting and measuring value.

14

Concepts

~40%

Of the exam

42

Practice questions

Concepts in this domain

01Product vision and what counts as a productA product is a vehicle to deliver value with a clear boundary, known stakeholders and well-defined users or customers.02The Product GoalThe single objective the Scrum Team plans against, and why a team holding three goals is holding none.03Product Backlog itemsWhat an entry on the Product Backlog is, what Scrum requires of it, and how much of what teams do to items comes from practices outside the framework.04Ordering the Product BacklogOrder expresses strategy, not preference, and being accountable for it is not the same as doing the work.05Product Backlog refinementThe ongoing activity of breaking down and further defining Product Backlog items into smaller, more precise items. It is not an event.06Estimating and sizingScrum asks that Product Backlog items carry a size, says who is responsible for it, and names no technique for arriving at one.07Forecasting and release planningScrum prescribes no forecasting technique. What it defines is that the Sprint Goal is the commitment, and that projections come from observation.08Burndown, burnup and cumulative flowThe three charts teams use to track progress, what each one shows that the others hide, and why Scrum names all three without requiring any of them.09Releasing an IncrementWhen a Done Increment can reach users, why the Sprint Review is not a gate, and what a rare batched release does to the feedback loop.10Stakeholders and collaborationHow stakeholders participate in Scrum, where their input enters, and where the Product Owner's decision stands.11Measuring valueValue is established by evidence rather than assertion, and the Increment is what makes it inspectable.12Evidence-Based ManagementScrum.org's framework for measuring value, built on four Key Value Areas and a goal structure that turns strategy into a sequence of experiments.13Technical debtThe accumulated cost of past choices that makes changing a product slower, and the Product Owner decision about when to pay it down.14Product Economics: Cost of Delay, Opportunity Cost, LTV and CACUse product economics to compare investments, calculate customer contribution and avoid misleading lifetime value or prioritisation claims.

Try a question from this domain

How does the Scrum Guide define a product?

AAnything sold to an external customer
BA vehicle to deliver value, with a clear boundary, known stakeholders and well defined users or customers
CThe output of one Scrum Team over a release cycle
DA software application with a published roadmap

42 questions on this domain.

One per page, with a worked explanation.