Is it time to cancel the sprint review meeting?

The Sprint Review Conference has long been an important part of scrum, a mechanism for the team to get feedback on the product increments that are delivered by the iteration. At the Sprint review meeting, the product owner determines the priority of the next sprint's requirements based on the feedback received.

So, is the sprint review now obsolete?

Ten years ago, almost every scrum team was delivered in a model like sprint,sprint,sprint,release, each with several iterations on the line, in extreme cases where every iteration was on the line and rarely heard in the middle of a Sprint.

Now, many teams are practicing continuous delivery and continuous release, and it's common to release them many times a day.

Let's imagine that for a continuous release team, we're going to do the sprint review scenario in the original way:

If they publish multiple times a day, they let the product owner and stakeholders give some feedback at the end of the iteration about the features they have delivered to the real user, and the stakeholders say, "Well, what do our users think of these features?" ”。 If the team publishes the product backlog entry after the middle of the iteration, the standard Sprint review meeting reviews the features that have been published and that the user has already used, and the actual value of the review meeting is small.

I coached some teams to conduct a feature review. The specific pattern is that one or two members of the team touch with the stakeholder who asked for it, and if necessary, they can call the PO, and they demonstrate this feature to the stakeholders, gather the stakeholder feedback on the feature, and then decide whether to publish the feature or make the necessary adjustments. Unlike the standard Sprint review, which was originally a review of a large number of product backlog entries, it is now a team of teams that have done multiple rounds of an instant review of a feature in the middle of the iteration as needed.

However, even in this case, the traditional sprint review at the end of the iteration is still valuable. The main purpose of the jury is to get feedback, but it also has an added value, and the stakeholders are fully involved to better learn and understand the product. A team that carries out a feature review can also consider a formal sprint review, which is a great way for all stakeholders to learn and understand what Sprint is publishing.

Not all teams are suitable for one feature review at a time, for example, if your team delivers physical products released once a year, the review of a traditional-style sprint is still the best choice. If your team most of the time is an iteration release, consider converting to a single feature to better achieve agile success.

Translator:
Eric Liao Liao Jingbin, a nationally renowned agile coach, consultant, trainer

Original
Mike Cohn

This article turns from: Leangoo Agile Development Tools (www.leangoo.com)

Original link: https://www.leangoo.com/11843.html

Is it time to cancel the sprint review meeting?