Scrum Framework Fundamentals

Correct Answer: Suggest discussing the specifics of the issue in a focused session right after the Daily Scrum with only the relevant team members.

The correct response facilitates effective use of the Daily Scrum time and respects its purpose as a planning meeting for the day, not as a problem-solving or issue discussion forum. Suggesting a focused session afterwards allows the team to maintain the flow of their Daily Scrum and ensures those concerned can dive deeper into the issue without taking time away from others. The wrong answers either misinterpret the purpose of the Daily Scrum (wrong_answer_1 and wrong_answer_3) or bypass the autonomy and responsibility of the Scrum Team (wrong_answer_2).

Correct Answer: Consult with the Product Owner to reassess the Sprint Backlog and prioritize tasks, including possible mitigation or resolution of the technical debt.

The correct course of action involves collaboration between the Scrum Team members, particularly the Scrum Master facilitating a dialogue with the Product Owner to assess and adjust the Sprint Backlog as necessary. This maintains the empirical process control core of Scrum, allowing for inspection and adaptation. Increasing team hours is not sustainable and does not address the root cause or strategic handling of work. Bringing in an external consultant without reassessing priorities can disrupt team dynamics and sprint goals. Holding a Sprint Retrospective before the end of the Sprint to address this issue breaks the intended cadence and purpose of Scrum events.

Correct Answer: Propose to put the changes into the Product Backlog and have them estimated by the Development Team for future sprints.

The best action for a Scrum Master when stakeholders ask for changes that would affect the next sprint's goal during a Sprint Review is to propose the changes be placed in the Product Backlog and have them estimated by the Development Team for future sprints. This is because the Scrum methodology emphasises flexibility and adaptability but at the same time, respect for set sprint goals and timelines. The next sprint's goal is already established and should not be altered last minute due to stakeholder requests. Meanwhile, the other answer choices are incorrect because incorporating the changes immediately would disrupt the pre-planned sprint and might negatively impact the team's performance. Asking the team to work on the changes during the Sprint Retrospective is inappropriate because the Retrospective is a time for reflection and planning for improvement, not for doing actual development work. Ignoring the changes is not a good idea because stakeholder feedback is valuable and can provide insight into the potential improvements for the product.