PSM-II Exam Dumps : Professional Scrum Master II

• B: Ask the Developers and the Product Owner if removing regression testing from the Definition of Done allows the team to produce useful and valuable Increments at the end of every Sprint. This is a good way to challenge the decision and make them think about the consequences of lowering the quality standards. The Scrum Master can help them understand the importance of delivering a potentially releasable product increment that meets the expectations of the stakeholders and customers.
• C: Ask the Developers and the Product Owner what problem they are going to solve by altering the Definition of Done during the Sprint to remove regression testing. Will this raise transparency or improve quality? This is a good way to explore the root cause of the issue and find out why they are not able to complete regression testing for all of the selected Product Backlog items in the Sprint. The Scrum Master can help them identify and remove any impediments or inefficiencies that prevent them from achieving their Sprint Goal.

References:

• Scrum Guide 2020, page 9: “The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.”
• Scrum Guide 2020, page 13: “The Scrum Master serves the Scrum Team in several ways, including coaching the team members in self-management and cross-functionality.”
• Professional Scrum Master II Course, page 12: “The Definition of Done is a crucial aspect of transparency. If it is not clear when work is done, then stakeholders may make wrong assumptions about the state of the software.”

The complexity of the problem being solved and the complexity of the requirements are both sources of uncertainty and variability that can impact the Sprint Goal and the Sprint Backlog. The skills and working relationships of the people on the Scrum Team(s) are also crucial for delivering a valuable product increment in a Sprint. The Scrum Master is accountable for establishing an environment where the Scrum Team can be effective and improving the professionalism of the Scrum Team.

References:

• Scrum Guide 2020, page 6: “The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.”
• Scrum Guide 2020, page 10: “The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog items. This provides guidance to the Development Team on why it is building the Increment.”
• Scrum Guide 2020, page 11: “The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).”
• Evidence-Based Management Guide, page 9: “Uncertainty is inherent in complex work. The more complex work is, the more uncertainty there is. Uncertainty comes from two sources: variability and emergence.”

 The Daily Scrum is a 15-minute event for the Developers of the Scrum Team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work1. It is one of the five events of the Scrum framework and enables the three pillars of the empirical process of Scrum: transparency, inspection, and adaptation2. The Daily Scrum is not a status meeting, but a chance for the Developers to collaborate, coordinate, and plan their work3.

As a Scrum Master, you could help the Developers understand that lowering the frequency of communication will only increase the feeling of disconnect between the team members, especially when they are working from globally distributed locations. You could also coach the Developers on why a daily frequency is important as an opportunity to update the Sprint Plan and how it helps the team organize work toward achieving the Sprint Goal. You could suggest alternative conferencing tools or methods that are easily available and effective for the team. You could also facilitate the Daily Scrum by ensuring that it is positive, productive, and focused on the Sprint Goal.

Acknowledging and supporting this self-managing team’s decision might seem like a good option, but it would not help the team to improve their collaboration and alignment. Having the Developers vote to make sure there is consensus within the team might also seem like a democratic way to handle the situation, but it would not address the underlying issue of why the team wants to reduce the frequency of the Daily Scrum.

References:

• The Scrum Guide 2020, section “The Daily Scrum”
• What Is the Daily Scrum?, A Guide to the Daily Event - Scrum Alliance
• The Importance of Daily Scrum Meetings | Grata Software