Agile Business Analysis FREE Agile Business Analysis Delivery Horizon and Feedback Questions and Answers 2 — Questions and Answers
Question 1: In an agile context, what is the primary purpose of defining a delivery horizon?
- To set a fixed deadline that cannot change
- To establish a timeframe for planning and delivering increments of value (Correct answer)
- To determine the total project budget
- To assign team members to specific tasks
Correct answer: To establish a timeframe for planning and delivering increments of value
A delivery horizon establishes the timeframe within which the team plans and delivers increments of business value, enabling iterative progress.
Question 2: Which feedback mechanism is MOST effective for validating that a delivered increment meets stakeholder expectations?
- Sending a status report via email
- Conducting a sprint review with a live demonstration (Correct answer)
- Updating the project charter
- Filing a change request form
Correct answer: Conducting a sprint review with a live demonstration
Sprint reviews with live demonstrations allow stakeholders to interact with working software and provide immediate, actionable feedback.
Question 3: How should a business analyst handle conflicting feedback from multiple stakeholders during an iteration review?
- Ignore feedback from lower-ranking stakeholders
- Escalate all conflicts to the project sponsor immediately
- Facilitate a discussion to understand priorities and align on the highest-value outcome (Correct answer)
- Implement all feedback regardless of conflicts
Correct answer: Facilitate a discussion to understand priorities and align on the highest-value outcome
The business analyst should facilitate collaborative discussion to surface priorities and help stakeholders align on the most valuable path forward.
Question 4: What distinguishes a near-term delivery horizon from a long-term delivery horizon in agile planning?
- Near-term has detailed plans with high confidence; long-term has broader goals with less certainty (Correct answer)
- Near-term focuses on strategic vision; long-term focuses on tactical execution
- Near-term requires formal approval; long-term does not
- There is no meaningful distinction between the two
Correct answer: Near-term has detailed plans with high confidence; long-term has broader goals with less certainty
Near-term horizons contain detailed, high-confidence plans while long-term horizons outline broader goals acknowledged to have greater uncertainty.
Question 5: Why is continuous feedback considered essential to managing delivery horizons effectively?
- It ensures documentation is always up to date
- It allows the team to adjust scope and priorities based on evolving understanding (Correct answer)
- It satisfies audit and compliance requirements
- It reduces the need for stakeholder involvement
Correct answer: It allows the team to adjust scope and priorities based on evolving understanding
Continuous feedback enables the team to adapt scope and priorities as new information emerges, keeping delivery aligned with actual business needs.
Question 6: A team consistently receives feedback too late in the iteration to act on it. What should the business analyst recommend?
- Extend the iteration length to allow more time
- Introduce earlier and more frequent feedback touchpoints within the iteration (Correct answer)
- Remove the feedback step to save time
- Wait until the next release to address feedback
Correct answer: Introduce earlier and more frequent feedback touchpoints within the iteration
Introducing earlier and more frequent feedback touchpoints ensures the team can incorporate insights while there is still time to respond within the iteration.
Agile Business Analysis FREE Agile Business Analysis Delivery Horizon and Feedback Questions and Answers 2
In an agile context, what is the primary purpose of defining a delivery horizon?