Agile Business Analysis Delivery Horizon Activities 3 — Questions and Answers
Question 1: During the Delivery Horizon, the BA facilitates a sprint retrospective discussion about requirement misunderstandings. What is the MOST productive outcome?
- Identifying team members responsible for the misunderstandings
- Agreeing on process improvements to how stories are elaborated and accepted going forward (Correct answer)
- Documenting the misunderstandings in a formal lessons-learned report for the PMO
- Reducing the number of user stories accepted each sprint
Correct answer: Agreeing on process improvements to how stories are elaborated and accepted going forward
Retrospectives should produce actionable process improvements that prevent the same elaboration gaps from recurring.
Question 2: A BA is working in a Delivery Horizon where the team practices continuous deployment. Which activity becomes ESPECIALLY critical for the BA?
- Creating detailed project schedules with fixed milestones
- Ensuring acceptance criteria are precise enough to support automated acceptance testing (Correct answer)
- Obtaining written sign-off from stakeholders before each deployment
- Maintaining a separate requirements repository outside the team's tools
Correct answer: Ensuring acceptance criteria are precise enough to support automated acceptance testing
Precise acceptance criteria enable automated tests that gate continuous deployments, making them both feasible and safe.
Question 3: Which of the following BEST represents a BA's contribution during a sprint review in the Delivery Horizon?
- Presenting sprint velocity charts to the executive sponsor
- Facilitating stakeholder feedback on demonstrated increments and capturing actionable backlog updates (Correct answer)
- Approving team timesheets for the completed sprint
- Presenting a status report comparing planned vs. actual scope
Correct answer: Facilitating stakeholder feedback on demonstrated increments and capturing actionable backlog updates
The BA's sprint review role centers on eliciting stakeholder feedback and translating it into refined backlog items for future sprints.
Question 4: An Agile BA discovers that a third-party API the team is integrating with behaves differently than its documentation states. This is BEST handled by:
- Updating the user story to remove the API dependency entirely
- Collaborating with the developer and product owner to adjust acceptance criteria or spike a solution (Correct answer)
- Logging the issue and continuing without changing the story
- Escalating to the vendor and pausing all related development
Correct answer: Collaborating with the developer and product owner to adjust acceptance criteria or spike a solution
A collaborative adjustment to the story or a time-boxed spike resolves the uncertainty quickly without halting delivery unnecessarily.
Question 5: During the Delivery Horizon, the product owner is frequently unavailable. What is the BEST Agile BA response?
- Make all product decisions independently to keep the team moving
- Work with the product owner to pre-clarify anticipated questions and establish escalation paths (Correct answer)
- Pause the sprint until the product owner is available
- Assign product owner responsibilities to the scrum master
Correct answer: Work with the product owner to pre-clarify anticipated questions and establish escalation paths
Proactive pre-clarification and clear escalation paths reduce the team's dependency on real-time product owner availability.
Question 6: What does 'thin slicing' mean in the context of Delivery Horizon story preparation by the BA?
- Reducing story points to fit more work into a sprint
- Breaking large features into the smallest vertical slices that deliver end-to-end value independently (Correct answer)
- Removing non-functional requirements to speed delivery
- Assigning stories to only the most experienced developers
Correct answer: Breaking large features into the smallest vertical slices that deliver end-to-end value independently
Thin vertical slices let the team deliver and validate real value frequently, reducing batch size and integration risk.
Question 7: A BA notices that done stories are not being released to users despite being accepted. Which Delivery Horizon concern does this MOST directly surface?
- Insufficient sprint velocity
- A disconnect between the team's Definition of Done and the organization's release process (Correct answer)
- Poor acceptance criteria quality
- Overloaded product backlog
Correct answer: A disconnect between the team's Definition of Done and the organization's release process
When accepted work doesn't flow to users, the DoD and release pipeline are misaligned, preventing real business value realization.
During the Delivery Horizon, the BA facilitates a sprint retrospective discussion about requirement misunderstandings.
What is the MOST productive outcome?