Many teams/companies underutilize the entrepreneurial spirit of Scrum and its concept where the Product Owner is a mini-CEO of the Product.
Why Many Scrum Teams Don't Go Beyond Demo The Sprint Review is a great tool for getting feedback, while the number of changes to the Product Backlog after the Sprint Review can be an important indicator of how healthy your Scrum is. Unfortunately, teams often forget about it. Scrum is based on iterative and incremental development principles, which means getting feedback and making continuous updates to the Product Backlog. Releasing Increment (can be done anytime during the Sprint) Here are some decisions that can be formally made:Īdding team(s) with an assumption that it will speed up the development The Product Owner makes a formal decision regarding financing the next Sprint during the Sprint Review. Each Sprint is an important risk mitigation tool and the Sprint Review is a decision point for the Product Owner.Įach Sprint can be the last one. Also, it is a place for reviewing budgets, timeline and capabilities. The Sprint Review is not just about product demonstration, it is an inspection of the completed Sprint, the Product Backlog and the marketplace. Inspecting Is Much More Than Just An Increment. Inspect: Sprint, Product Backlog, Increment, Marketplace, Budget, Timeline, Capabilities.Īdapt: Product Backlog, Release Plan. Here is a short summary of what we inspect and adapt during the Sprint Review. Sprint is one of the five official Scrum Events and is an opportunity for the Scrum Team to practice empiricism. Thus, the stakeholders get a shared understanding of the future work.Ī review of the budget, timeline, potential capabilities follows. The attendees collaborate on the Product Backlog Items, which can be completed during the next Sprint.
The Product Owner discusses the current state of the Product Backlog, marketplace changes, and forecasts the likely release dates. The Development Team demonstrates the "Done" functionality (Demo), answers the questions and discusses problems they met on their way. The Product Owner opens the meeting and tells the attendees what the Development Team completed during the current Sprint (what has been "Done" and “not Done”). The Scrum Team and stakeholders (users, other teams, managers, investors, sponsors, customers, etc.) One could say that we invite the whole world to the Sprint Review and this is absolutely true. The Sprint Review is much more than just a Demo. It is true that the Demonstration or Demo is an essential part of the Sprint Review, but it isn't the only one. Is it just a matter of terminology? From my point of view, the Sprint Review is the most underestimated Scrum Event, and for many companies, its potential is yet to be revealed. Many of those practicing Scrum mistakenly call the Sprint Review a Demo.
0 kommentar(er)
