Agile Business Analysis FREE Agile Business Analysis User Stories and Modeling Questions and Answers 2 — Questions and Answers
Question 1: Which technique helps an Agile team decompose a large user story (epic) into smaller, independently deliverable pieces?
- Story mapping (Correct answer)
- Gantt charting
- Critical path analysis
- Work breakdown structure
Correct answer: Story mapping
Story mapping visually arranges user stories along a narrative flow, making it easier to split epics into thin, vertical slices that deliver end-to-end value.
Question 2: In the INVEST criteria for well-formed user stories, what does the 'N' stand for?
- Negotiable (Correct answer)
- Necessary
- Nominal
- Non-functional
Correct answer: Negotiable
The 'N' in INVEST stands for Negotiable, meaning the story details should be open to discussion between the team and product owner rather than rigidly specified.
Question 3: What is the primary purpose of a persona in Agile business analysis?
- To represent a fictional but realistic end-user archetype (Correct answer)
- To define system architecture constraints
- To document regulatory compliance requirements
- To assign tasks to specific team members
Correct answer: To represent a fictional but realistic end-user archetype
Personas are fictional user archetypes based on real research that help the team empathize with end users and write more targeted user stories.
Question 4: When using the 'Given-When-Then' format for acceptance criteria, what does the 'Given' clause specify?
- The precondition or initial context before the action (Correct answer)
- The action performed by the user
- The expected outcome after the action
- The non-functional performance requirement
Correct answer: The precondition or initial context before the action
The 'Given' clause establishes the precondition or starting state that must be true before the scenario's action is triggered.
Question 5: Which modeling technique uses a simple grid to show how different user roles interact with various system features?
- Role-feature matrix (Correct answer)
- Sequence diagram
- Entity-relationship diagram
- Data flow diagram
Correct answer: Role-feature matrix
A role-feature matrix maps user roles against system features to quickly identify which roles need access to which capabilities.
Question 6: What distinguishes a spike from a regular user story in Agile?
- A spike is time-boxed research to reduce uncertainty, not to deliver production code (Correct answer)
- A spike must always be completed within a single sprint
- A spike replaces the need for acceptance criteria
- A spike is used only for bug fixes
Correct answer: A spike is time-boxed research to reduce uncertainty, not to deliver production code
A spike is a time-boxed investigation aimed at answering a question or reducing technical risk, producing knowledge rather than shippable product functionality.
Which technique helps an Agile team decompose a large user story (epic) into smaller, independently deliverable pieces?