User Story Development & Refinement Flashcards
7 cards from real CAE practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 User Story Development & Refinement flashcards as text
A product owner notices that a user story's acceptance criteria conflict with each other. What is the BEST first step?
Answer: Facilitate a conversation with stakeholders to resolve the conflict
Conflicting acceptance criteria signal misaligned stakeholder expectations, which require facilitated conversation to surface and resolve.
Which statement BEST describes the 'N' in the INVEST criteria for user stories?
Answer: The story must be negotiable and not a fixed contract
The 'N' in INVEST stands for Negotiable, meaning the story details can be discussed and adjusted collaboratively rather than treated as a rigid specification.
A team consistently underestimates stories about third-party API integration. What refinement action would help MOST?
Answer: Add a spike story to research the API before committing to estimates
A spike is a time-boxed investigation story used to reduce uncertainty and gather information needed for more accurate future estimates.
What is the primary purpose of a story map in user story development?
Answer: To visualize the full user journey and identify gaps in the backlog
Story maps arrange user activities horizontally and tasks vertically, revealing the big picture of the user journey and highlighting missing stories.
During backlog refinement, the team identifies a story that is too large to complete in one sprint but does not yet have enough information to split it. What should happen?
Answer: Keep the story in the backlog as an epic until it can be properly decomposed
Large stories lacking sufficient detail are epics that should remain in the backlog and be further refined as more information becomes available.
A user story reads: 'As an admin, I want to manage users.' Why is this story problematic?
Answer: The story lacks specific, testable acceptance criteria and is too vague
Vague verbs like 'manage' hide scope and make the story untestable; the team cannot verify completion without specific acceptance criteria.
What does 'definition of ready' mean in the context of user story refinement?
Answer: The story meets agreed-upon criteria before it can be pulled into a sprint
The definition of ready is a team agreement on the minimum conditions a story must meet before the team commits to working on it in a sprint.