PSPO-I Online Practice Questions and Answers

Correct Answer: DE

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

Correct Answer: A

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/

Correct Answer: D

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.

Correct 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 References:

1: The Scrum Guide2, page 7

2: The Scrum Guide

Correct Answer: B

Correct Answer: E

Scrum During the Sprint Retrospective, the Scrum Team discusses how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done123. This includes methods of communication, the way the Scrum Team does Sprint Planning, skills needed to improve the Developers' ability to deliver, and the Definition of Done123.

Correct Answer: A

The Sprint Review is an event that occurs at the end of each Sprint, where the Scrum Team and the stakeholders inspect the Increment and adapt the Product Backlog if needed. The Sprint Review is an opportunity for the Product Owner to validate that the Increment meets their expectations and delivers value to the customers and users. The Sprint Review is also an opportunity for the Developers to demonstrate their work and receive feedback from the Product Owner and the stakeholders. Stakeholders are people external to the Scrum Team who have a stake or interest in the product, such as customers, users, sponsors, managers, or other teams. Stakeholders provide valuable input, feedback, and insights to the Scrum Team regarding the product vision, goals, value proposition, requirements, features, functions, quality, usability, or market conditions. Collecting stakeholder feedback is one of the main purposes of the Sprint Review. Stakeholder feedback can help the Scrum Team to: References: Scrum Guide: https://www.scrumguides.org/scrum-guide.html Sprint Review: https://www.scrum.org/resources/what-is-a-sprint-review Stakeholders: https://www.agilealliance.org/glossary/stakeholders

Correct Answer: BC

In Scrum, there is only one product and one Product Backlog for a given product. The Product Backlog 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. The Product Backlog is ordered by the Product Owner based on the product vision, goals, and value.

Having multiple Product Backlogs for one product would create confusion, duplication, inconsistency, and waste. It would also make it harder to align the Scrum Teams and the stakeholders on the same product direction and priorities.

Therefore, each Scrum Team should not have a separate Product Backlog. 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.

Having multiple Product Owners for one product would create conflicts, overlaps, gaps, and inefficiencies. It would also make it harder to maintain a clear and consistent product vision, strategy, roadmap, and backlog. Therefore, there should

be only one Product Owner for one product.

In some cases, when there are multiple Scrum Teams working on one product, it may be necessary to have some form of scaling or coordination mechanism to ensure alignment and collaboration among the teams. However, this does not

mean that there should be multiple Product Owners or Product Backlogs. Instead, there should be ways to facilitate communication, feedback, integration, and transparency among the teams and with the Product Owner. For example, some

frameworks or practices that can help with scaling Scrum are Nexus, LeSS, SAFe, or Scrum of Scrums.

References:

Scrum Guide: https://www.scrumguides.org/scrum-guide.html Nexus: https://www.scrum.org/resources/what-is-nexus LeSS: https://less.works/

SAFe: https://www.scaledagileframework.com/

Scrum of Scrums: https://www.agilealliance.org/glossary/scrum-of-scrums/

Correct Answer: A

Explanation: The Scrum Guide states that "By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint. Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself."1 This means that the Scrum Team may add the high priority process improvements to the Sprint Backlog for the next Sprint, as part of their plan to deliver the Increment and achieve the Sprint Goal. The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.1 References:

1: The Scrum Guide2, page 16

2: The Scrum Guide

Correct Answer: AD

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.

References:

Professional Scrum Product OwnerTM Training, page 5, section "Product Value" Professional Scrum Product OwnerTM Training, page 6, section "Product Vision" Professional Scrum Product OwnerTM Training, page 7, section "Product

Backlog Management"

Professional Scrum Product OwnerTM Training, page 8, section "Release Management"

Professional Scrum Product OwnerTM Training, page 9, section "Business Strategy"

Professional Scrum Product OwnerTM Training, page 10, section "Stakeholders and Customers"