Scrum is intended as a simple, yet sufficient framework for complex product delivery. Scrum is not a one-size-fits-all solution, a silver bullet or a complete methodology. Instead, Scrum provides the minimal boundaries within which teams can self-organize to solve a complex problem using an empirical approach. This simplicity is its greatest strength, but also the source of many misinterpretations and myths surrounding Scrum. In this series of posts we — your ‘mythbusters’ Christiaan Verwijs & Barry Overeem — will address the most common myths and misunderstandings. PS: The great visuals are by Thea Schukken. Check out the previous episodes here (1, 2, 3, 4 , 5, 6, 7, 8, 9, 10 and 11).
Sigh. It is that time of the Sprint again; the Sprint Review. The Development Team is setting up up shop in one of the meeting rooms. While Jim connects his laptop to a beamer, Susan nervously re-arranges the notes of the work the team completed this Sprint. “Shall I demonstrate the new shopping basket?” she asks senior developer John with a hint of uncertainty in her voice. John nods, and - after a pause - adds “Sure. I’ll show the new order review page then”. As the clock hits eleven, the stakeholders start dropping in and awkwardly find spots around the huge table. Mary, the Product Owner, arrives and settles in one of the more comfortable chairs at the head of the table. She turns towards the Development Team and signals the start of the Sprint Review; “Take it away guys”. Forty minutes later, the Development Team has gone through their list of completed items and demonstrated everything worth showing. As the demonstration wraps up, the audience offers a mild applause to the Development Team. As the stakeholders are leaving the room, the Development Team sighs in relief. “Well, that was a great Sprint Review!”, Mary concludes.
In this post, we address the myth that the Sprint Review is primarily an opportunity to ‘demo’ the increment to stakeholders.
This post is for you if you recognize one or more of these telltale signs:
By treating the Sprint Review primarily as a demo, the purpose of this crucial opportunity for inspection and adaptation is lost. Too many Scrum Teams approach the Sprint Review as their moment to show progress, to give a ‘product update’, to sell what was built to stakeholders or to talk about what they did.
“Too many Scrum Teams approach the Sprint Review as their moment to show progress, to give a ‘product update’, to sell what was built to stakeholders or to talk about what *they* did.“
The Scrum Guide describes the Sprint Review as an event that “is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed”. It emphasizes that during the Sprint Review, “the Scrum Team and stakeholders collaborate about what was done in the Sprint. Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value”.
“Collaboration between the Scrum Team and its stakeholders is key during the Sprint Review”
In other words, the collaboration between the Scrum Team and its stakeholders is key during the Sprint Review. In Scrum, we understand that product development is a complex activity. As we do the work, both the problem we’re trying to solve and the optimal solution will emerge from what we learn during development. The Sprint Review is a critical opportunity in Scrum to make this possible by letting insights emerge from the work that was done and to build on them to inform the next steps.
The Sprint Review is about making the state of the product (Increment) and the Product Backlog transparent. The Scrum Team and stakeholders then inspect both and share insights on what was learned from that inspection. Together with current market conditions, organizational changes, budget, and timeline, they decide together on next steps. The output of the Sprint Review consists of adjustments to the Product Backlog based on what was learned. In a sense, the Sprint Review is about answering the question: “Based on what we learned this Sprint, what are the next steps?”. This provides valuable input for the Sprint Planning.
Optimally, the Sprint Review has the following characteristics:
In this blog post, we busted the myth that the Sprint Review is about demo-ing the Increment to stakeholders. Although a demo certainly can be part of a Sprint Review, it fails to capture what the Sprint Review is actually about: a collaboration between the Scrum Team and stakeholders to inspect the increment and progress to date and decide on the most valuable next steps.
What do you think about this myth? Do you recognize the Sprint Review being only a demo? What are your lessons learned?
Want to separate Scrum from the myths? Join our Professional Scrum Master or Scrum Master Advanced courses (in Dutch or English). We guarantee a unique, eye-opening experience that is 100% free of PowerPoint, highly interactive and serious-but-fun. Check out our public courses (Dutch) or contact us for in-house or English courses. Check out the previous episodes here (1, 2, 3, 4 , 5, 6, 7, 8, 9, 10 and 11).