Sprint Review

Correct Answer: Proceed with the Sprint Review, gathering feedback from stakeholders and the team, and ensure to communicate the outcomes to the Product Owner.

The Sprint Review's purpose is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Master should facilitate the event even in the Product Owner's absence, making sure that the feedback loop is not broken. The correct approach is to proceed with the meeting as scheduled, while ensuring the Product Owner is informed of the outcomes. Rescheduling might disrupt the rhythm of the team and stakeholders, omitting important discussions or making decisions without the Product Owner could lead to misalignment with the product vision.

Correct Answer: Encourage the Development Team to be transparent about the incomplete increment, pinpointing the learning opportunity for improvement during the Sprint Retrospective.

While it is crucial for the increment demonstrated at the Sprint Review to meet the 'done' criteria, it is equally important to foster an environment of transparency and continuous improvement. The correct action is to encourage openness about the work that is not 'done' and use it as a basis for learning and adaptation in the Sprint Retrospective. Extending the sprint duration goes against Scrum principles, as it undermines the concept of a fixed sprint length and can create unsustainable working habits. Adjusting Backlog priorities is a continuous activity and not directly related to addressing work that doesn't meet the 'done' criteria during the Sprint Review. While enhancing the rigor of daily Scrum meetings can be beneficial, it alone does not address the immediate issue of presenting an incomplete increment during the Sprint Review.

Correct Answer: Encourage a retrospective focused on improving alignment with business objectives for future sprints

The correct answer involves facilitating an environment for continuous improvement and reflection on aligning work with business objectives. Directly modifying the Product Backlog without consultation misses the collaborative aspect of Scrum. Halting development doesn't align with the iterative and incremental nature of Scrum, which emphasizes adapting over stopping. Lastly, while an immediate Sprint planning session for redesign might seem proactive, it could lead to inefficiencies and fatigue without ensuring genuine alignment and understanding, lacking the strategic review and adaptation component critical for realignment in the context of Scrum.