User Stories and Acceptance Criteria Flashcards
7 cards from real CPOA 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 Stories and Acceptance Criteria flashcards as text
What format is most commonly used to write user stories in agile development?
Answer: As a [role], I want [goal], so that [benefit]
The 'As a [role], I want [goal], so that [benefit]' template is the standard user story format that captures who the user is, what they want, and the business value delivered.
Which element of the INVEST acronym ensures that a user story delivers standalone business or customer value?
Answer: Valuable
The 'V' (Valuable) in INVEST ensures each user story delivers value to the customer or business, making it worth implementing on its own.
What is the primary purpose of acceptance criteria in a user story?
Answer: To define the conditions that must be met for the story to be accepted as complete
Acceptance criteria define the specific, verifiable conditions that must be satisfied for a user story to be considered complete and acceptable by the product owner.
According to the '3 C's' model of user stories, what does the third C represent?
Answer: Confirmation
The 3 C's are Card, Conversation, and Confirmation — Confirmation refers to the acceptance tests or criteria used to verify the story is complete.
What should a product owner do when a user story is too large to complete in a single sprint?
Answer: Split it into smaller, independently deliverable stories
Oversized user stories (epics) should be split into smaller, independently deliverable stories that fit within a single sprint to maintain flow and velocity.
What is a Definition of Done (DoD) in agile?
Answer: A shared team agreement on quality standards that must be met for any work item to be complete
The Definition of Done is a shared, team-level agreement on quality standards — such as coding, testing, and documentation requirements — that must be met for any work item to be considered complete.
Which technique brings together the product owner, developer, and tester to collaboratively review a user story and ensure shared understanding before development begins?
Answer: Three Amigos
The 'Three Amigos' technique brings together the product owner, developer, and tester to discuss a story from their different perspectives and prevent misunderstandings before implementation.