Free Practice Questions for Scrum PSPO-II Exam

When multiple Scrum Teams are working on the same product, it is essential that all of their Increments be combined every Sprint. This ensures that the Product Owner and stakeholders can accurately inspect the Increment, which is a fundamental aspect of transparency and empiricism in Scrum1. Combining Increments allows for a clear understanding of the current state of the product, which is crucial for effective inspection and adaptation.

Verified Answer: A, B

Very Very Short Explanation: In the context of Scrum and the PSPO II guidelines, when there is uncertainty about customer needs or market desires, it is recommended to make smaller releases to allow for quicker feedback and adaptation (A), and to increase the focus on validating customer needs to ensure that the product development is aligned with what customers actually want (B). This approach is consistent with the principles of empiricism and agility, which emphasize the importance of transparency, inspection, and adaptation123.

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

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.

Option A is the best answer because it reflects the agile and empirical nature of Scrum and Product Ownership. The Product Vision is a concise and inspiring statement that describes the purpose, direction, and value proposition of the product1. The Product Vision is not a fixed or static document, but rather an emergent and dynamic one that adapts to the changing environment, needs, and feedback. The Product Owner is accountable for creating and communicating the Product Vision to the Scrum Team and the stakeholders2. The Product Owner collaborates with the Scrum Team and the stakeholders to inspect and adapt the Product Vision based on the new insights, opportunities, and learnings that arise from the changing environment34. The Product Owner also uses various techniques, such as product discovery, user research, market analysis, and experiments, to validate and refine the Product Vision5 .

Option B is not the best answer because it contradicts the accountability of the Product Owner. The Product Owner is the sole person responsible for managing the Product Backlog and maximizing the value of the product and the work of the Scrum Team. The Product Owner is also the sole person responsible for creating and communicating the Product Vision to the Scrum Team and the stakeholders2. The Product Owner may seek input and feedback from the Scrum Team and the stakeholders, but the final decision and authority on the Product Vision belongs to the Product Owner. The Scrum Team and the stakeholders are not accountable for developing and evolving the Product Vision, but they are expected to understand and support it .

Option C is not the best answer because it contradicts the reality and complexity of product development. The Product Vision is not a technical specification, but rather a strategic and business-oriented statement that guides the development of the product1. The Product Vision does not prescribe how the product should be built, but rather why and what the product should achieve. However, the Product Vision is not completely detached from the technical aspects of the product, as the technology choices may have an impact on the feasibility, desirability, and viability of the product. The Product Owner should be aware of the strategic technology choices and their implications, and discuss them with the Development Team and the stakeholders, as part of the product discovery and validation process .

1: Product Vision

2: Product Owner Accountabilities

3: Empiricism

4: Stakeholders and Customers

5: Product Discovery

 Product Backlog Management

 The Scrum Guide

 Scrum Team

 Product Value

 Product Feasibility

 Product Validation

[Agile Manifesto]

[User Research]

[Market Analysis]

[Experiments]

Personas are fictional characters that represent the different user types that might use your product or service in a similar way1. Personas can help you to2345:

Understand the needs of a set of users by creating empathy and insight into their goals, behaviors, and pain points.

Formulate hypotheses about product value by identifying the problems and opportunities that your product can address for each user type.

Understand market potential by estimating the size and characteristics of each user segment and their willingness to pay for your product.

Discover key buying triggers by exploring the motivations, influences, and decision-making processes of each user type.

Design and test your product features and user experience by using personas as a guide and a reference point. References:

1: Personas – A Simple Introduction

2: The Complete Guide to User Personas and How They Can Help Your Marketing Strategy (With Examples)

3: Personas | Usability.gov

4: The importance of personas for digital experience

5: Personas | Definition and Overview

If Product Backlog items are not sufficiently clear during Sprint Planning, the Developers will typically have difficulty creating a forecast of work for the Sprint (B). This is because the clarity of the Product Backlog items is crucial for the Developers to understand what is expected and to plan their work accordingly. The Scrum framework emphasizes the importance of a well-refined Product Backlog for effective Sprint Planning

According to the Scrum Guide, the Scrum Team consists of one Scrum Master, one Product Owner, and Developers. There is no distinction between different types of Developers, such as testers, programmers, designers, etc. The Developers are the people who deliver a potentially releasable Increment of “Done” product at the end of each Sprint. They are accountable for creating and adhering to the Definition of Done, ensuring technical excellence and good design, and collaborating with the Product Owner to maximize value1. Therefore, everyone on the Scrum Team is responsible for ensuring the quality of the product, and there is no specific tester role. However, this does not mean that testing skills are not needed or valued. On the contrary, testing is an essential activity that supports the team and critiques the product throughout the development process2. A professional tester can contribute to the Scrum Team by coaching the team on testing techniques, tools, and practices, helping the team to define clear and unambiguous acceptance criteria, challenging the team to consider different scenarios and edge cases, creating and executing test plans, and providing feedback on the product’s usability, performance, security, and other aspects3. A professional tester can also collaborate with the Product Owner to ensure that the product meets the expectations and needs of the stakeholders and users.