Agile Business Analysis Agile Elicitation and Collaboration 3 — Questions and Answers
Question 1: Which collaboration technique helps a cross-functional agile team rapidly generate and evaluate a large number of ideas without judgment?
- Root cause analysis
- Brainstorming (Correct answer)
- Gap analysis
- Decision tree analysis
Correct answer: Brainstorming
Brainstorming encourages free idea generation in a judgment-free environment, maximizing creative output from the team.
Question 2: In agile, what does 'just enough' elicitation mean?
- Collecting all requirements before any development begins
- Gathering sufficient detail to begin the next iteration without over-specifying the future (Correct answer)
- Skipping elicitation for low-priority stories
- Documenting every stakeholder request in full detail
Correct answer: Gathering sufficient detail to begin the next iteration without over-specifying the future
Just enough elicitation means gathering only the detail needed for the immediate work, deferring elaboration of future items.
Question 3: A product team wants to validate an early concept with users before committing to full development. Which approach is MOST aligned with agile principles?
- Write a detailed requirements specification and review it with stakeholders
- Build a prototype or MVP and test it with real users (Correct answer)
- Conduct a formal business case review
- Wait until the concept is fully designed before seeking feedback
Correct answer: Build a prototype or MVP and test it with real users
Building a prototype or MVP enables rapid feedback from real users, reducing the risk of building the wrong product.
Question 4: When collaborating with a stakeholder who has low availability, which technique BEST enables asynchronous input into the elicitation process?
- Daily standups
- Online surveys and collaborative document review (Correct answer)
- In-person workshops
- Pair programming sessions
Correct answer: Online surveys and collaborative document review
Online surveys and collaborative document review allow stakeholders to contribute on their own schedule without requiring real-time attendance.
Question 5: What is the key difference between elicitation and requirements analysis in an agile context?
- Elicitation documents requirements; analysis gathers them
- Elicitation draws out information from stakeholders; analysis interprets and structures that information (Correct answer)
- Elicitation is done once; analysis is ongoing
- Elicitation is performed by developers; analysis is done by the product owner
Correct answer: Elicitation draws out information from stakeholders; analysis interprets and structures that information
Elicitation is the discovery activity of gathering information, while analysis involves interpreting, structuring, and deriving meaning from it.
Question 6: A business analyst is running a retrospective-style session to improve the elicitation process itself. Which agile value does this BEST reflect?
- Customer collaboration over contract negotiation
- Working software over comprehensive documentation
- Continuous improvement through inspect and adapt (Correct answer)
- Responding to change over following a plan
Correct answer: Continuous improvement through inspect and adapt
Retrospective-style sessions embody the agile principle of inspecting and adapting the team's process for continuous improvement.
Question 7: Which statement BEST describes the role of the business analyst during agile sprint reviews?
- The BA presents completed documentation to stakeholders
- The BA facilitates stakeholder feedback and captures insights that inform the next sprint's backlog (Correct answer)
- The BA approves or rejects the sprint output on behalf of stakeholders
- The BA is not involved in sprint reviews
Correct answer: The BA facilitates stakeholder feedback and captures insights that inform the next sprint's backlog
During sprint reviews, the BA facilitates stakeholder engagement, captures feedback, and translates insights into actionable backlog refinements.
Agile Business Analysis Agile Elicitation and Collaboration 3
Which collaboration technique helps a cross-functional agile team rapidly generate and evaluate a large number of ideas without judgment?