Most Recent Scrum PSM-II Exam Questions & Answers

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

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.

A) The stakeholders have not been using the Sprint Reviews to actively engage, and inspect and evaluate progress. This is a possible factor that may have led to the disappointment and anger of the stakeholders. The Sprint Review is an event where the Scrum Team and the stakeholders collaborate to inspect the product Increment and adapt the Product Backlog based on feedback and new insights. If the stakeholders do not participate actively in the Sprint Review, they may miss the opportunity to provide input, voice their concerns, and influence the direction of the product development.

D) The Scrum Master has not ensured transparency. This is another possible factor that may have led to the disappointment and anger of the stakeholders. The Scrum Master is accountable for establishing and promoting transparency among the Scrum Team and the stakeholders, by ensuring that everyone has a clear and common understanding of the product vision, the Product Goal, the Product Backlog, the Sprint Goal, the Sprint Backlog, and the Definition of Done. Without transparency, there may be misalignment, confusion, or unrealistic expectations among the stakeholders regarding the product being built.

E) The Product Owner has not been interacting frequently with the stakeholders and kept them aware of the progress of the project. This is also a possible factor that may have led to the disappointment and anger of the stakeholders. The Product Owner is responsible for engaging with the stakeholders regularly and communicating the value, scope, and status of the product development. The Product Owner should also seek feedback from the stakeholders and incorporate it into the Product Backlog refinement and ordering. If the Product Owner does not interact frequently with the stakeholders, they may feel disconnected, ignored, or dissatisfied with the product being built.

The Scrum Guide, section 2.3 (The Scrum Team), page 7

The Scrum Guide, section 3.6 (The Sprint Review), page 11

The Scrum Guide, section 4.1 (The Product Backlog), page 11

The Scrum Master Learning Path, module 2 (The Scrum Framework), lesson 5 (The Sprint Review) and lesson 6 (The Sprint Retrospective)

When multiple Scrum Teams work from the same Product Backlog, they need to collaborate and coordinate their work to deliver a potentially releasable Increment that meets the Definition of Done. This requires minimizing dependencies between Scrum Teams, such as technical, functional, or organizational dependencies. Dependencies can cause delays, rework, waste, and lower quality.Scrum Teams should strive to be cross-functional and autonomous, and use techniques such as feature slicing, dependency mapping, and integration testing to reduce dependencies123.Reference:1: https://www.scrum.org/resources/blog/dependencies-between-scrum-teams2: https://www.scrum.org/resources/blog/feature-slicing-how-make-it-work3: https://www.scrum.org/resources/blog/integration-testing-scrum-projects