Agile Business Analysis Agile Business Analysis Agile Elicitation and Collaboration Questions and Answers 2 — Questions and Answers
Question 1: During a sprint planning session, the business analyst notices that stakeholders are providing conflicting requirements. What is the BEST elicitation technique to resolve this?
- Send an email asking each stakeholder to rank their priorities
- Facilitate a structured workshop with all stakeholders to collaboratively negotiate priorities (Correct answer)
- Escalate the conflict to the product owner and step back
- Document both sets of requirements and let the development team choose
Correct answer: Facilitate a structured workshop with all stakeholders to collaboratively negotiate priorities
A structured workshop enables real-time collaboration, allowing stakeholders to hear each other's perspectives and reach consensus on priorities.
Question 2: Which collaborative technique is MOST effective for eliciting non-functional requirements in an agile environment?
- User story mapping
- Quality attribute workshops (Correct answer)
- Daily stand-ups
- Retrospectives
Correct answer: Quality attribute workshops
Quality attribute workshops specifically target non-functional requirements by bringing together architects, developers, and stakeholders to define quality attributes and scenarios.
Question 3: An agile business analyst is working with a geographically distributed team. Which elicitation approach BEST maintains collaboration effectiveness?
- Rely exclusively on written documentation shared via email
- Use asynchronous communication tools only to respect time zones
- Combine synchronous video sessions with shared digital collaboration boards (Correct answer)
- Have one team member collect all requirements and distribute them
Correct answer: Combine synchronous video sessions with shared digital collaboration boards
Combining synchronous video sessions with shared digital boards balances real-time collaboration with persistent visual artifacts that distributed teams can reference.
Question 4: What is the PRIMARY purpose of using observation as an elicitation technique in agile business analysis?
- To verify that developers are following coding standards
- To understand actual workflows and identify unstated requirements (Correct answer)
- To monitor team velocity and sprint progress
- To evaluate stakeholder engagement levels
Correct answer: To understand actual workflows and identify unstated requirements
Observation helps business analysts discover tacit knowledge and actual work practices that stakeholders may not articulate during interviews or workshops.
Question 5: In an agile context, when should a business analyst use prototyping as an elicitation technique?
- Only after all user stories have been written and approved
- When stakeholders struggle to articulate requirements for a new or unfamiliar system (Correct answer)
- Only during the final sprint before release
- When the team has excess capacity and needs additional work
Correct answer: When stakeholders struggle to articulate requirements for a new or unfamiliar system
Prototyping is most valuable when stakeholders cannot easily describe what they need, as it provides a tangible artifact to react to and refine.
Question 6: Which practice BEST demonstrates the agile principle of collaboration over documentation during elicitation?
- Creating comprehensive requirements documents before development begins
- Using a shared product backlog that is continuously refined through stakeholder conversations (Correct answer)
- Eliminating all written artifacts to maximize face-to-face time
- Recording every meeting and distributing transcripts to all team members
Correct answer: Using a shared product backlog that is continuously refined through stakeholder conversations
A shared product backlog refined through ongoing conversations embodies agile collaboration by maintaining just enough documentation while prioritizing continuous stakeholder engagement.
During a sprint planning session, the business analyst notices that stakeholders are providing conflicting requirements.
What is the BEST elicitation technique to resolve this?