PSPO-I Exam Dumps : Professional Scrum Product Owner (PSPO I) Exam

In accordance with Scrum theory, a group of 100 people should be divided into multiple Scrum Teams by understanding the product, the product vision and the rules of the Scrum framework, and then dividing themselves into teams because:

• It respects the self-organization and empowerment of the people. The people are the ones who have the knowledge, skills, and experience to create and deliver the product. They are also the ones who will work together as Scrum Teams, collaborating and coordinating their efforts. Therefore, they should have the autonomy and authority to decide how to form their teams, based on their preferences, interests, and capabilities.
• It supports the alignment and coherence of the Scrum Teams. The people should have a clear and shared understanding of the product, the product vision, and the rules of the Scrum framework before forming their teams. This can help them to align their goals and missions, to ensure that they are working on the same product and towards the same vision. It can also help them to follow the same principles and practices of Scrum, to ensure that they are working effectively and consistently.
• It fosters the collaboration and synergy of the Scrum Teams. The people should form their teams in a way that maximizes their collaboration and synergy. This can mean choosing team members that complement each other’s skills and strengths, that have good rapport and trust, that can communicate and coordinate well, and that can deliver a valuable Increment each Sprint.

References:

• Scrum Guide 2020, page 5: “Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value in each Sprint.”
• Scrum Guide 2020, page 5: “Scrum Teams are self-managing, meaning they internally decide who does what, when, and how.”
• Scrum Guide 2020, page 9: “Multiple Scrum Teams working together on a product use one Product Backlog.”
• Scrum Guide 2020, page 9: “The Product Owner is one person, not a committee.”

 New work or further decomposition of work is added to the Sprint Backlog as soon as possible after it is identified because:

• It reflects the current state of the Sprint. The Sprint Backlog is a plan that the Developers create and update throughout the Sprint, based on their progress, learnings, and changes. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that the Sprint Backlog is transparent, accurate, and up-to-date.
• It enables the Developers to self-manage their work. The Developers are accountable for organizing and managing their own work, and they have the authority to change the Sprint Backlog as needed. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can exercise their autonomy and empowerment, and adjust their plan accordingly.
• It supports the achievement of the Sprint Goal. The Sprint Goal is a single objective that provides guidance and focus for the Developers throughout the Sprint. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that their work is aligned with and contributes to the Sprint Goal.

References:

• Scrum Guide 2020, page 6: “Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.”
• Scrum Guide 2020, page 6: “The Developers are accountable for … organizing and managing their work.”
• Scrum Guide 2020, page 10: “The Sprint Goal is a single objective for the Sprint.”
• Scrum Guide 2020, page 14: “The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current Definition of Done.”
• Scrum Guide 2020, page 14: “The Sprint Backlog is composed of … all of the work needed to deliver a product Increment that meets the Definition of Done.”
• Scrum Guide 2020, page 14: “The Developers can change the content of the Sprint Backlog throughout the Sprint as more is learned.”

The Definition of Done is a shared understanding of what it means for work to be complete, and to ensure transparency. The Scrum Guide states that "The Developers are required to conform to the Definition of Done, as defined by the Scrum Team. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done."1 This means that the Product Owner does not have the final say over the Definition of Done, but rather collaborates with the Developers and the Scrum Master to agree on the quality standards and expectations for the product.

References:

• 1: The Scrum Guide2, page 14
• 2: The Scrum Guide