When preparing for the Sprint Review, it is the Product Owner’s responsibility to make sure that the right people are invited. This means that stakeholders should be identified and kept in the loop (McGreal & Jocham, 2018, p.95). If your team is shifting to a remote Sprint Review, this could be a good time to identify any potential stakeholders who don’t normally attend in person but could contribute valuable feedback.
While the Sprint Review is primarily intended as a collaborative event, it could still be beneficial to record the meeting. By doing so, your team can then make the recording available online for those in distant time zones or facing other irresolvable barriers to attendance. Of course, it’s a good idea to check with participants that they are happy to be caught on film before pressing record. This is especially true when involving external clients or users.
Similarly, given that schedule management can be tricky when adapting to remote work, I often find it useful to circulate a high-level description of the themes to be discussed in the Sprint Review, or even a copy of the sprint goal, in advance. By sharing this information ahead of time, your team can let stakeholders know whether this particular Sprint Review is relevant to them.
On a more practical note, investing in a high-quality headset can go a long way to improving sound quality in your Sprint Review. We have all experienced the agonizing frustration of participating in a remote meeting with loud background noises or ongoing audio feedback. Given that Sprint Reviews can be up to 4 hours long for month-long sprints, it is especially important to make sure that participants stand a chance of hearing you properly! More generally, testing your connection and any technologies to be used ahead of time can reduce the risk of irritating technical glitches.