PMI-ACP · Question #666
During a review session, an agile team presented done requirements to a group of stakeholders. Stakeholder feedback indicated that the done requirements failed to meet the most pressing needs and…
The correct answer is A. Reprioritized requirements prior to committing to iteration work. The root cause of this problem is that the team built the wrong things - items that were not the most pressing or valuable. The fix is to reprioritize the backlog before committing to iteration work, ensuring that the highest-value items are always at the top. This is a core…
Question
During a review session, an agile team presented done requirements to a group of stakeholders. Stakeholder feedback indicated that the done requirements failed to meet the most pressing needs and provide value. What should the team have done to prevent this?
Options
- AReprioritized requirements prior to committing to iteration work
- BEnsured that requirements remained stable during the iteration cycle
- CHad stakeholders focus on items created after the product backlog was initially built
- DWorked on features rather than a set of components
How the community answered
(34 responses)- A71% (24)
- B3% (1)
- C18% (6)
- D9% (3)
Explanation
The root cause of this problem is that the team built the wrong things - items that were not the most pressing or valuable. The fix is to reprioritize the backlog before committing to iteration work, ensuring that the highest-value items are always at the top. This is a core product owner responsibility and a fundamental agile principle: always work on the most valuable items first. Option B (stable requirements) contradicts agile's embrace of change. Option C (focusing on newer items) is arbitrary and could still miss the highest-priority work. Option D (features vs. components) addresses technical decomposition, not value prioritization.
Topics
Community Discussion
No community discussion yet for this question.