PSPO-II Exam Questions & Answers

Let's break down why the correct answer is C and 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 the correct answer 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 Reference:

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

The Sprint Goal promotes transparency within the team about what they are trying to achieve during the Sprint.

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

Professional Scrum Competency: Managing Products with Agility - Forecasting and 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 Developers 1 on 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.' 3 This 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 is incorrect.

Explanation and Reference:

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 is incorrect.

Explanation and Reference:

Professional Scrum Competency: Managing Products with Agility - Forecasting and 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 is incorrect.

Explanation and Reference:

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 aspects in 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.

A Product Goal is a summary statement of the desired outcome or value that the product should deliver. It communicates the target future state of the product, which is aligned with the product vision and strategy. It enhances focus by providing a clear direction and purpose for the Scrum Team and the stakeholders. It is a commitment contained in the Product Backlog, which means that it is transparent, visible, and understood by everyone involved in the product development. It provides a long-term objective for the Scrum Team to plan against, which helps them to prioritize and refine the Product Backlog items and to craft the Sprint Goals.

Option D is not correct because the Product Goal does not need to have the approval of all stakeholders. The Product Owner is accountable for the value of the product and the Product Backlog, and therefore has the authority to define and communicate the Product Goal. The Product Owner may collaborate with the stakeholders to discover and validate their needs and expectations, but does not need to seek their consensus or permission for the Product Goal.

Option F is not correct because the Product Goal is not a contract with the business, but rather a flexible and adaptable guide for the product development. The Product Goal is not fixed and immutable, but rather emergent and dynamic. It can be changed or updated as the product evolves and the market conditions change. The Product Goal does not limit or constrain the changes that may occur during the product development, but rather enables and supports them.Reference:

Professional Scrum Product Owner II Assessment

Understanding and Applying the Scrum Framework

Managing Products with Agility

Scrum Guide 2020 Update - Introducing the Product Goal

The Product Goal explained

A ''cone of uncertainty'' is a graphical representation of the evolution of the amount of uncertainty during a project. It shows that at the beginning of a project, there is a high degree of variability and unpredictability in the estimates of the scope, cost, time, and value of the product. As the project progresses, more information and feedback are gathered, and the uncertainty decreases, reaching zero when the product is delivered and validated. A ''cone of uncertainty'' can be used to visualize the uncertainty of the potential value that a Scrum Team delivers over time, and to guide the empirical process of inspection and adaptation. By using a ''cone of uncertainty'', a Scrum Team can:

Align the expectations of the stakeholders and customers with the reality of the complex and dynamic environment.

Avoid making premature or unrealistic commitments based on inaccurate or incomplete estimates.

Embrace change and experimentation as opportunities to learn and deliver more value.

Inspect the actual value delivered and the feedback received, and adapt the product vision, strategy, and backlog accordingly.

Forecast the range of possible outcomes and the level of confidence for each Sprint and release.

The other options are not valid uses of a ''cone of uncertainty''. A ''cone of uncertainty'' does not represent the relative level of difficulty for predicting the velocity of individual team members, as velocity is a measure of the amount of work done by the whole Scrum Team, not by individuals. A ''cone of uncertainty'' does not rapidly identify and prioritize all uncertainties, as uncertainties are not always known or quantifiable, and may change over time. A ''cone of uncertainty'' does not determine whether to cut quality, similar to the ''Iron Triangle'' of project management, as quality is not a variable that can be traded off in Scrum, but a non-negotiable aspect of the Definition of Done and the value proposition of the product.

:

Professional Scrum Product Owner II Certification

Managing Products with Agility

Cone of Uncertainty - Wikipedia

The Product Owner is accountable for effective Product Backlog management. The 2020 Scrum Guide states that this includes creating and clearly communicating Product Backlog items.

So the accountable person is clearly the Product Owner.

Why D is the best answer:

Option D identifies the Product Owner, which is the key official answer. However, the wording about a ''proxy'' is not the exact Scrum Guide wording. The Scrum Guide says the Product Owner may delegate the responsibility to others, but the Product Owner remains accountable. So while the option is not perfectly phrased, it is still the best available answer because it correctly names the Product Owner as the accountable person.

Why A is incorrect:

Developers may help refine, clarify, and break down Product Backlog Items, but they are not the accountable role for clearly expressing them.

Why B is incorrect:

The Scrum Master is not accountable for clearly expressing Product Backlog Items. The Scrum Master helps the Scrum Team understand Scrum and supports effectiveness, but Product Backlog accountability belongs to the Product Owner.

Why C is incorrect:

This wrongly assigns accountability to the Scrum Master. That is not supported by the Scrum Guide.

Why E is incorrect:

Again, this incorrectly makes the Scrum Master accountable.

Important correction to the option wording:

The official Scrum wording is not ''appoint a proxy.'' The correct concept is:

The Product Owner may delegate the work, but remains accountable.

2020 Scrum Guide -- Product Owner: https://scrumguides.org/scrum-guide.html#product-owner

2020 Scrum Guide -- Product Backlog: https://scrumguides.org/scrum-guide.html#product-backlog

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

Professional Scrum Product Owner II Assessment

Understanding and Applying the Scrum Framework

Managing Products with Agility

What is a Product Backlog?

Product Backlog Explained