Question 1

How often should customer satisfaction be measured? (choose the best answer)

Accepted Answer

A

Explanation: Scrum is founded on empiricism, which emphasizes making decisions based on observation and feedback. Customer satisfaction is a critical measure of the value delivered. To effectively inspect and adapt the product, feedback loops must be short. The Scrum framework facilitates this through events like the Sprint Review, which occurs at least once per month. Measuring customer satisfaction frequently allows the Product Owner and the Scrum Team to validate hypotheses, understand if they are delivering value, and adjust the Product Backlog accordingly. This aligns with the agile principle of continuous improvement and maximizing the value of the product resulting from development.

Question 2

True or False: The Scrum Team is accountable for creating a valuable increment every Sprint.

Accepted Answer

A

Explanation: The 2020 Scrum Guide explicitly states, "The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint." This is a fundamental principle of the framework. The Scrum Team, consisting of the Product Owner, the Scrum Master, and the Developers, is a cohesive, self-managing unit. Their collective accountability ensures a shared focus on delivering a usable and potentially releasable product enhancement during each Sprint. This outcome, the Increment, is the primary measure of progress and a concrete step toward achieving the Product Goal.

Question 3

One of the Scrum events is the Daily Scrum. What are two intended outcomes of the Daily Scrum? (choose the best two answers)

Accepted Answer

D, E

Explanation: The Daily Scrum is a key inspection and adaptation event for the Developers of the Scrum Team. Its primary purpose is to inspect progress toward the Sprint Goal and to create a plan for the next 24 hours of work. This involves improving communication and promoting quick decision-making. A critical part of this process is identifying any impediments that are blocking progress, which allows the team to address them promptly (D). The outcome of this inspection and planning is a shared understanding among the Developers of the most crucial work to tackle next, ensuring they are aligned and can make the best possible progress toward the Sprint Goal (E).

Question 4

Which outcome is expected as a Scrum Team matures? (choose the best answer)

Accepted Answer

B

Explanation: As a Scrum Team matures, it embodies the principle of continuous improvement. The Definition of Done (DoD) is a living artifact that represents the team's shared understanding of the quality required for a Product Increment to be releasable. A mature team continuously seeks to improve its processes and the quality of its output. Therefore, it is expected that they will refine and expand their DoD to include more stringent criteria, such as more comprehensive testing, higher performance standards, or improved documentation. This evolution reflects the team's growing capability and commitment to delivering a high-quality product, which is a hallmark of maturity in Scrum.

Question 5

Who must attend the Daily Scrum? (choose the best answer)

Accepted Answer

C

Explanation: The Daily Scrum is a 15-minute event specifically for the Developers of the Scrum Team. The primary purpose of this event is for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. While other members of the Scrum Team, like the Product Owner and Scrum Master, may attend if invited by the Developers, their presence is not mandatory. The event is owned by the Developers to plan their work for the next 24 hours, making their attendance the only mandatory requirement for the event to be effective and serve its purpose as defined in the Scrum framework.

Question 6

During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog? (choose the best answer)

Accepted Answer

D

Explanation: The Sprint Backlog is a living artifact that represents the Developers' real-time plan for achieving the Sprint Goal. It is not static; it emerges and is updated throughout the Sprint as the Developers learn more about the work required. To maintain transparency and ensure the plan is accurate, any newly identified tasks or the further decomposition of existing work should be reflected in the Sprint Backlog as soon as it is discovered. This continuous adaptation is fundamental to Scrum's empirical nature and is the responsibility of the Developers.

Question 7

As the Developers start work during the Sprint, they realize they have selected too much work to finish in the Sprint. What should they do? (choose the best answer)

Accepted Answer

B

Explanation: The Sprint Backlog is a forecast by the Developers about what functionality will be in the next Increment. It is not a fixed commitment. When the Developers realize they cannot complete all the selected work, they must act with transparency and collaboration. The correct action is to immediately work with the Product Owner to renegotiate the scope of the Sprint Backlog. This allows for a joint decision on which Product Backlog Items are least critical to achieving the Sprint Goal and can be moved out of the current Sprint. This upholds the Scrum values of focus, commitment (to the Sprint Goal), and openness, ensuring the team adapts to new information as soon as it emerges.

Question 8

Which two things should the Scrum Team do during the first Sprint? (choose the best two answers)

Accepted Answer

D, E

Explanation: The fundamental purpose of every Sprint, including the first, is to deliver a tangible outcome. The Scrum Guide mandates that "the entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint." This means the team must produce a "Done," usable version of the product, even if it's a very small slice. To create this Increment (E), the team must build some form of valuable functionality (D). This approach allows the team to test its processes, validate assumptions, and provide stakeholders with a concrete product to inspect and adapt from the very beginning, embodying the empirical nature of Scrum.

Question 9

What are three advantages of a Product Owner sharing a clearly defined Product Goal with the Scrum Team? (choose the best three answers)

Accepted Answer

C, D, E

Explanation: The Product Goal, a commitment for the Product Backlog, describes a future state of the product that serves as a long-term objective for the Scrum Team. A clearly defined Product Goal provides a strategic context and direction, ensuring that each Sprint is a deliberate step toward a larger objective rather than an isolated effort (C). It acts as a crucial focusing mechanism, allowing the team to prioritize work and make decisions by constantly evaluating if they contribute to this goal (D). During the Sprint Review, the Product Goal is the benchmark against which the increment and overall progress are inspected, facilitating a more meaningful discussion with stakeholders about future steps (E).

Question 10

When should the Product Owner update the project plan? (choose the best answer)

Accepted Answer

B

Explanation: Scrum does not use a traditional, static project plan. Instead, the Product Backlog serves as the single, authoritative plan for the product. It is an emergent and dynamic artifact that evolves throughout the product's lifecycle. The Product Owner is responsible for managing this backlog, which involves continuously updating and re-ordering it as new information, market feedback, and stakeholder insights become available. This ensures the plan always reflects the most current understanding of what is needed to maximize the product's value.

Question 11

True or False: Multiple Scrum Teams working on the same product must have the same Sprint start date.

Accepted Answer

B

Explanation: The Scrum Guide does not mandate that multiple Scrum Teams working on the same product must have the same Sprint start date. While aligning Sprints is a highly recommended practice to facilitate the integration of work into a single, valuable Increment each Sprint, it is not a formal rule within the core Scrum framework. The Scrum Guide is intentionally non-prescriptive on this point, allowing teams to determine the best approach for their context. Specific scaling frameworks built upon Scrum, such as Nexus, do enforce this rule to manage dependencies and integration, but it is not a requirement of Scrum itself.

Question 12

True or False: During the Sprint Review the stakeholder's role is to reorder the Product Backlog.

Accepted Answer

B

Explanation: The Product Owner is the sole person accountable for managing the Product Backlog, which explicitly includes ordering its items. During the Sprint Review, stakeholders inspect the Increment and provide valuable feedback. This collaboration and feedback are crucial inputs that the Product Owner uses to determine future adaptations and reorder the Product Backlog. However, the stakeholders' role is to provide input and collaborate, not to perform the action of reordering themselves. The final accountability for the order of the Product Backlog rests with the Product Owner.

Question 13

Who is responsible for the sizing of Product Backlog items? (choose the best answer)

Accepted Answer

D

Explanation: According to the principles of Scrum, the individuals who will perform the work are responsible for estimating the effort required. This accountability lies with the Developers. However, for an estimate to be meaningful, the Developers must have a sufficient understanding of the Product Backlog item (PBI). This clarity is achieved through discussion and collaboration with the Product Owner, who is responsible for the PBI's content and acceptance criteria. Therefore, the most accurate description of this process is that the Developers perform the sizing after clarifying the requirements with the Product Owner. This ensures the estimate is based on a shared understanding of the work.

Question 14

The Scrum Master observes the Product Owner struggling with ordering the Product Backlog. What is an appropriate action for the Scrum Master to take? (choose the best answer)

Accepted Answer

A

Explanation: The Scrum Master's role is to be a servant-leader and coach, ensuring Scrum is understood and enacted. When the Product Owner struggles, the Scrum Master should coach them on the underlying principles rather than doing the work for them or prescribing a specific solution. Reminding the Product Owner that the primary goal of ordering the Product Backlog is to maximize the value delivered by the Developers is the most appropriate coaching action. This empowers the Product Owner to improve their own skills and fulfill their accountabilities, reinforcing the principles of self-management and empiricism within the Scrum Team.

Question 15

How much time is required after a Sprint to prepare for the next Sprint? (choose the best answer)

Accepted Answer

D

Explanation: The Scrum framework prescribes a continuous flow of development through consecutive Sprints. The conclusion of one Sprint, marked by the Sprint Retrospective, is immediately followed by the start of the next Sprint with its Sprint Planning event. There are no gaps or intermediate phases between Sprints. This continuous cycle maintains momentum, provides a consistent rhythm for the Scrum Team, and ensures that opportunities to inspect and adapt are never delayed. Activities like backlog refinement and planning for the next Sprint occur during the current Sprint, not in a break between them.

Free SCRUM PSPO-I Actual Exam Questions