Free Practice Questions for Scrum PSPO-II Exam

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.

= As a Product Owner, you are accountable for maximizing the value of the product and the work of the Developers. To do this, you need to have a clear vision of the product and its target users, as well as a validated understanding of the market opportunities and risks. You also need to collaborate with stakeholders and customers to align their expectations and feedback with the product goals and strategy.

In this scenario, you face a dilemma between pursuing a new market segment or satisfying the existing customers. Both options have potential value, but also uncertainty and trade-offs. The best way to proceed is to devise an experiment that will help you to test your assumptions and learn more about the new market and its potential. This could be a small-scale release, a prototype, a survey, or any other method that can provide you with empirical evidence and feedback. By doing this, you can reduce the risk of investing in a feature that may not deliver the expected value, and also gain insights that can help you to refine your product vision and backlog.

This approach is consistent with the principles of agile product management, which emphasize delivering value early and often, validating hypotheses with data, and adapting to changing customer needs and market conditions. It also demonstrates your ability to apply the Scrum values of openness, courage, and respect, as you are willing to explore new possibilities, challenge your own opinions, and involve your stakeholders and customers in the decision-making process. References := Scrum Guide, Managing Products with Agility, Evidence-Based Management

 The smallest product Increment that is valuable enough to release is one that delivers a single new or improved outcome for the customers or users of the product. This is because the outcome is the ultimate measure of value, not the output or the features1. An outcome is a change in behavior, attitude, or situation that results from using the product2. An outcome can be achieved by delivering a single feature, fixing a defect, or improving an existing functionality, as long as it meets the Definition of Done and the Sprint Goal3. Therefore, the best answer is A.

The other options are not correct because:

B. Adds a new feature. This is not a sufficient condition, as a new feature may not deliver a valuable outcome if it is not aligned with the product vision, the customer needs, or the market conditions4.

C. Fixes at least one defect. This is not a necessary condition, as a defect may not affect the value of the product if it is minor, rare, or irrelevant to the customer5.

D. Delivers all “must do” Product Backlog items. This is not a realistic condition, as the Product Backlog is a dynamic and emergent artifact that changes based on feedback, learning, and discovery. There is no fixed set of “must do” items that can guarantee the delivery of value. References: 1: Outcome vs. Output, 2: What is an Outcome?, 3: The Definition of Done, 4: Feature vs. Outcome, 5: Defect vs. Value, : The Product Backlog

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 and 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

According to the Professional Scrum Product Owner™ II certification guide1, the Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed and what standards were met as part of the Increment. If the Definition of Done is not met, the Increment is not Done and cannot be released. Therefore, the following statements are true:

A. The next Sprint may be interrupted when quality issues are encountered. This is true because the Scrum Team may have to spend time fixing the quality issues in the previous Increment before working on the new Sprint Backlog items. This may affect the Sprint Goal and the delivery of value.

C. The indication of progress on the Product Backlog is not transparent. This is true because the Product Backlog items that were supposedly Done in the previous Sprint are actually not Done according to the Definition of Done. This means that the Product Owner cannot accurately forecast the release plan and the stakeholders cannot trust the progress reports.

D. The Scrum Team should not release the Increment. This is true because releasing an Increment that does not meet the Definition of Done may compromise the quality, usability, and value of the product. It may also damage the reputation and trust of the Scrum Team and the organization.

E. The incomplete Sprint Backlog items should be returned to the Product Backlog. This is true because the Sprint Backlog items that were not Done according to the Definition of Done are still part of the Product Backlog. The Product Owner should re-order them based on their value and priority and decide when to include them in the next Sprint.

The following statement is false:

B. The project manager cannot effectively update the plan. This is false because there is no project manager role in Scrum. The Product Owner is responsible for managing the Product Backlog and the value delivery, while the Scrum Master is responsible for facilitating the Scrum process and removing impediments. The Developers are responsible for managing the Sprint Backlog and the quality of the Increment.

 1: Professional Scrum Product Owner™ II Certification | Scrum.org

In earlier versions of the Scrum Guide, the Daily Scrum was structured around three specific questions:

What did I do yesterday?

What will I do today?

What impediments are blocking my progress?

However, the latest Scrum Guide (2020 and beyond) no longer prescribes these questions. Instead, it emphasizes that the Daily Scrum is an event for the Developers to inspect progress toward the Sprint Goal and adapt their plan as necessary.

Why the Answer is E (None of the Above):

Scrum no longer mandates specific questions for the Daily Scrum.

The focus is on progress toward the Sprint Goal, not on individual work tracking.

Developers decide how they structure the discussion to improve collaboration and planning.

Time spent (Option D) is not relevant to Scrum’s empirical approach, which values outcomes over effort tracking.

Key Scrum Guide Principles Supporting This Answer:

" The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work. "

" The Daily Scrum is not a status meeting; it is an event to inspect progress and adapt the Sprint Backlog as needed. "

Conclusion:

The Scrum Guide does not require specific questions at the Daily Scrum, making Option E ( " None of the above " ) the correct answer.

 The Scrum framework encourages the delegation of tasks to promote team ownership and efficiency. Delegating tasks like detailing Product Backlog items, interviewing users, and analyzing data to Developers allows the Product Owner to focus on value maximization and leverage the skills of the Developers12. This approach aligns with the Scrum principle of self-organization and empowerment of the Development Team.

 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

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.

According to the Scrum Guide, the Scrum Team consists of one Scrum Master, one Product Owner, and Developers. The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint1. The Increment is a concrete step toward achieving the Product Goal, and it must meet the Definition of Done and be usable by the stakeholders1. The Product Owner is accountable for maximizing the value of the product and the work of the Developers1. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice, and removing impediments to the Scrum Team’s progress1. The Developers are accountable for creating any aspect of a usable Increment each Sprint1. All three roles must collaborate and coordinate their efforts to deliver the best possible product2.