PSPO PSPO-I Reddit Questions

• The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product.
• All types of requirements are acceptable on a Product Backlog, as long as they are aligned with the product vision and goals, and they are transparent, clear, and valuable. The Product Backlog can include stability requirements, performance requirements, product functionality, documentation, fixes, or any other aspects that contribute to the quality and usability of the product.
• The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The Product Owner is responsible for managing and refining the Product Backlog, collaborating with the stakeholders and the Developers, and ordering the items in a way that best achieves goals and missions. The Product Owner represents the interests of everyone with a stake in the product and ensures that the Scrum Team works on the right things at the right time.
• The Developers are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog

The Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices1. The Scrum Master also facilitates Scrum events as requested or needed2. The Daily Scrum is a 15-minute event for the Developers to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary[3][3]. It is a key opportunity for the Developers to plan their work for the next 24 hours and collaborate on any challenges or impediments4. The Scrum Master should coach the team on the purpose and value of the Daily Scrum, and help them find ways to make it more effective and enjoyable. The Scrum Master should also learn why the Developers want to reduce the frequency of the Daily Scrum, and work with them to address any underlying issues or concerns. The Scrum Master should not impose a decision on the team, nor delegate the decision to a vote, as these actions would undermine the self-management and empowerment of the Developers5.

References:

• 1: The Scrum Guide, November 2020, p. 7
• 2: The Scrum Guide, November 2020, p. 11
• [3][3]: The Scrum Guide, November 2020, p. 10
• 4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

According to Scrum.org, when splitting a large group into multiple Scrum Teams, it can be beneficial to allow the people to self-organize into smaller teams12. This approach respects the principle of self-organization, which is a key aspect of Scrum12. It allows individuals to choose the team they feel they can contribute to most effectively12. However, it’s important to note that this process should be facilitated and guided to ensure a balanced distribution of skills and capabilities across the teams12.

The Scrum Guide states that "Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint."1 This means that there is no gap or break between Sprints, and the Scrum Team does not need to spend extra time to prepare for the next Sprint. The Scrum Team should be able to start the next Sprint Planning right after the Sprint Review and Sprint Retrospective of the previous Sprint. The Scrum Team should also ensure that the testing and documentation of the work are done within the Sprint, and not left for later.

References:

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