Scrum Professional Scrum Product Owner I PSPO-I Exam Questions

Answer : A

The Developers are accountable for managing the progress of work during a Sprint, as they are the ones who plan, execute, and deliver the work. The Scrum Guide states that 'The Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.'1 The Developers are also responsible for conducting the Daily Scrum, a 15-minute event for the Developers to synchronize activities and create a plan for the next 24 hours.1 The Developers are self-managing, which means they decide how best to accomplish their work, rather than being directed by others outside the Scrum Team.1

1: The Scrum Guide2, page 7

2: The Scrum Guide

Answer : D

The Sprint Backlog is created during Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that 'The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).'1 The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.

1: The Scrum Guide2, page 15

2: The Scrum Guide

Answer : A

The Scrum Guide states that ''the Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint''. It also states that ''the Developers can do the work of any other role on the Scrum Team, as long as accountability is met''. Therefore, the Developers on the Scrum Team should write the user documentation, as it is part of the Definition of Done and the work needed to deliver a ''Done'' Increment. The other options are not acceptable, as they violate the Scrum values of commitment, focus, and respect, and they create dependencies, delays, and waste.

The Scrum Guide, section 2.2. Developers

Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.3. The Product Owner and the Definition of Done

Professional Scrum Product Owner I (PSPO I) Sample Questions, question 12

Answer : A, B, C

The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are responsible for creating and communicating a vision, ordering the Product Backlog, and ensuring that the best possible job is done to delight customers. The Developers are the people in the Scrum Team that are committed to delivering a ''Done'' Increment that meets the Definition of Done and the Sprint Goal. They are responsible for managing and organizing their work within the Sprint, collaborating with the Product Owner and the Scrum Master, and applying their skills and creativity to create a product that delivers value to the stakeholders and customers. A Project Manager is not a role in the Scrum Team, as Scrum does not recognize titles for Developers, regardless of the work being performed by the person. There is no need for a Project Manager, as the Scrum Team is self-managing and accountable for delivering value.

The Scrum Guide

The Scrum Team

Professional Scrum Product Owner I Certification

Answer : D, E

the first Sprint is the same as any other Sprint, and the Scrum Team should deliver a potentially releasable Increment of 'Done' product at its conclusion. This means that the team should build at least one piece of valuable functionality that meets the Definition of Done and aligns with the Sprint Goal. The other options are not things that the Scrum Team should do during the first Sprint, as they are either too detailed, too vague, or too long-term for the Scrum framework. The Scrum Team should not make up a plan for the rest of the project, as Scrum is an empirical process that adapts to changing requirements and feedback1. The Scrum Team should not define the major product features and a release plan architecture, as these are the responsibilities of the Product Owner, who should have a vision and a roadmap for the product2. The Scrum Team should not analyze, describe, and document the requirements for the subsequent Sprints, as this would violate the principle of emergent design and just-in-time planning3.

1: The Scrum Guide | Scrum.org 2: What is a Product Owner? | Scrum.org 3: Emergent Design and Just-in-Time Planning | Scrum.org

Answer : B

The Product Owner is responsible for managing and refining the Product Backlog, which is the single source of truth for the plan of the product development. The Product Backlog is a living artifact that changes as the product and the market evolve. The Product Owner updates the Product Backlog continuously based on feedback, learning, and stakeholder needs. There is no separate project plan document in Scrum.

[Scrum Guide], section 3.1: ''The Product Backlog is an emergent, ordered list of what is needed to improve the product.''

[Professional Scrum Product Owner], chapter 5: ''The Product Backlog represents everything necessary to develop and launch a successful product.''

[What is a Product Backlog?]: ''The Product Backlog is a list of all things that need to be done within the project.''

Answer : C, D

The Product Owner should care that the Scrum Team adheres to its Definition of Done because:

It helps to forecast the team's productivity over time. By having a clear and consistent Definition of Done, the Product Owner can measure the amount of work that the team can deliver in each Sprint and plan accordingly.

It affects the product's total cost of ownership. By ensuring that the work done by the team meets the quality standards and expectations of the stakeholders, the Product Owner can reduce the risk of technical debt, rework, defects, and maintenance costs in the future.

Scrum Guide 2020, page 10: ''The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product.''

Scrum Guide 2020, page 11: ''The Product Owner is accountable for effective Product Backlog management, which includes ... ordering Product Backlog items; and, ensuring that the Product Backlog is transparent, visible and understood.''

Scrum Guide 2020, page 14: ''The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration.''