Agile Business Analysis Agile Business Analysis 4 — Questions and Answers
Question 1: What is the PRIMARY difference between 'given-when-then' and traditional use case formats for defining acceptance criteria?
- Given-when-then is only used for automated testing, not business analysis
- Given-when-then expresses behavior in a scenario-based, testable format accessible to all team members (Correct answer)
- Traditional use cases are always preferred in Agile teams
- Given-when-then requires a dedicated BDD tool to be useful
Correct answer: Given-when-then expresses behavior in a scenario-based, testable format accessible to all team members
Given-when-then (BDD-style) writes acceptance criteria as concrete scenarios that are easily understood by business analysts, developers, and testers alike.
Question 2: A business analyst is facilitating a product backlog refinement session and notices one story has a very high estimate. What should the analyst do?
- Accept the estimate and move on
- Ask the team to lower the estimate to fit the sprint
- Facilitate a discussion to understand complexity and split the story if needed (Correct answer)
- Remove the story from the backlog entirely
Correct answer: Facilitate a discussion to understand complexity and split the story if needed
A high estimate often signals a story that is too large or complex and should be broken into smaller, more manageable pieces.
Question 3: In Scaled Agile Framework (SAFe), what is the role of a 'Business Owner' during PI Planning?
- To assign individual tasks to developers
- To provide business context and validate team objectives against business priorities (Correct answer)
- To manage the Scrum ceremonies for each team
- To approve all technical architecture decisions
Correct answer: To provide business context and validate team objectives against business priorities
Business Owners attend PI Planning to provide strategic context, review team objectives, and ensure alignment with business priorities.
Question 4: Which analysis technique helps a business analyst determine the minimum viable set of features needed to test a hypothesis with real users?
- Root cause analysis
- MoSCoW prioritization
- MVP (Minimum Viable Product) analysis (Correct answer)
- Gap analysis
Correct answer: MVP (Minimum Viable Product) analysis
MVP analysis identifies the smallest feature set that delivers enough value to test core assumptions with actual users and gather feedback.
Question 5: A product owner asks the business analyst to help prioritize the backlog. The team has limited capacity and many conflicting stakeholder requests. Which technique accounts for BOTH business value AND effort?
- WSJF (Weighted Shortest Job First) (Correct answer)
- MoSCoW
- Dot voting
- Story point estimation only
Correct answer: WSJF (Weighted Shortest Job First)
WSJF prioritizes items by dividing the cost of delay by job duration, balancing business value against the effort required.
Question 6: What does 'continuous discovery' mean in the context of Agile Business Analysis?
- Running a requirements workshop at the start of every sprint
- Ongoing user research and validation throughout the product lifecycle, not just at the beginning (Correct answer)
- Continuously adding new features based on stakeholder requests
- Discovering defects continuously through automated testing
Correct answer: Ongoing user research and validation throughout the product lifecycle, not just at the beginning
Continuous discovery is the practice of regularly engaging with users and stakeholders throughout development to validate assumptions and learn from real feedback.
Question 7: When creating a context diagram for an Agile project, what does it primarily show?
- The internal data flow between system modules
- The system's boundaries and its interactions with external entities (Correct answer)
- The sequence of sprint ceremonies
- The team's communication channels
Correct answer: The system's boundaries and its interactions with external entities
A context diagram illustrates the system boundary and shows how the system interacts with external actors, systems, and data sources.
What is the PRIMARY difference between 'given-when-then' and traditional use case formats for defining acceptance criteria?