A cross-functional agile team is developing a new customer portal. After the third sprint review, the product owner realizes that while the delivered features meet the acceptance criteria, the overall user experience is fragmented and doesn't align with the original product vision. Individual stories were completed successfully, but they don't work together cohesively. The team followed all agile ceremonies and the definition of done. What is the most likely root cause of this issue?

Question

Accepted Answer

The correct answer is B. Insufficient backlog refinement is the most likely root cause when individual stories meet acceptance criteria but don't create a cohesive product. Effective backlog refinement ensures stories are properly sized, understood, and aligned with the product vision and overall user experience. This includes considering how features work together, not just in isolation. The product owner is responsible for ensuring the backlog reflects the product vision through ongoing refinement activities. Option A is a plausible distractor but less likely because the issue isn't about technical integration—features work but lack cohesion in user experience. Integration testing would catch technical issues, not vision alignment problems. Option C doesn't fit because stakeholders seeing fragmented features at sprint reviews would have provided feedback earlier. Option D assumes a skills gap without evidence, when the actual problem is planning and vision alignment.

PMP Practice Question: Process — Agile, Medium

More Process Questions