Agile Business Analysis General 5 — Questions and Answers
Question 1: A BA is facilitating a story mapping session. What is the primary output of this exercise?
- A risk register for the project
- A visual representation of the user journey with stories organized by activity and priority (Correct answer)
- A detailed functional specification document
- A completed sprint backlog for the next three iterations
Correct answer: A visual representation of the user journey with stories organized by activity and priority
Story mapping produces a two-dimensional visual of user activities (horizontal) and story priority (vertical), enabling shared understanding and release planning.
Question 2: Which practice best supports 'failing fast' in agile business analysis?
- Delaying all testing until after full feature completion
- Building and testing low-fidelity prototypes early to validate assumptions quickly (Correct answer)
- Avoiding experimentation to reduce project risk
- Waiting for stakeholder sign-off before beginning any development work
Correct answer: Building and testing low-fidelity prototypes early to validate assumptions quickly
Low-fidelity prototypes and early testing allow teams to validate or invalidate assumptions quickly before investing in full development.
Question 3: When decomposing requirements in agile, what is the correct order from largest to smallest?
- Stories → Features → Epics → Themes
- Themes → Epics → Features → Stories → Tasks (Correct answer)
- Tasks → Stories → Epics → Features → Themes
- Features → Themes → Epics → Stories → Tasks
Correct answer: Themes → Epics → Features → Stories → Tasks
The agile hierarchy flows from Themes (strategic goals) down through Epics, Features, Stories, and finally Tasks (work units).
Question 4: A business analyst is asked to measure whether a new feature delivered actual business value. Which approach is most appropriate?
- Count the number of user stories completed in the release
- Track predefined KPIs or OKRs before and after the feature launch (Correct answer)
- Review the feature's acceptance criteria checklist
- Measure developer satisfaction with the implementation
Correct answer: Track predefined KPIs or OKRs before and after the feature launch
Comparing predefined KPIs or OKRs before and after delivery is the most objective way to measure whether a feature delivered real business value.
Question 5: In agile business analysis, what is the purpose of a 'spike'?
- A short burst of unplanned development to fix production bugs
- A time-boxed research effort to reduce uncertainty before estimating or implementing a story (Correct answer)
- A technique for rapidly prioritizing the backlog under deadline pressure
- A meeting to negotiate scope between the BA and the development team
Correct answer: A time-boxed research effort to reduce uncertainty before estimating or implementing a story
A spike is a time-boxed investigation used to answer a specific question or reduce risk before committing to an estimate or implementation approach.
Question 6: Which of the following is a key difference between agile and traditional (waterfall) business analysis?
- Agile BAs document more extensively than waterfall BAs
- Agile BAs collaborate continuously with the team, while waterfall BAs hand off requirements in a formal document at the start (Correct answer)
- Agile BAs have no involvement after requirements are defined
- Waterfall BAs attend daily standups; agile BAs do not
Correct answer: Agile BAs collaborate continuously with the team, while waterfall BAs hand off requirements in a formal document at the start
Agile BAs remain embedded in the team throughout delivery, continuously refining requirements, while waterfall BAs typically hand off a requirements document before development begins.
Question 7: What is the primary benefit of using acceptance test-driven development (ATDD) in agile projects?
- It eliminates the need for a QA team on agile projects
- It ensures shared understanding of expected behavior before development begins by defining tests collaboratively upfront (Correct answer)
- It replaces user stories with formal test plans as the primary requirements artifact
- It allows developers to write acceptance tests after completing the code
Correct answer: It ensures shared understanding of expected behavior before development begins by defining tests collaboratively upfront
ATDD creates shared understanding by having BAs, developers, and testers collaborate to define acceptance tests before coding starts, reducing ambiguity.
Agile Business Analysis General 5
A BA is facilitating a story mapping session.
What is the primary output of this exercise?