PSPO PSPO-I Updated Exam

According to Scrum.org, the Developers own the Sprint Backlog12.The Sprint Backlog is a plan by and for the Developers1.It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal1.Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned1.

Scrum is a framework for developing, delivering, and sustaining complex products. Scrum defines three roles: the Product Owner, the Scrum Master, and the Developers. Scrum does not have any other roles or titles, such as “tester”, “analyst”, “designer”, or “architect”.

The Developers are the people in the Scrum Team who 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.

The Developers are responsible for quality, not just for programming. Quality is not something that can be added or verified after the product is built. Quality is something that must be built into the product from the start, by following good practices, standards, and principles. Quality is also something that must be inspected and adapted continuously, by applying feedback loops, testing methods, and improvement actions.

The Developers are not divided into sub-teams or sub-roles based on their skills or specialties. The Developers are a cross-functional and self-organizing team that has all the skills and capabilities needed to create a valuable product Increment. The Developers collaborate and coordinate their work as one unit, without any hand-offs or silos.

The Developers may have different backgrounds or expertise, such as testing, analysis, design, or architecture. However, these are not separate roles or responsibilities in Scrum. They are part of the collective accountability and responsibility of the Developers as a whole. The Developers may perform different tasks or activities based on their skills or preferences, but they are all equally responsible for delivering a high-quality product Increment.

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 aforecast 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 SprintBacklog is a plan with enough detail that changes in progress can be understood in the Daily Scrum1.

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

The reasons why it is important that there is only one Product Owner per product are:

It is clear who is accountable for the ultimate value of the product. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for identifying and articulating the Product Goal, which is a long-term objective for the product that guides all the activities of the Scrum Team.

It helps avoid barriers to effective communication and rapid decision-making. The Product Owner is the sole person responsible for managing the Product Backlog, which is an emergent, ordered list of what is needed to improve the product. They must ensure that the Product Backlog is transparent, visible, and understood by everyone who needs to work on it. They must also collaborate with the Developers and the stakeholders to refine, order, and prioritize the Product Backlog items based on value and impact.

The Scrum Team always knows who determines the order of the Product Backlog. The Product Owner has the final authority to decide what items are more important and valuable for the product. They must communicate this order clearly and consistently to the Scrum Team and the stakeholders. They must also respect and support the self-management of the Developers in choosing how best to accomplish their work.

Other options, such as the Scrum Master knowing who acts as their backup while on vacation or it would confuse the stakeholders if they had to work with more than one person, are not valid reasons why it is important that there is only one Product Owner per product. They may reflect a misunderstanding of the roles and accountabilities of the Scrum Team or the stakeholders.