Online PSPO-I Questions Video

 An Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.1 An Increment is a concrete, tangible, and usable outcome of the work done by the Developers in a Sprint. It is not a plan, a mock-up, a design, or a roll-out plan, as these are not valuable or useful products in themselves. An Increment must meet the definition of “Done”, which means it must adhere to the quality standards agreed upon by the Scrum Team and the stakeholders.1 An Increment must also be potentially releasable, which means it must be in a state that it could be delivered to the customer or user if the Product Owner decides so.1

References:

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

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal1. The Sprint Backlog is a forecast by the Developers about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment1. The Sprint Backlog makes visible all the work that the Developers identify as necessary to meet the Sprint Goal1. The Sprint Backlog can include any items that the Developers deem necessary to achieve the Sprint Goal, such as user stories, tasks, use cases, tests, or others. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum1.

References:

• The Scrum Guide, section 3.3. Sprint Backlog
• Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.2. The Product Owner and the Sprint
• Professional Scrum Product Owner I (PSPO I) Sample Questions, question 11

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 Team can maintain the Product Backlog to maximize its transparency by continually keeping it up to date with the most recent insights because:

• It reflects the current state of the product and the work. The Product Backlog is a dynamic and emergent artifact that represents all the possible features, functions, requirements, enhancements, and fixes that constitute changes to the product. By updating it frequently, the Scrum Team can ensure that the Product Backlog is accurate, complete, and relevant.
• It enables the Product Owner to optimize the value of the product and the work of the Scrum Team. The Product Owner is accountable for effective Product Backlog management, which includes ordering, refining, and communicating the Product Backlog items. By updating it frequently, the Product Owner can incorporate new learnings, feedback, opportunities, and changes into the product decisions and priorities.
• It supports the inspection and adaptation of the Scrum Team and the stakeholders. The Product Backlog is a source of information and transparency for everyone involved in the product development. By updating it frequently, the Scrum Team and the stakeholders can inspect the progress and outcomes of each Sprint, and adapt their plans and actions accordingly.

References:

• Scrum Guide 2020, page 10: “The Product Backlog is an emergent, ordered list of what is needed to improve the product.”
• Scrum Guide 2020, page 11: “The Product Owner is accountable for effective Product Backlog management, which includes … ensuring that the Product Backlog is transparent, visible and understood.”
• Scrum Guide 2020, page 11: “The ordering of the items in the Product Backlog is the sole responsibility of the Product Owner. They order Product Backlog items to best achieve goals and missions.”
• Scrum Guide 2020, page 11: “Higher ordered Product Backlog items are clearer and more refined than lower ordered ones.”
• Scrum Guide 2020, page 15: “The Sprint Review is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.”