CAE User Story Development & Refinement 2 — Questions and Answers
Question 1: A product owner notices that a user story's acceptance criteria conflict with each other. What is the BEST first step?
- Delete the conflicting criteria and rewrite the story
- Facilitate a conversation with stakeholders to resolve the conflict (Correct answer)
- Split the story into two separate stories immediately
- Move the story to the icebox until the conflict resolves itself
Correct 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.
Question 2: Which statement BEST describes the 'N' in the INVEST criteria for user stories?
- The story must be written in natural language
- The story can be estimated without depending on other stories
- The story must be negotiable and not a fixed contract (Correct answer)
- The story should have no more than three acceptance criteria
Correct 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.
Question 3: A team consistently underestimates stories about third-party API integration. What refinement action would help MOST?
- Add a spike story to research the API before committing to estimates (Correct answer)
- Permanently assign the API integration stories a fixed high estimate
- Remove API integration stories from the backlog
- Ask the vendor to write the acceptance criteria
Correct 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.
Question 4: What is the primary purpose of a story map in user story development?
- To assign ownership of each story to a developer
- To visualize the full user journey and identify gaps in the backlog (Correct answer)
- To replace the product backlog with a two-dimensional structure
- To track which stories have been completed across sprints
Correct 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.
Question 5: 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?
- Force-split the story using any available technique
- Keep the story in the backlog as an epic until it can be properly decomposed (Correct answer)
- Remove it from the backlog until the next quarter
- Assign it to the most senior developer to handle alone
Correct 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.
Question 6: A user story reads: 'As an admin, I want to manage users.' Why is this story problematic?
- It uses the word 'manage,' which is not allowed in agile
- The role 'admin' is too technical and should be replaced with a persona
- The story lacks specific, testable acceptance criteria and is too vague (Correct answer)
- It does not follow the INVEST criteria for being small enough
Correct 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.
Question 7: What does 'definition of ready' mean in the context of user story refinement?
- The story has been approved by the project manager
- The story meets agreed-upon criteria before it can be pulled into a sprint (Correct answer)
- The developer has confirmed they understand the story
- The story has passed QA review
Correct 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.
CAE User Story Development & Refinement 2
A product owner notices that a user story's acceptance criteria conflict with each other.
What is the BEST first step?