Scrum PSPO-I Exam Questions

New work or further decomposition of work is added to the Sprint Backlog as soon as possible after it is identified because:

It reflects the current state of the Sprint. The Sprint Backlog is a plan that the Developers create and update throughout the Sprint, based on their progress, learnings, and changes. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that the Sprint Backlog is transparent, accurate, and up-to-date.

It enables the Developers to self-manage their work. The Developers are accountable for organizing and managing their own work, and they have the authority to change the Sprint Backlog as needed. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can exercise their autonomy and empowerment, and adjust their plan accordingly.

It supports the achievement of the Sprint Goal. The Sprint Goal is a single objective that provides guidance and focus for the Developers throughout the Sprint. By adding new work or further decomposition of work to the Sprint Backlog promptly, the Developers can ensure that their work is aligned with and contributes to the Sprint Goal.

Scrum Guide 2020, page 6: ''Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.''

Scrum Guide 2020, page 6: ''The Developers are accountable for ... organizing and managing their work.''

Scrum Guide 2020, page 10: ''The Sprint Goal is a single objective for the Sprint.''

Scrum Guide 2020, page 14: ''The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current Definition of Done.''

Scrum Guide 2020, page 14: ''The Sprint Backlog is composed of ... all of the work needed to deliver a product Increment that meets the Definition of Done.''

Scrum Guide 2020, page 14: ''The Developers can change the content of the Sprint Backlog throughout the Sprint as more is learned.''

Developers are self-managing, which means that they decide how much work they can do in a Sprint, and how they will do it1. They manage the Sprint Backlog, which is the plan for how the Developers will achieve the Sprint Goal, and the single source of truth for the work to be done in the Sprint2. The Developers create and update the Sprint Backlog throughout the Sprint as more is learned[3][3]. The other options are not managed by the Developers, but by the Product Owner or the Scrum Team as a whole. The Product Owner is accountable for ordering the Product Backlog, which is an ordered list of everything that is known to be needed in the product4. The Product Owner also decides when to release the product, based on the value, risk, and stakeholder feedback5. The Scrum Team collaborates on inviting the stakeholders for the Sprint Review, which is an event where the Scrum Team and the stakeholders inspect the product Increment and adapt the Product Backlog. The Scrum Team also decides the Sprint length, which is the time-box within which the Scrum Team delivers a product Increment.

1: The Scrum Guide, November 2020, p. 6

2: The Scrum Guide, November 2020, p. 10

[3][3]: The Scrum Guide, November 2020, p. 10

4: The Scrum Guide, November 2020, p. 6

5: Managing Products with Agility, Scrum.org, accessed on December 16, 2023

: The Scrum Guide, November 2020, p. 13

: The Scrum Guide, November 2020, p. 9

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 job of a Product Owner focuses on the following aspects:

Working with customers and stakeholders to identify the most valuable product requirements: The Product Owner engages in frequent and regular interactions with the people who have a stake or interest in the product, such as customers, users, sponsors, managers, or other teams. The Product Owner solicits and incorporates their input, feedback, and insights to understand their needs and expectations, discover new opportunities or ideas, align and collaborate on the product direction and priorities, and validate and deliver value to them. The Product Owner translates these requirements into Product Backlog items that can deliver value to customers or users.

Clearly communicating project or release status and strategies to customers and stakeholders: The Product Owner communicates effectively and transparently with the customers and stakeholders about the progress, outcomes, and plans of the product development. The Product Owner shares relevant information and data about the product vision, goals, value proposition, roadmap, backlog, increment, feedback, or metrics. The Product Owner also communicates the strategies and decisions for delivering value to customers or users, such as release frequency, scope, quality, or risk management.

The other options are not valid or relevant aspects of a Product Owner's job. They are either too narrow, unrealistic, or unrelated to the product value delivery. They are:

Writing clear, transparent User Stories: This is not a valid aspect of a Product Owner's job. User Stories are a common format for expressing product requirements in an agile way. They consist of a brief description of a feature or function from the perspective of a user or customer. They usually follow a template such as ''As a <role>, I want <goal>, so that <benefit>''. However, User Stories are not mandatory or universal in Scrum. The Product Owner can use any format or method to express product requirements, as long as they are clear, concise, and valuable. The format or method does not affect the value or quality of the product or service delivered.

Being with the Scrum Team all the time, just in case they need me to clarify a requirement: This is not a realistic aspect of a Product Owner's job. The Product Owner does not have to be physically present with the Scrum Team all the time. The Product Owner can work remotely or asynchronously with the Scrum Team, as long as they maintain effective communication and collaboration. The Product Owner should also empower and trust the Developers to make technical decisions and trade-offs that best meet the product goals and quality standards. The Product Owner should also ensure that the Product Backlog items are sufficiently clear and refined before they are selected for a Sprint.

Scrum Guide: https://www.scrumguides.org/scrum-guide.html

Product Owner: https://www.scrum.org/resources/what-is-a-product-owner

User Stories: https://www.agilealliance.org/glossary/user-stories

Customer satisfaction is a measure of how well a product or service meets or exceeds the expectations and needs of the customers. It is an important indicator of the value and quality of a product or service, and it can affect the loyalty, retention, and profitability of the customers.

Customer satisfaction should be measured frequently, as it can change over time depending on various factors, such as the market conditions, the customer feedback, the product updates, the competitor actions, and the customer behavior. Measuring customer satisfaction frequently can help the Product Owner and the Scrum Team to inspect and adapt their product vision, strategy, roadmap, backlog, and increments based on the customer needs and preferences. It can also help them to identify and resolve any issues or gaps that may affect the customer satisfaction and value delivery.

Measuring customer satisfaction quarterly, daily, or annually is not optimal, as it may not reflect the current state of the customer satisfaction and may miss some opportunities or risks that may arise in between the measurement intervals. Quarterly measurement may be too slow to respond to the fast-changing market and customer demands. Daily measurement may be too noisy and costly to collect and analyze. Annual measurement may be too outdated and irrelevant to inform the product decisions.

Scrum Guide: https://www.scrumguides.org/scrum-guide.html

Customer Satisfaction: https://www.agilealliance.org/glossary/customer-satisfaction/

The Product Owner and the Scrum Master are essential roles in the Scrum Team. They have distinct accountabilities and responsibilities that contribute to the success of the product and the team. The Product Owner is responsible for maximizing the value of the product and the work of the Developers. The Scrum Master is responsible for promoting and supporting Scrum and the Scrum Team. Both roles need to be fully engaged and available to the Scrum Team throughout the Sprint.