Scrum PSPO-II Practice Test Questions Answers

Let's break down why the correct answer isCand why the others are incorrect, referencing the Professional Scrum Product Owner™ II (PSPO II) objectives and associated competencies:

C. The Scrum Team is more focused through a common yet specific goal.

Verification:This is thecorrectanswer and aligns perfectly with the purpose of a Sprint Goal as defined in the Scrum Guide and emphasized within the PSPO II competencies.

Explanation and References:

Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the Scrum Framework - Empiricism

The Sprint Goal promotestransparencywithin the team about what they are trying to achieve during the Sprint.

It provides a basis forinspectionduring the Sprint, allowing the team to adapt their plans based on progress toward the Sprint Goal.

Professional Scrum Competency: Managing Products with Agility - Forecasting & Release Planning

The Sprint Goal helps the team focus on achieving a specific, valuable outcome each Sprint.

It provides a basis for forecasting what can be achieved in the Sprint.

Professional Scrum Competency: Managing Products with Agility - Product Value

The Sprint Goal should be aligned with maximizing product value, providing a clear link between the work done in the Sprint and the overall product vision.

Scrum Guide:The Scrum Guide states, "The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Developers1on why it is building the Increment.2[...] During Sprint Planning the Scrum Team also crafts a Sprint Goal. The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog."3This clearly emphasizes that the Sprint Goal provides focus and guidance.  

A. A Sprint Goal ensures that all the Product Backlog items selected for the Sprint are implemented.

Verification:This isincorrect.

Explanation and References:

Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the Scrum Framework - Empiricism

Scrum acknowledges that the plan for the Sprint (what Product Backlog items are chosen) may change as the team learns more during the Sprint.

The Sprint Goal is the commitment, and while the team strives to complete the selected Product Backlog items, the primary focus is on achieving the Sprint Goal, even if it means adapting the plan.

Scrum Guide:While the selected Product Backlog items are the initial plan, the Scrum Guide states, "The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal." This implies that the focus is on the coherent function (represented by the Sprint Goal), not necessarily the completion of every single Product Backlog item.

B. A Sprint Goal only gives purpose to Sprint 1.

Verification:This isincorrect.

Explanation and References:

Professional Scrum Competency: Managing Products with Agility - Forecasting & Release Planning

Every Sprint should have a Sprint Goal, providing ongoing direction and focus for the team.

Scrum Guide:The Scrum Guide explicitly states that a Sprint Goal is crafted during Sprint Planning, implying that it's a necessary component of every Sprint, not just Sprint 1.

D. Sprint Goals are not valuable. Everything is known from the Product Backlog.

Verification:This isincorrect.

Explanation and References:

Professional Scrum Competency: Managing Products with Agility - Product Value

Sprint Goals are crucial for maximizing product value by providing focus and ensuring the team is working on the most important aspectsin each Sprint.

Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the Scrum Framework - Empiricism

The Sprint Goal provides context and purpose beyond the individual Product Backlog items. It helps the team understand the "why" behind the work.

Scrum Guide:The Scrum Guide's emphasis on the Sprint Goal throughout the Sprint lifecycle (planning, daily Scrum, review, retrospective) demonstrates its importance.

In conclusion, the Sprint Goal serves as a unifying and focusing mechanism for the Scrum Team, promoting commitment to a specific outcome within each Sprint and is, therefore, a crucial element for successful Scrum implementation, aligning perfectly with the PSPO II competencies and the Scrum Guide.

B. It helps the Scrum Team keep focus and they can check any decision against it: A well-understood Product Goal acts as a powerful magnet that propels Scrum teams towards value delivery34. It guides efforts, prioritizes activities, fosters collaboration, and ensures focus on delivering value to customers34.

C. It provides overall direction so Sprints will feel less like isolated pieces of work: The Product Goal provides context to the Product Backlog2. It can be thought of as the ‘why’ we are doing all of this work2. It can be used as the elevator pitch to 'what is the Scrum Team working on?'2.

D. It makes it easier to inspect incremental progress at the Sprint Review: As each Increment is produced, the Product incrementally moves toward the Product Goal2. How that value is incrementally determined is very context-specific2.

A. Reorder items in the Product Backlog: The Product Owner is responsible for ordering the Product Backlog to maximize value12.

B. Answer questions from the Developers about items in the current Sprint: The Product Owner is engaged throughout the sprint, answering questions on how things are supposed to function & look4.

E. Gather information and opinions from stakeholders: Gathering information and opinions from stakeholders is a key activity for the Product Owner, as it helps in understanding the value and ordering the Product Backlog

A. Importance to users or customers: The value an item brings to the customer is a key factor in ordering the Product Backlog1.

B. Alignment with organizational strategy and goals: The Product Owner should consider how well an item aligns with the organization’s strategy and goals1.

C. Risk: Business, market, and technology risks are important considerations when ordering the Product Backlog1.

D. Alignment with other Product Backlog items: Dependencies and impact on other items in the Product Backlog should be considered1.

 In Scrum, there is no separate artifact called a project plan. The Product Backlog is the plan for the product development, and it contains all the features, requirements, enhancements, and fixes that are needed to deliver a valuable product. The Product Backlog is not a static or fixed document, but rather an emergent and dynamic one. It is constantly updated and refined by the Product Owner and the Developers as they learn more about the product, the users, the market, and the technology. The Product Backlog is updated whenever new information and insights emerge, which can happen at any time during the product development process. Therefore, option C is the best answer.

Option A is not correct because the Daily Scrum is not a status meeting, but rather a time-boxed event for the Developers to inspect their progress towards the Sprint Goal and adapt their Sprint Backlog accordingly. The Product Owner does not need to update the Product Backlog after the Daily Scrum, unless there is a significant change in the product vision, strategy, or value proposition that affects the Product Backlog items.

Option B is not correct because the Sprint Retrospective is not a time to update the Product Backlog, but rather a time-boxed event for the Scrum Team to inspect their way of working and identify potential improvements. The Product Owner does not need to update the Product Backlog before the Sprint Retrospective, unless there is a need to communicate a change in the Product Goal or the product roadmap that affects the Product Backlog items.

Option D is not correct because the Sprint Planning is not a time to know how much work will have to be done in the Sprint, but rather a time-boxed event for the Scrum Team to collaborate on selecting and planning the Product Backlog items that will deliver the Sprint Goal. The Product Owner does not need to update the Product Backlog before the Sprint Planning, unless there is a need to reorder or clarify the Product Backlog items that are the most valuable and relevant for the upcoming Sprint. References:

Professional Scrum Product Owner II Assessment

Understanding and Applying the Scrum Framework

Managing Products with Agility

What is a Product Backlog?

Product Backlog Explained