Backlog Refinement & Prioritization Flashcards

How does DA's 'Choose Your WoW' (Way of Working) philosophy apply to backlog refinement cadence?

Answer: Teams should experiment with and choose the refinement cadence that best fits their context

DA's 'Choose Your WoW' philosophy means teams select the refinement cadence—weekly, bi-weekly, continuous—that best suits their workflow and context.

A product owner frequently rewrites already-refined stories just before sprint planning. What is the BEST coaching intervention?

Answer: Establish a stability agreement—stories accepted into sprint planning should not be changed without team consent

A stability agreement or Definition of Ready rule prevents late-breaking changes that disrupt planning and erode team trust.

In DA, what is the significance of 'outcome-based' acceptance criteria over 'output-based' criteria during refinement?

Answer: Outcome-based criteria define the desired user or business result, ensuring the team builds toward value rather than mere feature completion

Outcome-based acceptance criteria tie story completion to measurable business or user results, aligning delivery with the DA principle of delighting customers.

When using the Kano model during backlog refinement, which category of features should typically be prioritized first to avoid customer dissatisfaction?

Answer: Must-be (basic) features

Must-be features are baseline expectations whose absence causes dissatisfaction, so they must be delivered before investing in delighters or performance differentiators.

A DAC is coaching a scaled program with six teams. What is the recommended approach to managing inter-team dependencies discovered during backlog refinement?

Answer: Surface dependencies early, visualize them on a program board or dependency map, and coordinate resolution across teams

Surfacing and visualizing inter-team dependencies early—using program boards or dependency maps—enables proactive coordination and prevents downstream blockers.

Which DA process blade most directly governs how teams manage and prioritize their incoming work requests?

Answer: Manage the Work Item List

The 'Manage the Work Item List' process blade in DA covers the full lifecycle of work items including intake, triage, prioritization, and refinement.

What is the primary risk of using velocity alone as the basis for backlog prioritization decisions?

Answer: Velocity measures output speed but ignores business value, leading to fast delivery of low-value items

Optimizing for velocity without coupling it to value metrics can create a fast-moving team that delivers high output but low customer impact.