Professional Scrum Master Facilitating Scrum Events Questions and Answers — Questions and Answers
Question 1: During a Daily Scrum, a Developer mentions a significant technical challenge that is blocking their progress on a critical Sprint Backlog item. The other Developers immediately start offering detailed solutions, and the discussion consumes the rest of the 15-minute timebox. As a Scrum Master, what is the most effective way to facilitate this situation?
- Politely interrupt the technical discussion, note it as an impediment, and suggest that the involved Developers meet immediately after the Daily Scrum to work on a solution. (Correct answer)
- Allow the discussion to continue as long as it is productive, as resolving impediments is a key purpose of the Daily Scrum.
- Take note of the proposed solutions and assign the best one to the Developer to implement.
- Remind the team that the Daily Scrum is only for reporting status and that problem-solving should happen at a different time.
Correct answer: Politely interrupt the technical discussion, note it as an impediment, and suggest that the involved Developers meet immediately after the Daily Scrum to work on a solution.
The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and create a plan for the next 24 hours. While identifying impediments is crucial, the 15-minute timebox is not intended for in-depth problem-solving. The Scrum Master's role is to ensure the event is positive and productive. The best facilitation technique is to acknowledge the impediment, ensure it's made transparent, and encourage the relevant team members to collaborate on a solution outside of the Daily Scrum, thus respecting the timebox and the purpose of the event.
Question 2: A Scrum Team is holding its Sprint Retrospective. The discussion becomes dominated by a few vocal members, while others remain silent. The team has not generated many actionable improvement items in the past few Sprints. Which facilitation technique would be most appropriate for the Scrum Master to introduce?
- Ask each individual to directly call out another team member who has not spoken yet.
- End the meeting early and talk to the silent members individually to gather their feedback privately.
- Implement a structured format, such as asking everyone to write their thoughts on sticky notes for key topics (e.g., 'What went well?', 'What could be improved?') and then discuss them as a group. (Correct answer)
- As the facilitator, propose a list of improvements based on your own observations of the Sprint and ask the team to vote on them.
Correct answer: Implement a structured format, such as asking everyone to write their thoughts on sticky notes for key topics (e.g., 'What went well?', 'What could be improved?') and then discuss them as a group.
A key responsibility of the Scrum Master is to ensure that the Scrum events are positive and productive for the entire team. In a Sprint Retrospective, the goal is to plan ways to increase quality and effectiveness by inspecting the last Sprint. If the discussion is unbalanced, a good facilitator will introduce techniques that encourage participation from everyone. Using a structured, non-verbal method like writing on sticky notes allows all team members, including introverted ones, to contribute their ideas equally before the discussion begins. This fosters a more inclusive and psychologically safe environment, leading to more valuable and diverse improvement ideas.
Question 3: Which of the following is the primary focus of the Sprint Review?
- To provide a status update to stakeholders and secure approval for the Increment.
- To inspect the outcome of the Sprint and collaborate on what to do next based on the new insights. (Correct answer)
- To review and improve the Scrum Team's processes, interactions, and tools.
- To demonstrate every single item worked on during the Sprint, regardless of its completion status.
Correct answer: To inspect the outcome of the Sprint and collaborate on what to do next based on the new insights.
The Scrum Guide states, 'The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations.' It is a working session where the Scrum Team and stakeholders collaborate on the progress towards the Product Goal. This includes reviewing what was accomplished, discussing any changes in the environment, and adapting the Product Backlog. It is explicitly not just a demo or a status meeting for approval.
Question 4: During Sprint Planning, the Product Owner presents a Sprint Goal, but the Developers feel they lack sufficient information on several high-priority Product Backlog items to determine what can be done. What should the Scrum Master do?
- Cancel the Sprint Planning meeting and instruct the Product Owner to refine the backlog further before rescheduling.
- Proceed with the meeting, and have the Developers select only the items they fully understand, even if it means not achieving the proposed Sprint Goal.
- Encourage the Product Owner to cancel the Sprint.
- Facilitate a collaborative discussion between the Product Owner and the Developers to refine the items during the Sprint Planning event, enabling a forecast and the crafting of a Sprint Goal. (Correct answer)
Correct answer: Facilitate a collaborative discussion between the Product Owner and the Developers to refine the items during the Sprint Planning event, enabling a forecast and the crafting of a Sprint Goal.
Sprint Planning is a collaborative event for the entire Scrum Team. One of its purposes is for the Developers to select items from the Product Backlog and create a plan for the Sprint. The Scrum Guide notes that the Scrum Team may refine items during this process to increase understanding and confidence. The Scrum Master's role is to facilitate this collaboration, ensuring the event is productive. Canceling the event or the Sprint is a drastic measure and usually not the best first step. The goal is to produce a plan for the Sprint, which includes a Sprint Goal and a selection of Product Backlog items.
Question 5: A key stakeholder frequently attends the Daily Scrum and uses the event to ask the Developers for status updates and assign new tasks. This is causing the event to regularly exceed its 15-minute timebox and is shifting the team's focus away from the Sprint Goal. How should the Scrum Master address this?
- Politely un-invite the stakeholder from future Daily Scrums as it is an event for the Developers.
- Coach the stakeholder on the purpose of the Daily Scrum and work with them and the team to find a more appropriate way to communicate outside of the event. (Correct answer)
- Extend the timebox for the Daily Scrum to 30 minutes to accommodate the stakeholder's questions.
- Instruct the Developers to ignore the stakeholder's requests and focus only on their original plan.
Correct answer: Coach the stakeholder on the purpose of the Daily Scrum and work with them and the team to find a more appropriate way to communicate outside of the event.
The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt their plan for the next day. It is not a status meeting for stakeholders. While others can attend, the Scrum Master is accountable for ensuring the event happens and that its purpose is understood. A key part of the Scrum Master's role is to remove impediments and protect the team from outside disruptions. The most effective approach is to coach the stakeholder on the purpose of the event and help establish a better communication channel, thereby resolving the disruption without creating conflict.
Question 6: At the end of the Sprint Retrospective, the Scrum Team has identified several impactful improvements. What is the most effective way to ensure these improvements are acted upon?
- The Scrum Master should assign each improvement item to an individual on the Scrum Team.
- The Scrum Team should select at least one high-priority improvement and add it to the Sprint Backlog for the next Sprint. (Correct answer)
- The Product Owner should add all the improvement items to the bottom of the Product Backlog.
- The improvements should be documented in a shared location for the team to review and implement whenever they have spare capacity.
Correct answer: The Scrum Team should select at least one high-priority improvement and add it to the Sprint Backlog for the next Sprint.
The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. To ensure that the identified improvements are not forgotten, the most impactful ones should be addressed as soon as possible. The Scrum Guide suggests that they may even be added to the Sprint Backlog for the next Sprint. This makes the commitment to improve visible and treats it with the same importance as other work planned for the Sprint, which is a key aspect of adaptation.
Professional Scrum Master Facilitating Scrum Events Questions and Answers
During a Daily Scrum, a Developer mentions a significant technical challenge that is blocking their progress on a critical Sprint Backlog item.
The other Developers immediately start offering detailed solutions, and the discussion consumes the rest of the 15-minute timebox.
As a Scrum Master, what is the most effective way to facilitate this situation?