Why you should never call the sprint review the sprint demo?
It might seem like semantics, but calling the meeting a Sprint Demo puts everyone who attends the Sprint Review in the wrong state of mind. In the Sprint Review you demo the latest increment to get feedback from the whole Scrum Team and key stakeholders.
When should you do a sprint review?
The general rule of thumb is to allow one hour for sprint review every one week of sprint length. That means teams should timebox sprint review to two hours for a two-week sprint and four hours for a one-month sprint.
What is the main purpose of a sprint demo review?
As described in the Scrum Guide, the purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
What a sprint review is not?
Signs of An Unhealthy Sprint Review The Development Team isn’t (fully) present. Neither are stakeholders and/or end users. The demonstrated functionality does not meet the Definition of “Done”. The Product Backlog is not updated.
Who is responsible for sprint review?
Participants in the sprint review typically include the product owner, the Scrum team, the ScrumMaster, management, customers and developers from other projects. During the sprint review, the project is assessed against the sprint goal determined during the sprint planning meeting.
Who are the attendees of the sprint review?
The Scrum Guide states that the attendees of the Sprint Review are the Scrum Team (Product Owner, Scrum Master, and Development Team) and “key stakeholders invited by the Product Owner”. I can definitely see advantages in having some external (to the Scrum Team, not necessarily to the organization) stakeholders present.
What should be the sprint goal in scrum?
Scrum Teams ensure they have a meaningful Sprint goal, not a Generic goal. For example, “policy renewal for individual policyholders” for an insurance product rather than saying, the goal is “complete all Product Backlog Items selected during the Sprint.” The team has random Product Backlog Items, so struggle to craft a sprint goal.
Is there acceptance of increment during Sprint review?
During the Sprint Review event, there is no “acceptance” of the Increment as it is already Done. There is discussion regarding the completed work (Increment) and what might be done next.
What do you need to know about sprint planning?
During the Sprint Planning, the Product Owner presents business objectives for the Sprint and an ordered Product Backlog. The Scrum Team discusses what can be done based on the Definition of Done and crafts the Sprint Goal and forecasts their work. Scrum Teams ensure they have a meaningful Sprint goal, not a Generic goal.