Domain 4 of 5
Product Backlog Management and Forecasting Ordering by value when several stakeholders have asked for different things, refining a Product Backlog item only as far as the Scrum Team needs and forecasting in a way that stays honest about what is unknown.
Concepts in this domain
01 The Product Backlog An emergent, ordered list of what is needed to improve the product, and the single source of work undertaken by the Scrum Team. 02 Ordering the Product Backlog Order expresses strategy, not preference, and being accountable for it is not the same as doing the work. 03 Product Backlog refinement The ongoing activity of breaking down and further defining Product Backlog items into smaller, more precise items. It is not an event. 04 Forecasting and release planning Scrum prescribes no forecasting technique. What it defines is that the Sprint Goal is the commitment, and that projections come from observation. 05 The Product Goal The single objective the Scrum Team plans against, and why a team holding three goals is holding none. Try a question from this domain
An organisation treats the Product Backlog as a signed requirements document that may only change through a change request. What has been lost?
A Nothing, provided change requests are processed within one Sprint. B The Product Backlog is emergent by design, so freezing it prevents the adaptation that inspecting the Increment is supposed to produce. C The Developers can no longer estimate the items accurately. D The Scrum Master can no longer facilitate refinement. 12 questions on this domain.
One per page, with a worked explanation.
Start the set