15 Sprint Review Anti-Patterns
via Scrum.org Blog by Stefan Wolpers
TL; DR: 15 Sprint Review Anti-Patterns
Are we still on the right track? Answering this question in a collaborative effort of the Scrum Team as well as internal (and external) stakeholders is the purpose of the Sprint Review. Given its importance, it is worthwhile to tackle the most common Sprint Review anti-patterns.
The Purpose of Scrum’s Sprint Review
The Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog. The Development Team, the Product Owner, and the stakeholders need to figure out whether they are still on track delivering value to customers. It is the best moment to create or reaffirm the shared understanding among all participants whether the Product Backlog is still reflecting the best use of the Scrum Team’s resources, thus maximizing the value delivered to customers. It is also because of this context that calling the Sprint Review a “sprint demo” does not match its importance for the effectiveness of the Scrum Team.
The Sprint Review is thus an excellent opportunity to talk about the general progress of the product. The Sprint Review’s importance is also the reason to address Sprint Review anti-patterns as a Scrum Master as soon as possible.
15 Sprint Review Anti-Patterns Holding Back Scrum Teams first appeared on Age-of-Product.com.