Delivery Horizon and Feedback Flashcards

An Agile team is holding a Sprint Review to demonstrate a working increment of their product. A stakeholder comments that while a feature was built exactly according to the user story's acceptance criteria, it doesn't solve the underlying business problem effectively. This feedback is PRIMARILY a validation of what?

Answer: The alignment between the delivered solution and the actual business need.

The Sprint Review's core purpose is to inspect the product increment and adapt the product backlog. [15, 17] This type of feedback is crucial because it reveals a gap between what was requested (the user story) and what was truly needed (the business value). It validates whether the team is building the *right thing*, not just building the *thing right*. [7]

Which of the following activities is MOST characteristic of the work a Business Analyst performs within the Delivery Horizon?

Answer: Collaborating daily with developers to clarify acceptance criteria for a user story in the current sprint.

The Delivery Horizon focuses on the immediate, short-term work of building the solution. [10, 20] Daily collaboration with the development team to ensure a shared understanding of requirements for the current sprint's work is a key activity at this level of detail. [1, 11] The other options are activities that take place at the Strategy or Initiative Horizons. [8]

A team's velocity is consistent, but during Sprint Reviews, stakeholders frequently express surprise at how features were implemented. To address this, the Business Analyst should focus on improving which feedback mechanism?

Answer: Continuous and informal feedback loops with stakeholders *during* the sprint.

Waiting for the Sprint Review to get feedback means that a whole sprint's worth of effort might be misaligned. Agile emphasizes continuous feedback to prevent this. [18] By facilitating more frequent, informal check-ins with stakeholders during development, the Business Analyst can ensure alignment and shared understanding, preventing surprises at the formal review. [16]

What is the primary purpose of a Sprint Retrospective from a business analysis perspective?

Answer: To inspect and adapt the team's processes, collaboration, and communication to improve future performance.

The Sprint Retrospective is a formal opportunity for the team to reflect on its own working processes. [21, 22] From a BA perspective, this is a key feedback loop for improving how requirements are communicated, how collaboration happens, and how the team can become more effective and efficient in delivering value in subsequent sprints. [19] The other options describe the Sprint Review or backlog refinement.

During sprint planning, the development team is unsure how to approach a specific user story due to ambiguity in the requirements. What is the MOST effective action for the Business Analyst to take at this moment?

Answer: Facilitate a quick discussion, using examples and clarifying acceptance criteria to create a shared understanding.

The Business Analyst's role in the Delivery Horizon, especially during sprint planning, is to ensure user stories are 'ready' and clearly understood. [2, 5] When ambiguity arises, the BA's primary function is to facilitate communication and clarify the requirements in real-time, often using examples, so the team can confidently accept the work into the sprint. [3, 12]

Which statement BEST describes the relationship between the Delivery Horizon and Agile feedback loops?

Answer: The Delivery Horizon is characterized by the shortest and most frequent feedback loops to continuously validate and adapt the work.

The Delivery Horizon operates on very short cycles (sprints), which inherently rely on rapid and frequent feedback loops like daily stand-ups, stakeholder demos, and team retrospectives. [9] This continuous feedback is essential for an Agile team to inspect its work and adapt its plan quickly, ensuring alignment with customer needs and reducing waste. [14, 16]