Agile Business Analysis User Stories and Modeling 5 — Questions and Answers
Question 1: A BA notices that a user story's acceptance criteria overlap with those of another story in the backlog. What is the best course of action?
- Delete the duplicate story immediately
- Review both stories with the product owner to merge or clarify boundaries (Correct answer)
- Assign both stories to the same developer to handle
- Add a dependency link and continue without changes
Correct answer: Review both stories with the product owner to merge or clarify boundaries
Overlapping acceptance criteria signal potential duplication or unclear story boundaries, requiring product owner review to prevent redundant work.
Question 2: Which persona characteristic is most critical to include when writing a user story to ensure the right solution is built?
- The persona's job title
- The persona's goals and motivations (Correct answer)
- The persona's salary range
- The persona's technical skill level
Correct answer: The persona's goals and motivations
A persona's goals and motivations drive the 'so that' benefit clause of the user story and guide solution design toward real user needs.
Question 3: A BA is modeling a system that must handle multiple business rules for a single user action. Which technique best captures conditional logic within a user story?
- Decision table (Correct answer)
- Story map
- Velocity chart
- Risk matrix
Correct answer: Decision table
Decision tables systematically capture all combinations of conditions and their corresponding outcomes, clarifying complex business rules.
Question 4: What is the key difference between a user story and a use case?
- User stories are written by developers; use cases are written by BAs
- User stories are brief conversation placeholders; use cases are detailed behavioral specifications (Correct answer)
- User stories require UML notation; use cases do not
- User stories are only for UI features; use cases cover backend processes
Correct answer: User stories are brief conversation placeholders; use cases are detailed behavioral specifications
User stories are intentionally brief to invite conversation, while use cases provide detailed step-by-step behavioral specifications.
Question 5: During backlog refinement, the team finds a story has unclear scope despite multiple discussions. What should the BA recommend?
- Create a spike to investigate and clarify requirements (Correct answer)
- Remove the story from the backlog permanently
- Assign the story to the most senior developer to interpret
- Move the story to the next sprint without changes
Correct answer: Create a spike to investigate and clarify requirements
A spike is appropriate when persistent uncertainty about a story's scope requires dedicated research or prototyping to resolve.
Question 6: A BA is creating a context diagram for a new system. What does this diagram primarily show?
- The internal database schema of the system
- The system's boundaries and its interactions with external entities (Correct answer)
- The sprint timeline and team assignments
- The sequence of user actions within a single feature
Correct answer: The system's boundaries and its interactions with external entities
A context diagram shows the system as a single process, its boundaries, and all external entities that interact with it.
Question 7: Which practice helps a BA ensure that user stories written early in a project remain relevant and accurate as the project evolves?
- Freezing the backlog after sprint 1
- Continuous backlog refinement and story grooming (Correct answer)
- Requiring formal sign-off on all stories before development
- Writing stories only at the start of each sprint
Correct answer: Continuous backlog refinement and story grooming
Continuous backlog refinement ensures stories are regularly reviewed, updated, and reprioritized to reflect current business needs.
A BA notices that a user story's acceptance criteria overlap with those of another story in the backlog.
What is the best course of action?