Your agile team is developing a customer portal and has received feedback from the product owner that the last three increments did not meet customer expectations, despite meeting acceptance criteria. The team followed all documented requirements and the product owner approved each user story before development. Customers are frustrated that features don't solve their actual problems. What should the team do to prevent this in future sprints?

Question

Accepted Answer

The correct answer is B. Direct customer engagement during sprint execution enables early validation of assumptions, promotes incremental feedback, and ensures the team builds the right thing, not just builds things right (ECO Process Task 7.1 - Plan and manage project/phase closure and transitions). This collaborative approach aligns with agile values of customer collaboration over contract negotiation and responding to change. Option A is the main distractor because while detailed acceptance criteria seem helpful, the problem isn't clarity of written requirements but rather a disconnect between documented needs and actual customer problems. More documentation doesn't solve misalignment; direct conversation and feedback loops do. Options C and D apply predictive thinking that doesn't address the root cause of misunderstood customer needs.

PMP Practice Question: Process — Agile, Medium

More Process Questions