Your agile team is three sprints into developing a mobile application. During the latest sprint review, stakeholders provide feedback that the user interface doesn't match their expectations, even though the implemented features match the acceptance criteria in the user stories. The Product Owner explains they wrote the acceptance criteria based on their understanding but didn't include UI specifications. The team is frustrated because they'll need to rework completed features. How should this situation be addressed going forward?

Question

Accepted Answer

The correct answer is C. The root cause is insufficient clarity before work begins and lack of stakeholder collaboration during development. Incorporating UI specifications into the Definition of Ready ensures stories are truly ready for development, while increasing stakeholder engagement during sprints enables early feedback before work is considered complete (ECO Process Task 4.2 on engaging stakeholders). This approach embraces agile principles of collaboration and early feedback. Option B is the main distractor because while creating mockups is valuable, having the team create detailed UI for all stories could slow down the process and may not be necessary for all work; instead, the Definition of Ready should specify when mockups are needed based on story complexity. Options A and D introduce more process overhead without addressing the fundamental collaboration issue, and option D simply delays the problem rather than preventing it.

PMP Practice Question: Process — Agile, Medium

More Process Questions