Professional Scrum Master I (PSM I)Scrum FrameworkMedium

A Scrum Team is consistently delivering Increments that meet their Definition of Done, but stakeholders are frequently surprised by the functionality presented at the Sprint Review, sometimes leading to rework. What is the most likely cause of this issue?

  1. AThe Product Owner is not adequately engaging with stakeholders and transparently communicating Product Backlog status.
  2. BThe Scrum Master is not effectively shielding the Developers from external interruptions.
  3. CThe Developers are not skilled enough to anticipate stakeholder needs.
  4. DThe Definition of Done is too lax and does not ensure sufficient quality.
Show answer & explanation

Correct answer: A. The Product Owner is not adequately engaging with stakeholders and transparently communicating Product Backlog status.

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team, which includes effective Product Backlog management and engaging with stakeholders. If stakeholders are surprised, it indicates a lack of transparency or insufficient communication regarding what is being built and why.

Why the other options are wrong

  • B. While a Scrum Master shields, stakeholder surprise usually points to Product Backlog transparency, not just interruptions.
  • C. This is a generalization and doesn't directly address the communication and transparency aspect of Scrum, especially concerning stakeholder engagement.
  • D. The problem states the Increment meets the Definition of Done, implying quality is not the primary issue, but rather alignment with stakeholder expectations.

Product Owner Accountability

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.

  • Accountable for Product Backlog management.
  • Clearly expressing Product Backlog Items.
  • Ordering Product Backlog Items to best achieve goals and missions.
  • Ensuring the Product Backlog is transparent, visible, and understood by all.

Memory trick: Surprise stakeholders mean the Product Owner isn't singing loud enough.

More Scrum Framework questions