Agile Business Analysis Delivery Horizon and Feedback 4 — Questions and Answers
Question 1: A BA is working on a product with high uncertainty. Which delivery horizon approach is most appropriate?
- Plan all three horizons in equal detail before starting
- Keep Horizon 1 well-defined, Horizon 2 directional, and Horizon 3 visionary with minimal detail (Correct answer)
- Avoid horizon planning entirely and work from the daily backlog only
- Define Horizon 3 first since it sets the long-term vision
Correct answer: Keep Horizon 1 well-defined, Horizon 2 directional, and Horizon 3 visionary with minimal detail
Under uncertainty, Horizon 1 should be detailed for near-term delivery while later horizons remain intentionally less defined to allow for emerging information.
Question 2: Which of the following best describes the relationship between a Minimum Viable Product (MVP) and a delivery horizon?
- An MVP spans all three horizons equally
- An MVP is a delivery horizon artifact used to test a core hypothesis with minimal investment (Correct answer)
- An MVP replaces the sprint goal in Scrum
- An MVP is only relevant for startup products, not enterprise agile
Correct answer: An MVP is a delivery horizon artifact used to test a core hypothesis with minimal investment
An MVP is a focused delivery artifact designed to test a core business hypothesis with the minimum effort, fitting within a near-term delivery horizon.
Question 3: What role does a business analyst play during a sprint review?
- Approving or rejecting stories on behalf of the product owner
- Facilitating stakeholder feedback collection and ensuring insights are captured for backlog refinement (Correct answer)
- Writing test cases based on the demo results
- Presenting the burndown chart to senior management
Correct answer: Facilitating stakeholder feedback collection and ensuring insights are captured for backlog refinement
During sprint reviews, the BA helps facilitate the feedback conversation and ensures stakeholder insights are captured and translated into actionable backlog adjustments.
Question 4: A BA discovers that a key assumption built into the product roadmap is wrong based on user feedback. What is the correct agile response?
- Continue with the roadmap since it was approved by leadership
- Document the finding for the next annual planning cycle
- Immediately update the roadmap and backlog to reflect the validated learning (Correct answer)
- Remove the feedback from the sprint review notes to avoid scope changes
Correct answer: Immediately update the roadmap and backlog to reflect the validated learning
Agile principles require teams to respond to change over following a plan, so invalidated assumptions must immediately trigger backlog and roadmap updates.
Question 5: What distinguishes a 'release' from a 'sprint' in the context of delivery horizons?
- Releases always require stakeholder approval; sprints do not
- A sprint is a time-boxed development cycle, while a release is the deployment of a potentially shippable increment to users (Correct answer)
- Sprints are only for technical work; releases include business analysis
- Releases span multiple teams while sprints are single-team only
Correct answer: A sprint is a time-boxed development cycle, while a release is the deployment of a potentially shippable increment to users
A sprint is the team's time-boxed work cycle, while a release is the act of making a potentially shippable increment available to real users for feedback.
Question 6: How should a BA handle conflicting feedback from two different user segments after a release?
- Discard feedback from the smaller segment
- Ignore both sets of feedback until a third release clarifies the situation
- Analyze whether both segments are target users and surface the conflict to the product owner for prioritization (Correct answer)
- Implement both conflicting changes to satisfy everyone
Correct answer: Analyze whether both segments are target users and surface the conflict to the product owner for prioritization
Conflicting feedback is valuable data; the BA should analyze segment relevance and present the trade-off clearly to the product owner for an informed decision.
Question 7: Which agile event is most explicitly designed to gather structured feedback on the delivered increment?
- Sprint planning
- Daily standup
- Sprint retrospective
- Sprint review (Correct answer)
Correct answer: Sprint review
The sprint review is the formal agile event dedicated to inspecting the delivered increment and gathering stakeholder feedback to adapt the product backlog.
Agile Business Analysis Delivery Horizon and Feedback 4
A BA is working on a product with high uncertainty.
Which delivery horizon approach is most appropriate?