PSM-II Exam Dumps and Practice Questions

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

The Scrum values of courage, openness, and respect are touched in this situation. Courage means that the Scrum Team members have the courage to do the right thing and work on tough problems, and also to speak up when they have concerns or disagreements. Openness means that the Scrum Team members and stakeholders agree to be open about all the work and the challenges with performing the work. Respect means that the Scrum Team members respect each other to be capable, independent people, and also respect the opinions and ideas of others.

In this case, the newest developer showed courage by expressing his feelings during the Sprint Retrospective, which is an opportunity for the Scrum Team to inspect itself and create a plan for improvements. The rest of the Developers should have been more open to listening to his perspective and ideas throughout the Sprint, as they might have valuable insights or suggestions for improving the product or the process. The Developers should also have respected the newest developer as a member of the team, and given him a fair chance to contribute and collaborate with them.

The Scrum Guide, November 2020, p. 13-14

What are the 5 Scrum Values?, Visual Paradigm, accessed on September 30, 2023

Scrum Values Poster, Scrum.org, accessed on September 30, 2023

A) They discuss in the upcoming Sprint Retrospective why this happened and what changes will make it less likely to recur. This is a good action to take, as it shows that the Scrum Team is willing to inspect and adapt their process and improve their collaboration and communication. The Sprint Retrospective is an opportunity for the Scrum Team to identify the root causes of the problem and create a plan for implementing improvements in the next Sprint.

D) The Developers forecast the most likely Product Backlog items to meet the business objective and create a Sprint Backlog based on a likely initial design and plan. Once the timebox for the Sprint Planning event is over, they start the Sprint and continue to analyze, decompose, and create additional functionality during the Sprint. This is also a good action to take, as it shows that the Scrum Team is flexible and adaptive, and does not let uncertainty or ambiguity prevent them from delivering value. The Developers can use the Sprint Goal as a guide to select and refine the Product Backlog items during the Sprint, and collaborate with the Product Owner to ensure that they are meeting the expectations and needs of the stakeholders.

The Scrum Guide, section 3.1 (The Sprint), page 8

The Scrum Guide, section 3.3 (The Sprint Goal), page 9

The Scrum Guide, section 3.5 (The Sprint Planning), page 10

The Scrum Guide, section 3.7 (The Sprint Retrospective), page 12

The Scrum Master Learning Path, module 2 (The Scrum Framework), lesson 2 (The Sprint), lesson 3 (The Sprint Goal), lesson 4 (Sprint Planning) and lesson 6 (The Sprint Retrospective)

https://www.scrum.org/resources/what-is-a-product-backlogThe Product Owner is responsible for maximizing the value of the product resulting from the work of the Scrum Team1.One of the ways to do this is to order the Product Backlog in a way that reflects the flow of value to the stakeholders and customers2.The Product Owner can use various factors to order the Product Backlog, such as value, risk, dependencies, learning opportunities, and feedback loops3.

However, sometimes the Product Owner may face challenges or constraints that affect the ordering of the Product Backlog, such as external dependencies, market changes, technical issues, or stakeholder requests4. In such cases, the Product Owner needs to balance between delivering value and managing risks.The Product Owner may need to adjust the Product Backlog ordering to account for these factors, but not at the expense of compromising the value delivery5.

In this scenario, the Developers are waiting for an external supplier to deliver a specific product component that they need to integrate and use. Without that component there will not be enough work in the next Sprint to occupy the full team. They ask their Product Owner to re-order the Product Backlog. The Product Owner asks the Scrum Master for help. A good advice for the Product Owner would be to tell them that their primary concern is the flow of value reflected in the ordering of the Product Backlog. Timeline of the flow might be influenced by such dependencies and require some level of Product Backlog re-ordering.

This advice would help the Product Owner to focus on delivering value while also considering the impact of the external dependency. The Product Owner could work with the Developers and stakeholders to identify and prioritize other valuable work that can be done in the next Sprint without relying on the external component. The Product Owner could also communicate with the external supplier and try to minimize or eliminate the dependency as much as possible.

The other options are not good advice for the Product Owner. Telling them that they need to re-order the Product Backlog to maximize utilization of the Developers would imply that keeping productivity high is more important than delivering value. This would go against the Scrum values of focus and respect. Telling them to remove all work involving the external component from the Product Backlog and create a new backlog for it would imply that they are ignoring or avoiding the dependency rather than managing it. This would go against the Scrum values of courage and openness.

The Scrum Guide 2020, section ''The Product Owner''

What is a Product Backlog? | Scrum.org, section ''Ordering''

Product Backlog Ordering - Zen Ex Machina, section ''Ordering by Value''

Product Backlog Ordering - Zen Ex Machina, section ''Ordering by Risk''

Ordered Not Prioritized | Scrum.org, section ''Ordering by Dependencies''

[The Scrum Values | Scrum.org], section ''The Scrum Values''

C) They are added to the Product Backlog and addressed throughout the next Sprints, combined with creating the business functionality in those Sprints, no matter how small that business functionality.

This is a good way because it is consistent with the Scrum principle ofempiricism, which means that the Scrum Team learns and adapts based on the actual outcomes and feedback, rather than following a predefined plan12. By adding these security concerns to the Product Backlog, the Product Owner can prioritize and refine them according to the value and urgency, and communicate them to the stakeholders.By addressing them throughout the next Sprints, the Scrum Team can deliver valuable and functional increments that also meet the security requirements34. D. During the Sprint Retrospective, the Scrum Team assesses how to add these expectations to the Definition of Done so every future Increment will live up to these requirements. If needed they can work with external specialists to better understand the requirements

This is another good way because it is consistent with the Scrum value ofopenness, which means that the Scrum Team and the stakeholders have a clear and common understanding of the product vision, goals, progress, and risks12. By adding these expectations to the Definition of Done, the Scrum Team can ensure that every future Increment meets the quality standards and satisfies the stakeholder needs.By working with external specialists, the Scrum Team can also leverage their expertise and experience to better understand and implement the security requirements34.