Agile Business Analysis Delivery Horizon and Feedback 5 — Questions and Answers
Question 1: A team's stakeholders give positive feedback in sprint reviews, but post-release analytics show low adoption. What should the BA investigate first?
- Whether the sprint reviews are being held too frequently
- Whether sprint review participants represent actual end users or only proxy stakeholders (Correct answer)
- Whether the development team followed the acceptance criteria
- Whether the product owner is attending sprint reviews
Correct answer: Whether sprint review participants represent actual end users or only proxy stakeholders
A gap between stakeholder approval and actual adoption often indicates that sprint review participants are not representative of real end users.
Question 2: In rolling wave planning within agile BA, how is the delivery horizon typically managed?
- All work is planned in full detail at project inception
- Near-term work is planned in detail while future work remains at a higher level until more is known (Correct answer)
- Only the first sprint is planned; everything else is ad hoc
- Future horizons are planned by external consultants
Correct answer: Near-term work is planned in detail while future work remains at a higher level until more is known
Rolling wave planning elaborates near-term work in detail and intentionally keeps future work at a higher level, allowing detail to emerge as knowledge grows.
Question 3: What is the primary benefit of using story maps when planning delivery horizons?
- They replace the need for sprint reviews
- They provide a visual structure that links user activities to delivery increments across horizons (Correct answer)
- They eliminate the need for a product backlog
- They are used only for technical architecture planning
Correct answer: They provide a visual structure that links user activities to delivery increments across horizons
Story maps visually connect user journeys to delivery increments, making it easy to plan what to deliver in each horizon while maintaining a user-centric perspective.
Question 4: Which scenario best illustrates a 'fast feedback loop' in agile delivery?
- A team releases a new feature quarterly and reviews NPS scores annually
- A team deploys a feature flag to 5% of users and monitors behavior within 48 hours (Correct answer)
- A team collects requirements for 3 months before beginning development
- A team conducts a formal acceptance test six weeks after development completes
Correct answer: A team deploys a feature flag to 5% of users and monitors behavior within 48 hours
Using a feature flag to expose a feature to a small user segment and monitoring behavior within 48 hours is a classic fast feedback loop practice.
Question 5: A BA is facilitating a roadmap review. A stakeholder insists on locking Horizon 2 and 3 details. What is the best response?
- Agree and document all three horizons in full detail
- Explain that locking future horizons too early undermines the team's ability to respond to feedback from Horizon 1 delivery (Correct answer)
- Escalate the disagreement to the steering committee
- Remove Horizons 2 and 3 from the roadmap entirely
Correct answer: Explain that locking future horizons too early undermines the team's ability to respond to feedback from Horizon 1 delivery
Locking future horizon details prematurely removes the flexibility that agile delivery requires to incorporate feedback from earlier increments.
Question 6: What is 'lead time' in the context of agile delivery horizons, and why does it matter for feedback?
- The time from backlog item creation to when a user can actually use the feature in production (Correct answer)
- The number of items in the product backlog
- The duration of a single sprint
- The time required to write acceptance criteria for a story
Correct answer: The time from backlog item creation to when a user can actually use the feature in production
Lead time measures how long it takes for a backlog item to reach users; shorter lead times accelerate feedback loops and improve the team's ability to learn.
Question 7: How does the concept of a 'release train' in SAFe relate to managing delivery horizons?
- It replaces individual sprint cycles with one large delivery event per year
- It provides a predictable, time-boxed cadence (Program Increment) for synchronizing teams and delivering cross-team increments on a defined horizon (Correct answer)
- It is a metaphor for eliminating the product backlog
- It applies only to hardware product development
Correct answer: It provides a predictable, time-boxed cadence (Program Increment) for synchronizing teams and delivering cross-team increments on a defined horizon
SAFe's Agile Release Train synchronizes multiple teams on a Program Increment cadence, creating a predictable delivery horizon for coordinated feedback and planning.
Agile Business Analysis Delivery Horizon and Feedback 5
A team's stakeholders give positive feedback in sprint reviews, but post-release analytics show low adoption.
What should the BA investigate first?