Agile Business Analysis Agile Business Analysis: Agile Methodology 1 — Questions and Answers
Question 1: In Agile business analysis, which artifact is BEST used to capture high-level features and requirements before they are broken down into user stories?
- Sprint backlog
- Epic (Correct answer)
- Release plan
- Definition of Done
Correct answer: Epic
An epic is a large body of work that captures high-level features or requirements. It serves as a container for related user stories and is decomposed into smaller, actionable stories as the team refines the backlog.
Question 2: A business analyst notices that the development team consistently underestimates story points during sprint planning. Which Agile technique should the BA recommend to improve estimation accuracy?
- MoSCoW prioritization
- Planning Poker (Correct answer)
- Burndown charting
- Kano analysis
Correct answer: Planning Poker
Planning Poker is a consensus-based estimation technique where team members use numbered cards to vote on effort estimates simultaneously, reducing anchoring bias and improving collective accuracy.
Question 3: Which Agile principle BEST supports the practice of delivering working software frequently in short iterations?
- Responding to change over following a plan
- Customer collaboration over contract negotiation
- Working software over comprehensive documentation (Correct answer)
- Individuals and interactions over processes and tools
Correct answer: Working software over comprehensive documentation
The Agile Manifesto value of 'working software over comprehensive documentation' underpins the practice of delivering functional increments frequently, prioritizing tangible, tested output over written artifacts.
Question 4: During a sprint retrospective, the team identifies that unclear acceptance criteria caused rework in the last sprint. As the Agile BA, what is the MOST appropriate corrective action?
- Increase the sprint length to allow more time for rework
- Add more detailed technical specifications to the sprint backlog
- Collaborate with the product owner to define clear, testable acceptance criteria before sprint planning (Correct answer)
- Move acceptance criteria definition to the sprint review
Correct answer: Collaborate with the product owner to define clear, testable acceptance criteria before sprint planning
Defining clear, testable acceptance criteria with the product owner before sprint planning ensures the team has a shared understanding of 'done,' reducing ambiguity and rework in future sprints.
Question 5: What is the primary difference between a Scrum Master and a Product Owner in an Agile team?
- The Scrum Master prioritizes the backlog; the Product Owner facilitates ceremonies
- The Scrum Master removes impediments and coaches the team; the Product Owner owns the product vision and backlog priority (Correct answer)
- The Scrum Master writes user stories; the Product Owner approves them
- The Scrum Master manages the budget; the Product Owner manages the team
Correct answer: The Scrum Master removes impediments and coaches the team; the Product Owner owns the product vision and backlog priority
The Scrum Master is a servant-leader who removes obstacles and ensures the team follows Agile practices, while the Product Owner is accountable for maximizing product value by managing and prioritizing the product backlog.
Question 6: An Agile business analyst is working with stakeholders who have conflicting priorities for the product backlog. Which technique is MOST effective for reaching a prioritized consensus?
- SWOT analysis
- MoSCoW prioritization (Correct answer)
- Root cause analysis
- Gap analysis
Correct answer: MoSCoW prioritization
MoSCoW prioritization (Must have, Should have, Could have, Won't have) provides a structured framework for stakeholders to collaboratively categorize and agree on the relative importance of backlog items, surfacing trade-offs transparently.
Agile Business Analysis Agile Business Analysis: Agile Methodology 1
In Agile business analysis, which artifact is BEST used to capture high-level features and requirements before they are broken down into user stories?