Sprint Review

Correct Answer: By illustrating the iterative nature of Scrum, showing how progress and feedback are cyclical with each Sprint. Offering to bring new stakeholders up to speed in a separate session.

The correct approach emphasizes the adaptive and iterative principles of Scrum, allowing for continuous feedback, learning, and adaptation. Incorporating new stakeholder feedback is vital, but it must be done within the structure of the Scrum framework, without compromising the current Sprint's goals or the Development Team's workflow. Option one is incorrect because it encourages unsustainable work habits that go against Scrum values. Option two disrupts the current Sprint and undermines the importance of adhering to Sprint goals. Option three is incorrect as it involves handling the situation in a non-collaborative and non-transparent manner, which could impact the open culture that Scrum encourages.

Correct Answer: Advocate for adhering to the Definition of Done and only include features that meet these criteria in the increment.

In Scrum, the increment must be in a usable condition and meet the Scrum Team's definition of 'Done' at the end of the Sprint, regardless of whether the Product Owner decides to release it. The ScrumMaster should guide the team to understand and follow this principle, ensuring that only fully developed features are included in the increment. This maintains quality and transparency. Other options might seem reasonable but could lead to technical debt, lower quality, or misunderstandings about the state of the product.

Correct Answer: The ScrumMaster should ensure that the Product Owner adds this bug to the Product Backlog to be addressed in future sprints.

In Scrum, when a bug is discovered during the Sprint Review, the best course of action is to document it in the Product Backlog to be addressed in future sprints. This is because the Scrum Team aims to deliver potentially shippable increments of product at the end of each Sprint. If an issue is found, it's logged for further study, prioritized and then rectified in the upcoming sprints based on its priority. This is what the first answer suggests. The other answers are incorrect because in Scrum, ignoring the bug is not acceptable - transparency is key in Agile practices. Insisting the team fix the bug immediately during the Sprint Review is also not right because this time is reserved for feedback and review, not for active problem-solving. Finally, blaming the team for presenting a faulty increment does not align with the values of Scrum, which emphasize shared responsibility, openness and collaboration.