PSM-II Exam Dumps : Professional Scrum Master II

Coach the Product Owner that achieving the Sprint Goal is the Scrum Team’s objective. A forecast is only used to initially estimate the effort required to reach the Sprint Goal.

• This is true because the Scrum Master’s role is to help the Product Owner understand the Scrum framework and its principles, such as empiricism, self-organization, and collaboration12. The Scrum Master should also remind the Product Owner that the forecast is not a commitment, but a plan that can be adjusted based on the Sprint progress and feedback3 . The Scrum Master should focus on the value and outcome of the Sprint, rather than the output and scope.

References: 1: What is a Scrum Master? | Scrum.org 2: What is a scrum master? [+ Responsibilities] | Atlassian 3: [Scrum Guide | Scrum Guides] : What Is a Scrum Master (and How Do I Become One)? - Coursera

A. Having one Product Owner will improve the clarity of accountability to the teams and to the product management department. This is a good suggestion, as it ensures that there is a single person who is responsible for maximizing the value of the product and managing the Product Backlog. Having one Product Owner also avoids confusion, duplication, or conflict among multiple Product Owners who may have different visions, priorities, or expectations for the product.

D. A single Product Backlog should be maintained holding all requirements for the new product. This is also a good suggestion, as it ensures that there is a single source of truth for the product requirements and that they are transparent and visible to all stakeholders. Having a single Product Backlog also enables the Product Owner to order the items based on their value, risk, dependency, and urgency, and to collaborate with the Scrum Teams to select and refine the items for each Sprint.

References:

• The Scrum Guide, section 2.3 (The Scrum Team), page 7
• The Scrum Guide, section 4.1 (The Product Backlog), page 11
• The Scrum Master Learning Path, module 2 (The Scrum Framework), lesson 4 (Sprint Planning) and lesson 5 (The Sprint Review)

When scaling Scrum, it is important to have multiple Scrum Teams working from one Product Backlog, because this ensures that they are aligned on the same product vision, goal, and value12. Having one Product Backlog also helps to reduce duplication, inconsistency, and waste, and to optimize the flow of work and feedback12. The Product Owner is accountable for managing the Product Backlog and ensuring that it is transparent, ordered, and refined for the multiple Scrum Teams3 . The Scrum Teams collaborate with the Product Owner and each other to deliver a single integrated product Increment every Sprint3 .

References: 1: What is Scaling Scrum? | Scrum.org 2: Scaling Scrum with Nexus | Scrum.org 3: Scrum Guide | Scrum Guides : The Nexus Framework for Scaling Scrum: Continuously Delivering an Integrated Product with Multiple Scrum Teams