APM User Story Development & Refinement 2 — Questions and Answers
Question 1: A product owner writes: 'As a customer, I want to filter search results so that I can find products faster.' During refinement, the team realizes this story has no measurable acceptance criteria. What is the BEST immediate action?
- Mark the story as ready and move to sprint planning
- Add specific acceptance criteria such as filter options and response time thresholds (Correct answer)
- Split the story into smaller stories before adding any criteria
- Escalate to the business stakeholder to rewrite the story
Correct answer: Add specific acceptance criteria such as filter options and response time thresholds
Acceptance criteria define the specific conditions that must be met for a story to be considered done, making them essential before a story is sprint-ready.
Question 2: Which technique helps a team identify hidden complexity in a user story by exploring the narrative from multiple user perspectives?
- Story mapping
- Personas and role-playing (Correct answer)
- Planning poker
- Kano model analysis
Correct answer: Personas and role-playing
Role-playing different personas during refinement surfaces edge cases and hidden requirements that a single perspective might miss.
Question 3: The INVEST acronym is used to evaluate user stories. What does the 'N' stand for?
- Narrow
- Negotiable (Correct answer)
- Notable
- Non-functional
Correct answer: Negotiable
Negotiable means the story is not a rigid contract — details can be discussed and adjusted between the team and product owner.
Question 4: A team's user story reads: 'As a system, I want to send email notifications so that users are informed.' What is the primary flaw in this story?
- It is too large to complete in one sprint
- The 'system' is not a valid user persona with a genuine need (Correct answer)
- It lacks technical implementation details
- The benefit clause is too vague
Correct answer: The 'system' is not a valid user persona with a genuine need
User stories should be written from the perspective of a human user or stakeholder, not a system, to ensure the story delivers real user value.
Question 5: During backlog refinement, the team estimates a story as 13 story points. Which action is MOST appropriate?
- Accept the estimate and schedule it for the next sprint
- Decompose the story into smaller stories before re-estimating (Correct answer)
- Re-estimate using hours instead of story points
- Archive the story as too large to implement
Correct answer: Decompose the story into smaller stories before re-estimating
Stories with very high estimates (like 13 points) are typically too large and should be split into smaller, more manageable stories.
Question 6: What is the primary purpose of the 'so that' clause in the standard user story template?
- To describe the technical implementation approach
- To articulate the business value or user benefit driving the request (Correct answer)
- To define the acceptance criteria for the story
- To identify dependencies on other stories
Correct answer: To articulate the business value or user benefit driving the request
The 'so that' clause captures the underlying motivation or benefit, helping the team understand why the feature matters and make better implementation decisions.
Question 7: A team notices that many user stories share a common underlying need across different roles. Which refinement technique BEST addresses this pattern?
- Spike solution
- Story abstraction into an epic (Correct answer)
- Velocity recalculation
- Retrospective action item
Correct answer: Story abstraction into an epic
When multiple stories share a common theme or need, abstracting them into an epic helps organize work and reveals the broader feature being built.
APM User Story Development & Refinement 2
A product owner writes: 'As a customer, I want to filter search results so that I can find products faster.' During refinement, the team realizes this story has no measurable acceptance criteria.
What is the BEST immediate action?