CPOA User Stories and Acceptance Criteria 1 — Questions and Answers
Question 1: What format is most commonly used to write user stories in agile development?
- As a [role], I want [goal], so that [benefit] (Correct answer)
- [Actor] should be able to [action] in order to [outcome]
- Given [context], When [action], Then [result]
- The system shall [function] to enable [user] to [goal]
Correct 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.
Question 2: Which element of the INVEST acronym ensures that a user story delivers standalone business or customer value?
- Independent
- Negotiable
- Valuable (Correct answer)
- Estimable
Correct 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.
Question 3: What is the primary purpose of acceptance criteria in a user story?
- To estimate the effort required to complete the story
- To define the conditions that must be met for the story to be accepted as complete (Correct answer)
- To identify the stakeholders who will review the completed story
- To document the technical implementation approach chosen by developers
Correct 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.
Question 4: According to the '3 C's' model of user stories, what does the third C represent?
- Context
- Criteria
- Conversation
- Confirmation (Correct answer)
Correct 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.
Question 5: What should a product owner do when a user story is too large to complete in a single sprint?
- Carry it over to the next sprint as-is without modification
- Remove it from the backlog permanently until resources increase
- Split it into smaller, independently deliverable stories (Correct answer)
- Assign additional team members to complete it within the current sprint
Correct 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.
Question 6: What is a Definition of Done (DoD) in agile?
- A checklist of acceptance criteria specific to one user story
- A shared team agreement on quality standards that must be met for any work item to be complete (Correct answer)
- The sprint goal agreed upon by the team at the start of each iteration
- A list of features that must be delivered by the end of a product release
Correct 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.
Question 7: Which technique brings together the product owner, developer, and tester to collaboratively review a user story and ensure shared understanding before development begins?
- Sprint Review
- Backlog Refinement
- Three Amigos (Correct answer)
- Pair Programming
Correct 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.
CPOA User Stories and Acceptance Criteria 1
What format is most commonly used to write user stories in agile development?