User Story Development & Refinement Flashcards

Which of the following BEST describes the purpose of a 'walking skeleton' in relation to user stories?

Answer: A minimal set of stories that spans the full system architecture end-to-end

A walking skeleton is a thin, end-to-end implementation of the system that connects all major components, providing a foundation on which to grow functionality story by story.

A team uses relative estimation and finds that a new story is twice as complex as an 8-point story. What story point value should they assign?

Answer: 16

Relative estimation means twice the complexity of an 8-point story is 16 points, assuming a Fibonacci or similar scale where 16 is the next appropriate value.

What is the 'Three Amigos' practice and how does it support story refinement?

Answer: The product owner, a developer, and a tester collaborate to refine a story from three perspectives before it is sprint-ready

Three Amigos brings together business, development, and testing perspectives during refinement to surface misunderstandings and create comprehensive acceptance criteria.

A product owner notices that a story has remained in the backlog unprioritized for six months. What is the BEST action?

Answer: Discuss with stakeholders whether the story is still valuable and archive or delete it if not

Long-dormant backlog items often represent outdated needs; regular backlog grooming should challenge whether such stories still deliver enough value to keep.

When should a team use a 'Behavior-Driven Development (BDD)' style for writing acceptance criteria?

Answer: When the team wants acceptance criteria expressed as executable specifications that serve as both documentation and automated tests

BDD-style acceptance criteria written in Given-When-Then can be directly executed as automated tests, creating living documentation that validates the system.

Which of the following scenarios represents a story that violates the 'Estimable' criterion of INVEST?

Answer: A story about redesigning the entire platform architecture with no further detail

A story too vague or too large to estimate violates the Estimable criterion; the team cannot commit to work they cannot size.

A product owner writes: 'As a user, I want the system to be fast so that I am not frustrated.' What is the PRIMARY issue with this story?

Answer: The benefit clause exists but the acceptance criteria for 'fast' are undefined and untestable

Without a measurable definition of 'fast' (e.g., page loads in under 2 seconds), the story cannot be tested or verified as complete.