Scrum PSM-II Exam Dumps

Respect is one of the Scrum values that means recognizing the value of each individual and their contribution, trusting them to fulfill their tasks, listening to and considering their ideas, and acknowledging their accomplishments. Respect also means honoring the diversity of people, their experiences, and their opinions. Respect facilitates collaboration, learning, and creativity in the Scrum Team.

Some statements that demonstrate respectful behavior in the Scrum Team are:

Respect the accountabilities of the Scrum Team members. This means that each role in the Scrum Team has a clear set of responsibilities and expectations, and that other team members respect those boundaries and do not interfere with or undermine them. For example, the Product Owner is accountable for maximizing the value of the product and the work of the Developers, and the Developers respect that by following the Product Owner's guidance on what to work on and what not to work on. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, causing change that increases the productivity of the Scrum Team, and working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization. The Developers respect that by adhering to the Scrum framework, being open to feedback and improvement, and collaborating with other Scrum Teams when needed.

Respect people, their experience, diversity, and difference in opinion. This means that each person in the Scrum Team is valued as a skilled professional who brings unique perspectives and insights to the team. The team members respect each other's expertise, skills, and ideas, and are willing to learn from each other and from their stakeholders. They also respect that people may have different opinions or preferences on how to approach a problem or a solution, and they seek to understand those differences rather than dismiss or ignore them. They engage in constructive dialogue and respectful disagreement when necessary, and they support team decisions even if they are not their personal choices.

Some statements that do not demonstrate respectful behavior in the Scrum Team are:

Respect the Product Owner by letting them change the Sprint Goal during the Sprint. This is not respectful because it violates the Scrum framework and undermines the Developers' autonomy and commitment. The Sprint Goal is a shared objective that provides guidance to the Developers on why they are building an Increment. It is crafted by the Product Owner in collaboration with the Developers during Sprint Planning, and it remains fixed for the duration of the Sprint unless a significant change occurs that invalidates it. Allowing the Product Owner to change the Sprint Goal during the Sprint would disrupt the focus and alignment of the Developers, introduce uncertainty and confusion, and reduce transparency and accountability.

Respect stakeholder expectations that Scrum Teams will meet their forecast. This is not respectful because it implies that stakeholders have unrealistic or unreasonable expectations that are not based on empirical evidence or feedback. The forecast is a plan for what functionality will be delivered in an Increment by the end of a Sprint. It is based on what is known at Sprint Planning, but it is not a guarantee or a commitment. The forecast may change during the Sprint as new information emerges or as unforeseen challenges arise. The Scrum Team respects stakeholders by being transparent about their progress and any changes to their forecast, by delivering a valuable Increment at least by the end of every Sprint, by seeking feedback from stakeholders during Sprint Review, and by incorporating that feedback into future Sprints.

The Scrum Values

Understanding the 5 Scrum Values

Top 5 Scrum Values & Principles

C) Timeboxes encourage the people who are closest to the problem to create the best possible result in the time allotted, given the current context.

This is true because timeboxes limit the amount of time that can be spent on an activity, which forces the Scrum Team to focus on the most valuable and feasible outcomes.Timeboxes also empower the Scrum Team to make decisions based on their own expertise and experience, rather than relying on external authorities or instructions12. D. Timeboxes help everyone focus on the same problem at the same time.

This is true because timeboxes create a shared sense of urgency and alignment among the Scrum Team and the stakeholders.Timeboxes also enable frequent feedback and inspection, which help the Scrum Team adapt to changing requirements and expectations12.

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.

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.''

A) You suggest taking the person aside and asking them what they believe the key outcomes are for the Daily Scrum. Effectively coaching them to help create focus during the Daily Scrum.

This is a good suggestion because it shows respect and empathy for the person, while also helping them understand the purpose and value of the Daily Scrum.Coaching is one of the core competencies of a Scrum Master, and it can help the person self-reflect and improve their behavior12. E. You suggest coaching the Developers to help them find a way to solve the problem, and own the solution.

This is another good suggestion because it empowers the Developers to take ownership of their own process and communication.The Scrum Master's role is not to impose rules or solutions, but to facilitate and enable the team's self-organization and collaboration12. By coaching the Developers, the Scrum Master can help them address the issue in a constructive and respectful way.

The Scrum Guide states that ''the moment a Product Backlog item meets the Definition of Done, an Increment is born'' and that ''the Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints''. Therefore, to deliver a product Increment that is integrated and potentially releasable, all Scrum Teams must have a shared understanding of what ''Done'' means and ensure that their work meets that standard. This also enables transparency, inspection, and adaptation across the Scrum Teams.

The Scrum Guide, section 3.4 (The Increment), page 10

The Scrum Master Learning Path, module 5 (The Increment), lesson 1 (What is an Increment?) and lesson 2 (Definition of Done)