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

• The Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment.
• The timebox for the Sprint Planning event is proportional to the length of the Sprint. For a one-month Sprint, the timebox is 8 hours. For shorter Sprints, the timebox is usually shorter. The Scrum Team may decide how much time to spend on each topic within the timebox, depending on their needs and preferences.
• The timebox for the Sprint Planning event ensures that the Scrum Team does not spend too much or too little time on planning their work for the Sprint. The timebox also ensures that the Scrum Team has enough clarity and alignment on what and how they want to achieve during the Sprint.

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Sprint Planning: https://www.scrum.org/resources/what-is-sprint-planning