#ef7e12

Simple Ways to Increase Efficiency in Sprint Review

Feral Sunar // Allianz Türkiye - Agile Coach

It is possible for us to get much greater efficiency from sprint reviews as a team and even as a company. And there are ways to do this as simple as turning on the camera or sending a message to our colleague. Let's review our habits in sprint reviews.

The last day of the sprint cycle... Even if we do not count the retrospective ritual, which we evaluate the process and which is often conducted under the moderation of an agile coach, the last ritual that closes the sprint under the moderation of the team... Yes, we are talking about “sprint review”.

In its simplest definition, the meeting where the team presents the sprint output, evaluates the output together with the stakeholders, gathers feedback, monitors the progress and then updates the backlog.

If you remember (and if you are one of our careful readers), I mentioned earlier the five most common mistakes that we see in the daily rituals. Now, I would like to talk about some inefficient habits that I frequently encounter in sprint reviews. 

 

The 4 most common mistakes in sprint review rituals or let us say how to make a bad sprint review in 4 items? 
😊

  • The Product Owner (PO) being the sole owner of Sprint: Outputs are only transmitted by the PO and not prepared as a team
  • Limitation to a single presentation: Explaining the output instead of showing it, not getting feedback
  • Executing as a kind of “Sprint Accounting”: Status reporting of each step as if making a record in the accounting process, and also presenting incomplete or unrelated work with stakeholders
  • Passive or non-participating stakeholders: Stakeholders do not participate in the ritual or remain passive even if they do. 

 

In order to avoid these behaviors as much as possible, we talk about how we can do a better “sprint review” in the agile teams I work with, in retrospectives and in one-on-one meetings. Below are a few items that can raise awareness that I have compiled from these conversations; let's see together... 

 

What can we do for a better sprint review? 

  •  “Sprint review” is a unique “demonstration” opportunity for the agile team to show the value produced during the sprint, to receive feedback for consideration in the next iterations, and to express our gratitude to our stakeholders who contributed. So, like any "show", rehearsing this as a whole team a reasonable time in advance can make our job easier in many ways. 

For example, in case the team member who will make the presentation cannot attend due to compulsory reasons, it is a good idea to have the backup person ready, to prepare beforehand for questions from stakeholders, to remove or add some parts by looking at the whole.

  • When we say a presentation, it will be a contribution that makes a difference and increases interest, without thinking of it as just sharing a presentation image, and coming up with a more catchy content by having a demo of the product, even if it is small. 

 

  • Since it is a ritual in which the outputs of what has been done during the sprint are conveyed to the stakeholders and their feedback is received, their participation is as critical as the correct and complete selection of the stakeholders. Even if there is a recurring meeting, before each review, leaving the "autopilot" to review the participants, reminding some participants in person can also increase participation.

 

  • Speaking of stakeholder involvement, when we consider the roles in agile teams, the participation of roles such as Tribe Leader, Business Owner, and Change Owner in rituals is also valuable, apart from Product Owner and Chapter Lead roles. A little reminder needs to be made here. Making the presentation seem like it was made to these leaders is also an “anti-pattern” that should be avoided. 

 

  • I have witnessed many times that the interaction increased in the reviews where the names of the stakeholders were mentioned instead of the general expressions such as “business unit, IT team” when talking about a thank you for an endless test or project. 

 

  • Considering that our rituals have shifted to the virtual environment after the pandemic, we should act as you feel comfortable, of course, but we also observe that the fact that the camera of the team member who conveyed the presentation was on at that time attracted the attention and attention of the participants, which made communication more fluent 😊

 

  • Another factor that increases participation can be to give a word to our stakeholders and involve them with questions.

 

  • Agile team members' regular participation in other agile team reviews makes a difference here as well as in every other subject. Recognizing the areas that are especially well done or open to improvement and evaluating them in the teams' own reviews is one of the habits that can take us all one step further.

Is there an anti-pattern or good practice that you noticed? Do not forget to share your experiences with us… 

 

P.S. You can contact us by clicking here to share your experiences and ask questions about the agile working method.
 

Comments

Image CAPTCHA
Enter the characters shown in the image.