APM User Story Development & Refinement 3 — Questions and Answers
Question 1: Which splitting pattern divides a user story based on the sequence of steps a user takes to accomplish a goal?
- Split by data variation
- Split by workflow steps (Correct answer)
- Split by business rule complexity
- Split by user role
Correct answer: Split by workflow steps
Splitting by workflow steps breaks a story into sequential sub-stories that each represent a distinct step in the user's process.
Question 2: A product owner adds a new story to the backlog mid-sprint without team consultation. According to agile principles, what should happen?
- The team must immediately incorporate the new story
- The scrum master should add it to the current sprint backlog
- The story should be added to the product backlog for consideration in future sprint planning (Correct answer)
- The team votes on whether to include it in the current sprint
Correct answer: The story should be added to the product backlog for consideration in future sprint planning
Mid-sprint backlog changes disrupt the team's focus; new stories should be captured in the product backlog and prioritized for a future sprint.
Question 3: What distinguishes a 'spike' from a standard user story in agile product management?
- A spike is a large user story that spans multiple sprints
- A spike is a time-boxed research task to reduce uncertainty, not deliver working software (Correct answer)
- A spike is a user story written by the development team rather than the product owner
- A spike represents a non-functional requirement
Correct answer: A spike is a time-boxed research task to reduce uncertainty, not deliver working software
Spikes are time-boxed investigation or research tasks used to answer specific technical or design questions that block story refinement.
Question 4: When using Given-When-Then (GWT) format for acceptance criteria, what does the 'Given' clause specify?
- The expected outcome of the user action
- The preconditions or context that must exist before the action (Correct answer)
- The action the user will perform
- The business rule being validated
Correct answer: The preconditions or context that must exist before the action
The 'Given' clause establishes the initial context or state of the system before the user performs the action described in the 'When' clause.
Question 5: A team consistently finds that user stories are not 'Ready' for sprint planning. Which practice MOST directly addresses this problem?
- Increasing sprint length to allow more planning time
- Conducting regular backlog refinement sessions with the team (Correct answer)
- Reducing the definition of ready requirements
- Assigning a dedicated writer to create stories in advance
Correct answer: Conducting regular backlog refinement sessions with the team
Regular backlog refinement ensures stories are continuously groomed, estimated, and clarified so they meet the definition of ready before sprint planning.
Question 6: Which of the following BEST describes the concept of 'thin vertical slices' in user story development?
- Stories that focus only on the UI layer
- Stories that deliver end-to-end functionality across all technical layers with minimal scope (Correct answer)
- Stories that are assigned to a single developer
- Stories that skip non-functional requirements
Correct answer: Stories that deliver end-to-end functionality across all technical layers with minimal scope
Thin vertical slices cut through all layers (UI, business logic, data) to deliver a small but complete piece of working functionality, enabling early feedback.
Question 7: A product owner wants to capture a constraint such as 'the system must support 10,000 concurrent users.' How should this BEST be represented in the backlog?
- As a standard user story with the system as the actor
- As a non-functional requirement or quality attribute story (Correct answer)
- As a spike to investigate feasibility
- As a bug report targeting the current architecture
Correct answer: As a non-functional requirement or quality attribute story
Performance and scalability constraints are non-functional requirements that should be explicitly captured and tracked as quality attribute stories in the backlog.
APM User Story Development & Refinement 3
Which splitting pattern divides a user story based on the sequence of steps a user takes to accomplish a goal?