Business Scrum Meeting

The Scrum Master should explain that changes can't be made mid-sprint and suggest reconsideration for the next sprint. This is because one tenet of scrum is maintaining a stable sprint backlog for the duration of the sprint. Major changes to the sprint backlog in the middle of the sprint would disrupt the work already in progress and violate this tenet. Altering the priority item in the middle of the sprint may demoralize team members, violate project scope, and impact overall productivity. This is why other answers are not the right course of action: Accepting the change immediately promotes bad practice and may jeopardize the team's ability to deliver on their commitment. Ignoring the request harms communication transparency which is unhealthy for project progression. Arguing is unprofessional and does not foster collaborative dynamics.

In Scrum, the Sprint Review is a meeting designed to inspect the increment and adapt the Product Backlog if needed. It is about what was done during the Sprint. Therefore, the correct approach is to demonstrate the work actually completed, omitting the unfinished feature. Demonstrating unfinished work or focusing on what wasn't completed violates Scrum principles centered around transparency and review of done work. Postponing the Sprint Review until the feature can be completed is not advisable as it would disrupt the regular cadence and rhythms established by Scrum, which values inspecting and adapting at the end of every Sprint. Including an overview of the unfinished feature's projected completion or focusing the Sprint Review on planned features for the next sprint diverts attention from the primary goal of the Sprint Review, which is to inspect the increment and adapt based on what was actually accomplished.

In a case where the Product Owner is absent in a business scrum meeting, the Scrum Master should proceed with the meeting and make certain to inform the Product Owner about the discussions and decisions made during the meeting afterwards. This makes sure that the Scrum team continues with their tasks without delay, and the Product Owner stays in the loop despite their absence. Cancelling the meeting immediately may lead to delays and slow down the progress. Rescheduling the meeting might not be the best option, especially if this causes more disruption and delay in the work. Lastly, the Scrum Master should not take over the Product Owner's role during the meeting as these two roles have distinct responsibilities and conflating them may lead to confusion and conflict.