Agile Business Analysis Agile Elicitation and Collaboration Questions and Answers — Questions and Answers
Question 1: An Agile team is kicking off a new initiative to build a customer relationship management (CRM) tool. The team needs to understand the end-to-end user journey and break down the work into a manageable backlog. What elicitation technique is BEST suited for visualizing the user's workflow and organizing features into a narrative flow?
- Personas
- Spikes
- Story Mapping (Correct answer)
- Interviews
Correct answer: Story Mapping
Story Mapping is a collaborative technique used to arrange user stories into a model that visualizes the user's entire journey. It organizes user activities chronologically along a horizontal axis and details user stories vertically by priority, creating a holistic view that is perfect for understanding workflow and planning releases.
Question 2: A business analyst wants to facilitate a session to identify problems and frustrations with an existing software product. Which collaborative elicitation game uses the metaphor of a boat being held back by anchors to help stakeholders identify impediments?
- Prune the Product Tree
- Remember the Future
- Affinity Mapping
- Speed Boat (Correct answer)
Correct answer: Speed Boat
The 'Speed Boat' (or 'Sailboat') game is a retrospective and elicitation technique where the boat represents the product, and anchors represent problems, risks, or anything slowing it down. This visual metaphor is highly effective for collaboratively identifying pain points.
Question 3: In an Agile context, the 'Three Amigos' refers to a collaborative practice that aims to create a shared understanding of a user story before development begins. Who are the typical participants in a 'Three Amigos' meeting?
- The Project Manager, the Lead Developer, and the Scrum Master
- A Business Representative (e.g., Product Owner/BA), a Developer, and a Tester (Correct answer)
- The Scrum Master, the Product Owner, and a Key Stakeholder
- The Business Analyst, the UX Designer, and the System Architect
Correct answer: A Business Representative (e.g., Product Owner/BA), a Developer, and a Tester
The 'Three Amigos' represents the three critical perspectives for a user story: business (what is the problem?), development (how can we build it?), and testing (how do we know it's correct?). These perspectives are typically embodied by a Product Owner or Business Analyst, a developer, and a tester to ensure a story is well-understood and ready for development.
Question 4: Which of the following BEST describes the agile principle of 'just-in-time' analysis?
- Performing a comprehensive analysis of all requirements at the very beginning of the project.
- Deferring detailed analysis and specification of requirements until just before they are needed for development. (Correct answer)
- Analyzing requirements only after the development work for an iteration has been completed.
- Holding a single, multi-day workshop to elicit all user requirements before the first sprint.
Correct answer: Deferring detailed analysis and specification of requirements until just before they are needed for development.
Just-in-time (JIT) analysis is an agile practice that avoids the waste of extensive upfront analysis. By detailing requirements for features right before they are scheduled for implementation, teams can incorporate the most current knowledge and feedback, increasing flexibility and reducing rework.
Question 5: An Agile BA is preparing for a backlog refinement meeting. The goal is to ensure that user stories at the top of the backlog are well-understood, estimable, and ready for the next sprint. Which activity is the primary focus of this meeting?
- Committing the team to the work they will complete in the next sprint.
- Gaining formal sign-off on the requirements from all stakeholders.
- Facilitating a discussion with the team to add detail, clarify acceptance criteria, and split large stories. (Correct answer)
- Presenting a completed, unchangeable list of requirements for the team to estimate.
Correct answer: Facilitating a discussion with the team to add detail, clarify acceptance criteria, and split large stories.
Backlog refinement is an ongoing, collaborative process where the BA, Product Owner, and development team work together to ensure backlog items are ready for future sprints. Key activities include clarifying requirements, defining acceptance criteria, and decomposing large items into smaller, manageable stories, which ensures a shared understanding before the commitment of a sprint planning meeting.
Question 6: What is the primary purpose of using low-fidelity prototypes, such as paper sketches or simple wireframes, during early elicitation sessions?
- To formally document and sign off on the complete set of system requirements.
- To provide the development team with the final, detailed user interface for implementation.
- To facilitate rapid feedback and collaboration on concepts without a large investment in design or code. (Correct answer)
- To create a legally binding contract for the scope of work to be delivered.
Correct answer: To facilitate rapid feedback and collaboration on concepts without a large investment in design or code.
Low-fidelity prototypes are intentionally simple and inexpensive to create. Their main purpose is to serve as a conversation starter, making it easy to gather early feedback, test concepts, and collaborate with stakeholders without investing significant time or resources in polished designs or development.
