Sprint Review or more well know as Demo are one of the most critical meeting in Scrum. Why? Because this is the time to get the real feedback for our Product Owner, stakeholders and sponsors of the project (most of the time you have to be lucky if one of the sponsor attend the demo).
What happens if we miss several Demos?
Sprint Review or demo is mandatory to collect the comments about the product released by the team after the end of the iteration so every Scrum team has to do this meeting without excuses.
Once I worked with an Scrum team that was reluctant to do the Sprint Review or Demo. Considering the team was new following Scrum practices I prefer to let them missed a couple of demos. Then into the Retrospective I strongly recommended them to do one demo with the Product Owner and many stakeholders that were visiting our offices. During the demo several stakeholders demands to improve the look and field of the website and skip some steps of a wizard that was released.
In addition, one of the sponsor of the project told me that he wants to attend the next demo in order to avoid the waste of time of updating the software each month.
Furthermore, the Product Owner who missed the last demo but validated the product released admitted his fault on not invested more time and effort to do a double check.
The role of Product Owner is crucial on each Agile project so if your company has a Product Owner for several projects or he has more duties that avoid him to stay fully focused on his role it is time to consider to get another Product Owner.
To sum it up, if the Product Owner can’t work full time and coordinate with the vision of the client you will face many issues as soon as the stakeholders participated in one demo or even worse when the Scrum team would release the software. As an Agile Coach encourage the Scrum Master to motivate the Scrum team to do each ceremony because all of them are necessary.