PSPO-II Exam Dumps - Professional Scrum Product Owner™ II (PSPO 2)

According to the Scrum Guide, the Developers are accountable for creating a plan for the Sprint, which includes selecting the Product Backlog items that they can deliver in the Sprint1. If they realize that the workload is too high, they have two options: either reduce the scope or increase the capacity. Reducing the scope means removing or changing some of the Product Backlog items, in agreement with the Product Owner, so that the Sprint Goal can still be achieved2. Increasing the capacity means adding more Developers to the team, but this is not recommended, as it can disrupt the team dynamics, lower the quality, and increase the communication overhead3. Therefore, the best actions to take are A and B, as they respect the self-organization and collaboration of the Scrum Team, and allow them to deliver a valuable and potentially releasable Increment at the end of the Sprint4.

The Sprint Retrospective is an event for the entire Scrum Team to inspect how the last Sprint went with regard to individuals, interactions, processes, tools, and their Definition of Done, and then plan improvements for the next Sprint.

The Product Owner is part of the Scrum Team. Therefore, during the Sprint Retrospective, the Product Owner participates as a Scrum Team member.

Why C is correct:

The Scrum Guide explicitly says the Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements. Since the Product Owner is one of the three accountabilities within the Scrum Team, they are expected to participate.

Why A is incorrect:

Capturing requirements for the Product Backlog is not the purpose of the Sprint Retrospective. The Retrospective focuses on team effectiveness, collaboration, processes, tools, and improvements. Product Backlog refinement and stakeholder/value discussions happen elsewhere as needed.

Why B is incorrect:

The Product Owner is part of the Scrum Team, so they should attend the Sprint Retrospective. The event is for the whole Scrum Team, not just Developers or only the Scrum Master.

Why D is incorrect:

The Sprint Retrospective is an internal Scrum Team event focused on improvement. The Scrum Guide does not assign the Product Owner responsibility for summarizing and reporting Retrospective discussions to stakeholders. In practice, Retrospectives are often kept within the team to support openness and honest inspection.

= Based on the Evidence-Based Management (EBM) framework, your product has a high Current Value (CV), which means that it delivers value to the existing customers and meets their needs and expectations. However, it also has a high Unrealized Value (UV), which means that there is a large gap between the potential and actual use of the product in the market. This indicates that your product has a low awareness, reach, or appeal among the potential customers who could benefit from it.

To increase the business performance of the product, you need to reduce the UV and increase the Ability to Innovate (A2I), which is the ability to deliver future value. One way to do this is to improve the marketing of the product, which can help you to communicate the value proposition, differentiate the product from the competitors, and attract a greater number of customers. This can also provide you with more feedback and data to inform your product strategy and backlog prioritization.

The other options are not the best actions to take, because they either do not address the root cause of the high UV, or they may compromise the CV or A2I of the product. Increasing the number of product features may not necessarily increase the value or the demand for the product, and it may also increase the complexity and the cost of development. Releasing an identical product with a new name may confuse the customers and dilute the brand identity, and it may also create legal or ethical issues. Dropping the price for the product may not be a sustainable or profitable strategy, and it may also affect the perceived quality or value of the product. References := Professional Scrum Product Owner™ II Certification, Managing Products with Agility, Evidence-Based Management

 A burndown chart is a graphical tool that shows the amount of work remaining versus time. It is often used to track the progress of a Sprint or a release. The work remaining is usually measured in terms of effort, such as hours or story points, and it is plotted on the vertical axis. The time is measured in terms of days or weeks, and it is plotted on the horizontal axis. The burndown chart starts with the total amount of work at the beginning of the Sprint or release, and it ideally ends with zero work at the end. The slope of the burndown chart indicates the rate of progress, or the velocity, of the Scrum Team12.

The other options are not what burndown charts track. Accumulated cost, accumulated business value, and individual worker productivity are not relevant or useful metrics for Scrum Teams, as they do not reflect the value or the quality of the product. Scrum Teams focus on delivering potentially releasable increments of the product that meet the Definition of Done, and they use empirical feedback to inspect and adapt their work13. References: 1: Understanding and Applying the Scrum Framework 2: Burndown Chart 3: Managing Products with Agility

The primary accountability of a Product Owner within the Scrum framework is to maximize the value of the work that the Scrum Team delivers. This involves managing the Product Backlog, but the overarching responsibility is ensuring that the team’s efforts translate into value

D is correct because the timebox for the Sprint Review is four hours or less for a one-month Sprint, and usually shorter for shorter Sprints1. The Sprint Review is an event where the Scrum Team and the stakeholders inspect the outcome of the Sprint and collaborate on what to do next1. A is incorrect because the Sprint Review is not an open-ended event, but a timeboxed one that respects the attendees’ time and ensures productivity2. B is incorrect because the Sprint Review is not a point in time, but a timeboxed event that has a specific purpose and agenda1. C is incorrect because the Sprint Review is not the same as the Daily Scrum, which is a 15-minute event for the Developers to synchronize their work1.

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. During Sprint Planning.

Verification: This is the correct answer.

Explanation and References:

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

Sprint Planning is the event where the Scrum Team collaboratively plans the work for the upcoming Sprint. Creating the Sprint Backlog is a key part of this event.

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

The Sprint Backlog represents the team ' s forecast of what they believe they can deliver in the Sprint to achieve the Sprint Goal. This forecasting occurs during Sprint Planning.

Scrum Guide: The Scrum Guide states, " The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team. [...] Sprint Planning answers the following questions: What can be Done this Sprint? How will the chosen work get done? " The answer to the second question results in the creation of the Sprint Backlog.  

A. During the Sprint.

Verification: This is incorrect.

Explanation and References:

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

While the Sprint Backlog can be updated during the Sprint as the Developers learn more, it is initially created before the Sprint starts, during Sprint Planning.

Scrum Guide: The Scrum Guide says " The Sprint Backlog is a plan by and for the Developers. 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 Goal. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum. " This means that Sprint backlog is already created before sprint starts.  

B. Prior to Sprint Planning.

Verification: This is incorrect.

Explanation and References:

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

The Sprint Backlog is created during Sprint Planning through collaboration between the Developers and the Product Owner. Before Sprint Planning, the Product Owner prepares a prioritized Product Backlog, but this is not the Sprint Backlog.

Scrum Guide: The Sprint Backlog emerges from the discussion and negotiation that happens during Sprint Planning. It is not pre-defined.

D. At the beginning of the project.

Verification: This is incorrect.

Explanation and References:

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

The Sprint Backlog is specific to each Sprint and is created at the beginning of each Sprint, not at the beginning of the entire project.

Scrum Guide: Scrum is iterative and incremental. Planning the work for the entire project upfront is not in line with Scrum principles. The Sprint Backlog is created anew during each Sprint Planning event.

In conclusion, the Sprint Backlog is created during Sprint Planning, where the Scrum Team collaboratively decides what work they will undertake in the upcoming Sprint and how they will accomplish it, aligning with the PSPO II competencies and the Scrum Guide.

Option D is the best answer because it indicates that the Product Owner and the Scrum Team are not aligned on the vision, goals, and value of the product. The Product Owner is responsible for maximizing the value of the product and the work of the Scrum Team1. To do so, the Product Owner needs to work closely with the Scrum Team, communicate the product vision, provide clear and valuable Product Backlog items, collaborate on the Sprint Goal, and inspect and adapt the product based on feedback23. If the Increment presented at the Sprint Review does not reflect the Product Owner’s expectations, it means that there is a gap between what the Product Owner wants and what the Scrum Team delivers. This gap can lead to waste, rework, dissatisfaction, and missed opportunities. The Product Owner should work more with the Scrum Team to ensure that they have a shared understanding of the product and its value proposition, and that they deliver Increments that meet the Definition of Done and the acceptance criteria45.

Option A is not the best answer because it does not necessarily imply that the Product Owner needs to work more with the Scrum Team. People may leave the Scrum Team for various reasons, such as personal, professional, or organizational factors. While the Product Owner should care about the well-being and motivation of the Scrum Team members, and try to foster a positive and collaborative environment, the Product Owner is not accountable for the people management or the team composition1. The Scrum Master is more likely to address the issues that cause people to leave the Scrum Team, such as impediments, conflicts, or dysfunctions.

Option B is not the best answer because it does not necessarily imply that the Product Owner needs to work more with the Scrum Team. The Product Owner is expected to spend enough time with the Scrum Team to provide them with the necessary guidance and feedback2. However, the Product Owner also has other responsibilities, such as engaging with stakeholders, customers, and users, managing the Product Backlog, validating the product value, and aligning the product strategy with the business goals12. The Product Owner does not need to work full time with the Scrum Team, as long as they are available and accessible when needed, and they empower the Scrum Team to make decisions and self-organize .

Option C is not the best answer because it does not necessarily imply that the Product Owner needs to work more with the Scrum Team. The acceptance criteria for the Product Backlog items are the conditions that must be met for the items to be considered done and valuable. The Product Owner is accountable for defining and communicating the acceptance criteria to the Scrum Team1. However, the Product Owner can also collaborate with the Scrum Team and the stakeholders to refine and clarify the acceptance criteria, and to ensure that they are aligned with the Definition of Done and the Sprint Goal . The acceptance criteria for the Product Backlog items may not appear to be complete at the beginning of the Sprint, but they can be refined and updated throughout the Sprint, as long as they do not change the scope or the value of the items. The Product Owner should work with the Scrum Team to ensure that the acceptance criteria are clear, testable, and valuable, but they do not need to work more with the Scrum Team just because the acceptance criteria are not complete at a certain point in time.

1: Product Owner Accountabilities

2: Product Backlog Management

3: Product Value

4: Product Vision

5: Sprint Review

 Scrum Master Accountabilities

 Stakeholders and Customers

 Business Strategy

 Definition of Done

 Product Backlog Refinement

 Sprint Planning

 Sprint Backlog