User Story Development & Refinement Flashcards

Which refinement anti-pattern occurs when the product owner presents fully detailed specifications and expects no team input during refinement?

Answer: Command-and-control refinement

Command-and-control refinement undermines collaboration; effective refinement is a team conversation where developers and the PO jointly clarify and shape stories.

When should a product owner consider adding a story to the backlog as an 'enabler' or 'infrastructure' story?

Answer: When a feature story depends on underlying technical work that doesn't directly deliver user value on its own

Enabler stories capture necessary technical groundwork (architecture, infrastructure, refactoring) that unblocks future feature stories even though they don't directly deliver user-facing value.

A team regularly discovers new requirements while implementing a story during the sprint. What refinement practice would MOST reduce this issue?

Answer: More thorough acceptance criteria definition during backlog refinement

Thorough acceptance criteria defined before the sprint starts surface ambiguities early, reducing mid-sprint discovery of undiscussed requirements.

In the context of user story refinement, what is 'story splitting by data variation'?

Answer: Creating separate stories for each type of data entity or data set the feature must handle

Splitting by data variation creates distinct stories for different data types or categories (e.g., handling credit card vs. PayPal payments separately).

Which statement BEST describes the relationship between epics and user stories in agile product management?

Answer: Epics are large bodies of work that are broken down into smaller, more actionable user stories

Epics represent high-level features or goals that are too large to deliver in a single sprint and are progressively refined into smaller user stories as the team learns more.

A team using Behavior-Driven Development (BDD) writes acceptance criteria using Given-When-Then. What is the primary benefit of this format?

Answer: It creates executable specifications that bridge business requirements and automated tests

GWT format expresses acceptance criteria in a structured way that can be directly translated into automated tests, aligning business expectations with verifiable behavior.

What is the recommended approach when a user story is too large to complete in a single sprint but cannot easily be split?

Answer: Treat it as an epic and create a placeholder; then conduct a spike to identify splitting opportunities

When a story resists splitting, treating it as an epic and using a spike to investigate decomposition options helps the team find a viable path forward.