PSPO-I Exam Dumps - Scrum PSPO Questions and Answers

The Scrum Team is a self-managing unit that organizes its own work and delivers a valuable product1. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers2. The Scrum Team is accountable for creating a valuable, useful Increment every Sprint[3][3]. If a Developer is having conflicts with other team members that affect the delivery of the Increment, the Scrum Team is responsible for resolving the issue and deciding whether to remove the Developer from the team or not. The Product Owner, the Scrum Master, and the hiring manager do not have the authority to remove a Developer from the Scrum Team, as this would violate the principle of self-management4.

References:

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

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

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

4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

 The timebox for the Sprint Review is four hours for a one-month Sprint. This is because:

• The Sprint Review is an event where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog if needed. The purpose of the Sprint Review is to elicit feedback and foster collaboration.
• The timebox for each Scrum event is proportional to its frequency and duration. A one-month Sprint corresponds to a maximum calendar month.
• The timebox for a one-month Sprint Review is four hours. For shorter Sprints, it is usually shorter.
• The timebox ensures that there is enough time to inspect what has been done in relation to what could be done next and make any necessary adaptations to optimize value.

Other options, such as two hours for a one-month Sprint, one day, or as long as needed, are not valid answers as they do not reflect the correct timebox for the Sprint Review.

References:

• [Scrum Guide], page 17, section “Sprint Review”
• [Scrum Guide], page 9, section “Sprint”
• [Scrum Guide], page 9, section “Timeboxing Scrum Events”

The Scrum Guide states that "Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint."1 This means that there is no gap or break between Sprints, and the Scrum Team does not need to spend extra time to prepare for the next Sprint. The Scrum Team should be able to start the next Sprint Planning right after the Sprint Review and Sprint Retrospective of the previous Sprint. The Scrum Team should also ensure that the testing and documentation of the work are done within the Sprint, and not left for later.

References:

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

• 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.

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Customer Satisfaction: https://www.agilealliance.org/glossary/customer-satisfaction/

The Scrum Master is a servant-leader for the Scrum Team, who helps the team understand and enact Scrum values, principles, and practices1. The Scrum Master also facilitates Scrum events as requested or needed2. The Daily Scrum is a 15-minute event for the Developers to inspect their progress toward the Sprint Goal and adapt the Sprint Backlog as necessary[3][3]. It is a key opportunity for the Developers to plan their work for the next 24 hours and collaborate on any challenges or impediments4. The Scrum Master should coach the team on the purpose and value of the Daily Scrum, and help them find ways to make it more effective and enjoyable. The Scrum Master should also learn why the Developers want to reduce the frequency of the Daily Scrum, and work with them to address any underlying issues or concerns. The Scrum Master should not impose a decision on the team, nor delegate the decision to a vote, as these actions would undermine the self-management and empowerment of the Developers5.

References:

• 1: The Scrum Guide, November 2020, p. 7
• 2: The Scrum Guide, November 2020, p. 11
• [3][3]: The Scrum Guide, November 2020, p. 10
• 4: Understanding and Applying the Scrum Framework, Scrum.org, accessed on December 16, 2023

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 Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of truth for the Scrum Team and the stakeholders. It contains all the requirements, features, functions, enhancements, fixes, and anything else that can deliver value to the customers and users of the product.
• All types of requirements are acceptable on a Product Backlog, as long as they are aligned with the product vision and goals, and they are transparent, clear, and valuable. The Product Backlog can include stability requirements, performance requirements, product functionality, documentation, fixes, or any other aspects that contribute to the quality and usability of the product.
• 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.

References:

• Scrum Guide: https://www.scrumguides.org/scrum-guide.html
• Product Backlog: https://www.scrum.org/resources/what-is-a-product-backlog

 The Product Owner orders the Product Backlog items according to various criteria, such as:

• The value of Product Backlog items. The Product Owner aims to maximize the value of the product and the work of the Scrum Team. Therefore, they prioritize the items that deliver the most value to the stakeholders and the users, considering factors such as customer satisfaction, market share, revenue, social impact, etc.
• The dependencies between Product Backlog items. The Product Owner tries to minimize the dependencies between items, as they may create complexity, uncertainty, and risk. Therefore, they order the items in a way that reduces or eliminates the dependencies, or resolves them as early as possible.
• The dependencies to other products. The Product Owner also considers the dependencies that the product has to other products, such as platforms, frameworks, libraries, services, etc. Therefore, they order the items in a way that aligns with the availability and compatibility of those products.

References:

• 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 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.”

The Scrum Guide states that “Sprints are the heart of Scrum where ideas are turned into value”. It also states that “Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint”. Furthermore, it states that “Sprints are limited to one calendar month. When a Sprint’s horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase”. Therefore, the correct answer is B. The other options are not acceptable, as they contradict the Scrum principles of empiricism, self-organization, and adaptation.

References:

• The Scrum Guide, section 3.1. Sprints
• Professional Scrum Product Owner I (PSPO I) Learning Path, section 2.2. The Product Owner and the Sprint

Explanation: 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.

References:

• [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.”