Managing the Product Backlog
Managing the Product Backlog tests whether you can keep the backlog a living, ordered, value-driven artifact rather than a fixed specification. EXIN Agile Scrum questions often probe DEEP, user stories, acceptance criteria, refinement, and the difference between ordering and labeling.
Backlog characteristics
- DEEP: Detailed appropriately, Estimated, Emergent, Prioritized. Top items are small and clear; lower items are coarse.
- The backlog is never complete in the specification sense; it emerges as learning accumulates.
- Ordering is a sequence based on value, risk, dependencies, and learning, not high-medium-low buckets.
User stories and criteria
- A user story is a placeholder for a conversation: As a role, I want capability, so that benefit. It is not a full requirements document.
- INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable.
- Acceptance criteria define one item; the definition of done is the shared quality bar for every increment.
- Split large stories by workflow step, business rule, data variation, or happy path versus edge cases.
Refinement and non-functional requirements
- Refinement is continuous and just-in-time, not a single grooming session before Sprint Planning.
- Non-functional requirements such as performance, security, and usability belong in the backlog with measurable acceptance criteria; otherwise they are ignored.
- The team estimates size; the Product Owner combines size with value to order.
Worked example
A story says only: As a customer I want to pay by card. It is too large and its value is unclear. The Product Owner splits it into saving a card, paying with a saved card, handling a declined card, and showing confirmation. Each gets measurable acceptance criteria. The declined-card item is ordered high because it reduces support risk. Reasoning: smaller stories improve flow and estimation; measurable criteria make acceptance objective; risk reduction is a form of value, not a technical afterthought.
Traps that cost marks
- The backlog must be fully detailed before Sprint 1: contradicts emergent, just-in-time refinement.
- Prioritized means high-medium-low labels: order is a sequence, and every item has a position.
- A user story is a requirements document: it is a conversation placeholder with acceptance criteria.
- Definition of done and acceptance criteria are the same: the definition of done applies to all items; acceptance criteria are item-specific.
- The Product Owner alone estimates: the people doing the work estimate size.