Agile Business Analysis Agile Elicitation and Collaboration 5 — Questions and Answers
Question 1: Which technique is MOST effective for eliciting requirements from a large, geographically dispersed group of stakeholders in an agile project?
- One-on-one in-person interviews
- Virtual facilitated workshops with collaborative tools (Correct answer)
- Mailing printed questionnaires
- Holding a single large in-person meeting
Correct answer: Virtual facilitated workshops with collaborative tools
Virtual facilitated workshops with collaborative tools enable broad participation and real-time collaboration regardless of location.
Question 2: What is the purpose of 'elephant carpaccio' as an agile elicitation and slicing technique?
- Estimating story points for large epics
- Slicing large features into the thinnest possible vertical slices to enable early delivery (Correct answer)
- Prioritizing the product backlog using weighted scoring
- Mapping dependencies between user stories
Correct answer: Slicing large features into the thinnest possible vertical slices to enable early delivery
Elephant carpaccio is a technique for decomposing large features into ultra-thin vertical slices, each delivering a small but complete piece of value.
Question 3: A business analyst wants to ensure all acceptance criteria are testable. Which format BEST supports this goal?
- Free-form narrative descriptions
- Given-When-Then (Gherkin) format (Correct answer)
- Bulleted lists of business rules
- UML use case diagrams
Correct answer: Given-When-Then (Gherkin) format
Given-When-Then format structures acceptance criteria as concrete, verifiable scenarios that can be directly translated into automated tests.
Question 4: What does it mean for a user story to be 'INVEST' compliant?
- It has been approved by the investment committee
- It is Independent, Negotiable, Valuable, Estimable, Small, and Testable (Correct answer)
- It includes a full cost-benefit analysis
- It has been reviewed by all stakeholders
Correct answer: It is Independent, Negotiable, Valuable, Estimable, Small, and Testable
INVEST is an acronym for the six qualities that make a well-formed user story: Independent, Negotiable, Valuable, Estimable, Small, and Testable.
Question 5: In an agile project, which behavior BEST demonstrates effective collaboration between the business analyst and the development team?
- The BA hands off a completed requirements document and steps away
- The BA participates in sprint ceremonies, answers questions, and refines stories with developers throughout the sprint (Correct answer)
- The BA reviews completed work only at the end of the sprint
- The BA submits change requests through a formal change control board
Correct answer: The BA participates in sprint ceremonies, answers questions, and refines stories with developers throughout the sprint
Active, continuous participation in sprint ceremonies and story refinement ensures the BA serves as a bridge between business needs and technical delivery.
Question 6: A product owner wants to reduce time spent in backlog refinement sessions. Which strategy would MOST effectively achieve this?
- Eliminate refinement sessions entirely
- Invest in continuous, lightweight refinement throughout the sprint rather than one long session (Correct answer)
- Limit backlog items to only the current sprint
- Delegate all refinement to developers
Correct answer: Invest in continuous, lightweight refinement throughout the sprint rather than one long session
Continuous lightweight refinement distributes the effort across the sprint, reducing the need for lengthy formal sessions while keeping the backlog healthy.
Question 7: Which agile elicitation practice BEST addresses the risk of gold-plating (adding unnecessary features)?
- Encouraging stakeholders to request all possible features upfront
- Using the Minimum Viable Product (MVP) concept to focus on essential value first (Correct answer)
- Approving all feature requests to maintain stakeholder satisfaction
- Deferring all features not in the initial contract
Correct answer: Using the Minimum Viable Product (MVP) concept to focus on essential value first
The MVP concept constrains scope to the minimum needed to deliver core value, preventing over-engineering and unnecessary feature creep.
Agile Business Analysis Agile Elicitation and Collaboration 5
Which technique is MOST effective for eliciting requirements from a large, geographically dispersed group of stakeholders in an agile project?