A Scrum Team has been consistently delivering 'Done' Increments every Sprint, yet the stakeholders are increasingly expressing dissatisfaction, stating that the product is not evolving fast enough to meet critical business needs. The Product Owner is diligent in ordering the Product Backlog based on perceived value. What is the MOST likely underlying cause of the stakeholder dissatisfaction?
- AThe Product Backlog is not being frequently refined with stakeholders' evolving needs.
- BThe Definition of Done is too lax and allows low-quality work to be accepted.
- CThe Product Owner is not effectively communicating the product vision to stakeholders.
- DThe Developers are not working efficiently enough to deliver more Product Backlog Items.
Show answer & explanationAnswer & explanation
Correct answer: A. The Product Backlog is not being frequently refined with stakeholders' evolving needs.
Even with a 'Done' Increment, if the Product Backlog isn't frequently refined with evolving stakeholder needs, the 'perceived value' by the Product Owner might diverge from the actual 'critical business needs' as understood by stakeholders. Product Backlog refinement is a continuous process involving collaboration to ensure the backlog reflects the latest understanding of value.
Why the other options are wrong
- B. The question states 'consistently delivering 'Done' Increments,' implying the Definition of Done is being met, so quality is unlikely the issue.
- C. While communication is always important, the issue points to the *content* of the backlog not aligning with needs, not just the vision's communication.
- D. The team is 'consistently delivering 'Done' Increments,' implying a stable pace. The problem is about *what* is being delivered, not the quantity.
Product Backlog Refinement Purpose
Product Backlog Refinement is the ongoing process of adding detail, estimates, and order to Product Backlog Items. It's a collaborative activity involving the Product Owner and Developers to ensure the Product Backlog is understood, transparent, and aligned with current market needs.
- Ongoing activity, not an event.
- Collaborative between PO and Developers.
- Ensures Product Backlog is ready for future Sprints.
Memory trick: Aligning Value Needs Constant Co-creation.