Developer Behavior: Sprint Review

Developers: Are you secretly sabotaging your own Sprint Review?

How can you 💪help💪 or 💥hurt💥 the Sprint Review?

The goal of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. I like to think of it as the Scrum Team and stakeholders discussing why their work is valuable, and how to keep it that way!

Hurts:

💥 Presenting work, WIP or even code. Focus on finding out what's important to the stakeholders instead. 💥 Disrespect other Team members or Stakeholders by saying things like: "That'll never work", "You're wrong" or "You don't understand". Ask clarifying questions instead. Be the expert! 💥 Shirking Ownership: blame others for issues, leave the review to the Product Owner, ignoring stakeholder altogether. Focus on what you can do, and ask for support instead.

Helps:

💪 Have working product, so your stakeholders can experience what has been achieved, then gather feedback and look forward together. 💪 Show up prepared as a Team, get involved in the discussion to build a common understanding of what is desired as well as possible.
💪 Ask for help! The perfect opportunity to if you can connect your challenges with customer outcomes!