🪴 (plotted plant) | Literature note |

Making Your Scrum Work #25



  • The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
  • Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog.

Problems for stakeholders with the Sprint Review

  • Waste of time: Your stakeholders do not feel seen, heard, or respected.
  • (This points to a failing relationship between stakeholders and the Product Owner or a flawed product discovery process.)

Potential consequences of skipping Sprint Reviews

  • diminishing level of trust between the stakeholders on the one side and the Scrum team on the other.
  • stakeholders might be tempted to exert more control over the development process by “tightening the leash,” for example, by demanding detailed reports to satisfy their information needs or setting arbitrary deadlines.

Some hints for stakeholder involvement

  • Also helpful is embracing radical transparency regarding what the Scrum team does and over-communication in every aspect. Also, please include them in the product discovery and Product Backlog management processes.
  • Shift & Share is an excellent Liberating Structure microstructure for that purpose.


Enjoy this post? Buy me a Coffee at ko-fi.com

Notes mentioning this note

There are no notes linking to this note.