Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
Who is accountable for creating a valuable and usable Increment each Sprint?
(choose the best answer)
The Scrum Team member who is accountable for creating a valuable and usable Increment each Sprint is the Developers. This is because:
The Developers are accountable for creating a ''Done'' Increment in every Sprint. They must ensure that every Product Backlog item they work on meets the Definition of Done before it is considered complete.
The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. It is a shared understanding among the Scrum Team and the stakeholders of what ''Done'' means for any Product Backlog item that is selected for a Sprint.
The Increment is a concrete and usable outcome of the Sprint that provides a measure of progress and value delivery. It must be in useable condition regardless of whether it will be released or not.
The Developers are self-managing professionals who organize and manage their own work. They decide how to best accomplish their work, rather than being directed by others outside the Scrum Team.
Other options, such as the CEO, the Product Owner, the Scrum Master, or the Scrum Team, are not accountable for creating a valuable and usable Increment each Sprint. They may have different roles and accountabilities in Scrum, but they do not do the actual work of creating a ''Done'' Increment.
[Scrum Guide], page 7, section ''Developers''
[Scrum Guide], page 10, section ''Definition of Done''
[Scrum Guide], page 10, section ''Increment''
[Scrum Guide], page 7, section ''The Scrum Team''
One of the Scrum events is the Daily Scrum. What are two intended outcomes of the Daily
Scrum?
(choose the best two answers)
The Daily Scrum is a 15-minute event for the Developers to synchronize activities and create a plan for the next 24 hours. This meeting is designed to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary. The intended outcomes are to identify any impediments that may prevent the Developers from achieving the Sprint Goal (D) and to foster a shared understanding among the Developers of what work is most important to undertake next in order to make the best possible progress toward the Sprint Goal (E). It is not a status update meeting for the Scrum Master or upper management, nor is it primarily about updating Scrum boards for stakeholder transparency.
What is the responsibility of the Product Owner in crafting the Sprint Goal?
(choose the best answer)
The Sprint Goal is a short statement of what the Scrum Team intends to achieve during a Sprint. It provides guidance and direction for the Scrum Team, as well as a basis for inspecting and adapting the product and the process. The Sprint Goal is aligned with the product vision and goals, and it reflects the value and purpose of the Sprint.
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.
The Sprint Planning is an event that occurs at the beginning of each Sprint, where the Scrum Team plans how to deliver a valuable product Increment. The Sprint Planning consists of two topics: What can be done this Sprint? and How will the chosen work get done? The outcome of the Sprint Planning is an agreed-upon Sprint Goal, a Sprint Backlog, and a plan for delivering the Increment.
The responsibility of crafting the Sprint Goal is shared by both the Product Owner and the Developers. The Product Owner should come to Sprint Planning with a business objective in mind, based on their understanding of the product vision, goals, value proposition, stakeholder feedback, market conditions, or other relevant factors. The Product Owner should propose how this objective can be achieved by selecting some Product Backlog items that can deliver value to customers or users. The Developers should collaborate with the Product Owner to craft a clear and concise Sprint Goal that expresses what they want to accomplish as a team during this Sprint. The Developers should also ensure that they have enough capacity and skills to deliver on this Sprint Goal.
Scrum Guide: https://www.scrumguides.org/scrum-guide.html
Sprint Goal: https://www.scrum.org/resources/what-is-a-sprint-goal
Product Owner: https://www.scrum.org/resources/what-is-a-product-owner
Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum
Sprint Planning: https://www.scrum.org/resources/what-is-sprint-planning
Who can cancel a Sprint?
(choose the best answer)
The Product Owner is the sole person responsible for managing the Product Backlog and ensuring that the value of the work the Scrum Team performs is understood by everyone involved. The Product Owner is the only person who can cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master1. A Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense1. Reference:
Scrum Guide
Sprint Cancellation
Can Scrum Master cancel a sprint?
Which metrics will help a Product Owner determine if a product is delivering value?
(choose the best two answers)
The metrics that will help a Product Owner determine if a product is delivering value are customer satisfaction and time to market. This is because:
Customer satisfaction is a measure of how well the product meets the needs and expectations of the customers5. It reflects the value proposition of the product and the feedback from the users.
Time to market is a measure of how quickly the product can be delivered to the market. It reflects the agility and responsiveness of the Scrum Team and the ability to deliver value early and often.
Other metrics, such as productivity, velocity, and percentage of scope implemented, are not directly related to value delivery. They may indicate how efficiently or effectively the Scrum Team is working, but they do not necessarily reflect how valuable or desirable the product is for the customers or stakeholders.
Professional Scrum Product Owner Training, page 5, section ''Product Value''
Professional Scrum Product Owner Training, page 6, section ''Product Vision''
Professional Scrum Product Owner Training, page 7, section ''Product Backlog Management''
Professional Scrum Product Owner Training, page 8, section ''Release Management''
Professional Scrum Product Owner Training, page 9, section ''Business Strategy''
Professional Scrum Product Owner Training, page 10, section ''Stakeholders & Customers''
The Product Owner is the person who will be held accountable if a product does not achieve its
goals or deliver value. Does this mean that the Product Owner has final say over the Definition
of Done?
(choose the best answer)
The Definition of Done is a shared understanding of what it means for work to be complete, and to ensure transparency. The Scrum Guide states that 'The Developers are required to conform to the Definition of Done, as defined by the Scrum Team. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done.'1 This means that the Product Owner does not have the final say over the Definition of Done, but rather collaborates with the Developers and the Scrum Master to agree on the quality standards and expectations for the product.
1: The Scrum Guide2, page 14
2: The Scrum Guide
Exam domains verified against: Official Scrum PSPO-I exam guide, last checked September 2026.
Master the foundational concepts of Scrum including Empiricism, the Scrum Team structure, all four Events, the three Artifacts, and the Definition of Done. This domain ensures you grasp how Scrum works as a complete system and how its events and artifacts create transparency and enable inspection and adaptation.
Focus on fostering Self-Managing Teams and understand how autonomy and collaboration enable teams to self-organize effectively. This domain emphasizes your role in creating an environment where teams continuously improve and take ownership of their work and outcomes.
Develop expertise in Forecasting and Release Planning, Product Vision, Product Value, Product Backlog Management, Business Strategy, and engaging Stakeholders and Customers. This domain covers how Product Owners deliver strategic, customer-focused, and value-driven product development.
Common questions about the exam itself
