Agile Business Analysis In Scrum Environment 5 — Questions and Answers
Question 1: A BA is helping a Scrum team that suffers from 'scope creep within stories' — developers keep adding features beyond the acceptance criteria. What technique helps prevent this?
- Increase sprint length to accommodate extra features
- Enforce INVEST criteria and clear acceptance criteria as the guardrail (Correct answer)
- Remove acceptance criteria to give developers more flexibility
- Let the PO decide during the sprint review what to keep
Correct answer: Enforce INVEST criteria and clear acceptance criteria as the guardrail
INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) and clear acceptance criteria define story boundaries and prevent gold-plating.
Question 2: In Scrum, which practice ensures the BA keeps the Product Backlog items prioritized by business value?
- Technical complexity ordering
- Regular backlog refinement with the Product Owner using value-based prioritization (Correct answer)
- Alphabetical ordering by feature name
- Ordering by the date requests were received
Correct answer: Regular backlog refinement with the Product Owner using value-based prioritization
Regular refinement sessions where the BA and PO evaluate business value, risk, and dependencies ensure the backlog reflects current priorities.
Question 3: A BA is asked to produce a 'release plan' for a 6-month Scrum project. Which approach best balances planning with Agile flexibility?
- Create a detailed fixed plan for all 6 months before any sprint begins
- Build a rolling wave plan with confident near-term detail and high-level projections for later (Correct answer)
- Refuse to plan beyond the current sprint
- Plan only based on the first sprint's velocity
Correct answer: Build a rolling wave plan with confident near-term detail and high-level projections for later
Rolling wave planning provides necessary near-term commitment while acknowledging that later details will emerge as the project progresses.
Question 4: Which Scrum artifact is the BA most likely to contribute to by writing user stories, acceptance criteria, and maintaining priority order?
- Sprint Burndown Chart
- Team Velocity Chart
- Product Backlog (Correct answer)
- Definition of Done
Correct answer: Product Backlog
The Product Backlog is the primary artifact where BAs contribute user stories, acceptance criteria, and collaborate on prioritization with the PO.
Question 5: A key stakeholder refuses to attend Sprint Reviews, saying they're 'too busy.' What risk does this create, and what should the BA do?
- No risk; Sprint Reviews are optional for stakeholders
- Risk of misaligned product direction; the BA should find alternate ways to gather this stakeholder's feedback (Correct answer)
- Risk that the sprint will be cancelled; escalate to the Scrum Master
- No action needed; the Product Owner covers this
Correct answer: Risk of misaligned product direction; the BA should find alternate ways to gather this stakeholder's feedback
Absent stakeholders risk undetected misalignment; BAs should proactively use demos, async reviews, or 1-on-1 sessions to close the feedback gap.
Question 6: When a BA uses the MoSCoW prioritization technique during backlog refinement, what does 'S' stand for?
- Strategic
- Should have (Correct answer)
- Scalable
- Standard
Correct answer: Should have
In MoSCoW, 'S' stands for 'Should have' — important requirements that are not critical but add significant value.
Question 7: At the end of a sprint, the Development Team completed all stories but the Product Owner rejects two items because they don't match the expected user experience. What does this indicate?
- The Definition of Done needs to include UX validation criteria (Correct answer)
- The sprint should be cancelled retroactively
- The developers made errors and must be penalized
- The PO rejected items outside their authority
Correct answer: The Definition of Done needs to include UX validation criteria
If UX standards weren't part of the Definition of Done or acceptance criteria, this gap should be addressed by updating the DoD to prevent recurrence.
Agile Business Analysis In Scrum Environment 5
A BA is helping a Scrum team that suffers from 'scope creep within stories' — developers keep adding features beyond the acceptance criteria.
What technique helps prevent this?