Professional Scrum Product Owner Certification PSPO-II Sample Questions Reliable
Prepare for the Actual Professional Scrum Product Owner PSPO-II Exam Practice Materials Collection
NEW QUESTION # 41
You are a Product Owner for a product with a rapidly declining customer base.
Despite data that indicates the decline is due to a shrinking market, rather than a lack of new features, an influential stakeholder insists on adding more features to attract new customers.
The influential stakeholder also says that if you do not add new features you risk losing your most profitable customer.
Which two of the following actions might you take?
(choose the best two answers)
- A. Acknowledge the views of the influential stakeholder but decline to add more features to the product.
- B. Collaborate with other stakeholders and use a voting system to decide which options should be considered.
- C. Agree with the stakeholder and add features to the Product Backlog as it might increase your customer base.
- D. Collaborate with the stakeholder to run a small experiment to validate their opinion.
Answer: A,D
NEW QUESTION # 42
While working on the current Sprint, the Developers realized that they overestimated the work, selected too much to finish. Likely, they cannot complete all the selected Product Backlog Items within the Sprint.
What should they do now? (choose the best answer).
- A. Get help from another Scrum Team, establish Knowledge Transfer sessions to spread the knowledge.
- B. Dilute the Definition of Done so that the Team can meet and finish all the required Product Backlog Items
- C. The Developers needs to collaborate with the Product Owner as soon as possible to remove some Product Backlog Items.
- D. Wait until the Sprint Review to inform the Product Owner.
Answer: C
NEW QUESTION # 43
Which of the following statements is true about the Product Vision?
(choose the best answer)
- A. None of the above.
- B. It must be completely free from discussions about strategic technology choices.
- C. It is the shared responsibility of the Scrum Team to develop and evolve.
- D. It evolves as the Scrum Team learns more about customers and their needs.
- E. All of the above.
Answer: D
Explanation:
* 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 .
References:
* 1: Product Vision
* 2: Product Owner Accountabilities
* 3: Empiricism
* 4: Stakeholders & 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]
NEW QUESTION # 44
The timebox for the Sprint Review is: (choose the best answer)
- A. 15 minutes
- B. Any length of time needed.
- C. At the end of every Sprint
- D. 4 hours for a 4-week Sprint. Usually shorter for shorter Sprints.
Answer: D
NEW QUESTION # 45
What is typical work for a Product Owner in a Sprint?
(choose the best two answers)
- A. Attend every Daily Scrum to answer functional questions about the Sprint Backlog.
- B. Collaborate with stakeholders, user communities and other Product Owners.
- C. Work with the Developers on Product Backlog refinement.
- D. Create financial reporting upon the spent hours reported by the Developers.
- E. Update the work plan for the Developers on a daily basis.
Answer: B,C
Explanation:
Explanation
As a Product Owner, you are accountable for maximizing the value of the product and the work of the Scrum Team. To do this, you need to collaborate with various stakeholders, user communities and other Product Owners to understand their needs, expectations and feedback, and to align them with the product vision and strategy. You also need to work with the Developers on Product Backlog refinement, which is an ongoing activity to add detail, estimates and order to Product Backlog items. This helps the Developers to understand what is valuable and feasible to deliver in the upcoming Sprints, and to plan and execute their work accordingly. These are typical and essential work for a Product Owner in a Sprint.
The other options are not typical or effective work for a Product Owner in a Sprint. Attending every Daily Scrum is not necessary, as the Daily Scrum is an event for the Developers to inspect their progress and plan their next steps. The Product Owner can attend the Daily Scrum if invited by the Developers, but should not interfere or answer questions that are not related to the Sprint Goal or the Product Backlog. Creating financial reporting upon the spent hours reported by the Developers is not a valuable activity, as it does not reflect the outcome or the value delivered by the product. It also goes against the Scrum values of trust and respect, as it implies that the Developers are not self-managing or committed to their work. Updating the work plan for the Developers on a daily basis is also not a good practice, as it undermines the autonomy and creativity of the Developers, and reduces their ability to inspect and adapt their work based on the empirical evidence. The Product Owner should not tell the Developers how to do their work, but rather focus on what is the most valuable outcome for the product.
References:
* Professional Scrum Product Owner™ II Certification
* Understanding and Applying the Scrum Framework
* Managing Products with Agility
NEW QUESTION # 46
The most important thing a Product Owner can do is:
(choose the best answer)
- A. Function as the single source of truth for all requirements.
- B. Ensure that all stakeholder needs are met.
- C. Determine the release schedule and contents.
- D. Maximize the value delivered by the product.
Answer: D
Explanation:
According to the Professional Scrum Product Owner II certification guide1, the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. This means that the Product Owner is responsible for defining, ordering, and validating what the Scrum Team works on, and ensuring that the product delivers value to the customers, users, and the organization. The other options are not the most important thing a Product Owner can do, because they are either too narrow (A), too unrealistic (B), or too prescriptive . References: 1: Professional Scrum Product Owner II Certification | Scrum.org
NEW QUESTION # 47
Experimentation can help a Product Owner to: Select all that apply
- A. Decide whether we should invest and build something
- B. Have complete certainty as to the future success of a Product
- C. Reduce waste
- D. Understand Product / Market fit and if we can create a business around a Product
Answer: A,C,D
NEW QUESTION # 48
Sharing people with unique skills across multiple teams will likely result in which of the following conditions?
(choose the best answer)
- A. Teams do not have to develop deep technical skills.
- B. More work gets done since people are better utilized.
- C. Costs are lower since expensive resources are shared.
- D. Teams may wait more often, impeding the delivery of value.
Answer: D
Explanation:
Explanation
Sharing people with unique skills across multiple teams will likely result in teams having to wait more often for those people to be available, impeding the delivery of value. This is because those people will have to context-switch between different teams, products, and domains, reducing their focus and efficiency1. Moreover, sharing people with unique skills will create bottlenecks and dependencies in the delivery process, increasing the risk of delays and quality issues2. Furthermore, sharing people with unique skills will discourage teams from developing deep technical skills themselves, making them less cross-functional and self-organizing3. Therefore, the best answer is A.
The other options are not correct because:
* B. Teams do not have to develop deep technical skills. This is not a desirable condition, as it contradicts the Scrum value of commitment and the principle of continuous improvement. Teams should strive to develop deep technical skills to deliver high-quality products and to respond to changing requirements and technologies4.
* C. Costs are lower since expensive resources are shared. This is not necessarily true, as the costs of context-switching, waiting, and quality issues may outweigh the benefits of sharing resources. Moreover, this option implies a resource-oriented mindset, rather than a value-oriented mindset, which is not aligned with the Scrum framework and the Product Owner role5.
* D. More work gets done since people are better utilized. This is not a valid measure of success, as the amount of work done does not reflect the value delivered. Moreover, this option implies a utilization-oriented mindset, rather than an outcome-oriented mindset, which is not aligned with the Scrum framework and the Product Owner role. References: 1: Context Switching, 2: Bottlenecks and Dependencies, 3: Cross-Functional Teams, 4: Technical Excellence, 5: Resource vs. Value Orientation, :
Utilization vs. Outcome Orientation
NEW QUESTION # 49
How should multiple Scrum Teams, working together on the same product, select the Product Backlog Item for their teams? (choose the best answer)
- A. The Developers pull in work in agreement with the Product Owner.
- B. The Scrum Team with the highest velocity is prioritized to pick up the Product Backlog Item first.
- C. Share the number of the Product Backlog Item equally to all teams.
- D. The Product Owner proactively assigns the Product Backlog Item to each team.
Answer: A
NEW QUESTION # 50
The smallest product Increment that is valuable enough to release is one that:
(choose the best answer)
- A. Delivers a single new or improved outcome.
- B. Delivers all "must do" Product Backlog items.
- C. Adds a new feature.
- D. Fixes at least one defect.
Answer: A
Explanation:
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
NEW QUESTION # 51
Which of the following might be considered when ordering Product Backlog items?
(choose all that apply)
- A. Cost of delay.
- B. Dependencies between Product Backlog items.
- C. Dependencies to other products.
- D. Cost of implementation.
- E. Value of Product Backlog items.
Answer: A,B,C,D,E
Explanation:
According to the PSPO II guide and Scrum.org competencies, when ordering Product Backlog items, a Product Owner should consider various factors to maximize the value of the work done by the Scrum Team.
These factors include:
A: Dependencies to other products: Recognizing dependencies to other products is crucial for the Product Owner to ensure that the Scrum Team is working on items that can be completed and deliver value without being blocked by external dependencies.
B: Value of Product Backlog items: The primary role of a Product Owner is to maximize the value delivered by the Scrum Team, and ordering items based on their value is a fundamental aspect of this responsibility.
C: Dependencies between Product Backlog items: Understanding and managing dependencies between Product Backlog items helps in planning Sprints more effectively, ensuring that the team is working on items in a logical sequence.
D; Cost of delay: The cost of delay is a critical economic factor that influences the ordering of Product Backlog items. Items that would result in a higher cost if delayed should be prioritized.
E: Cost of implementation: While value maximization is the goal, the cost of implementation cannot be ignored. Balancing the cost and the expected value is essential for effective Product Backlog management.
These considerations are in line with the Scrum.org Professional Scrum competencies, particularly under
'Managing Products with Agility', where it's emphasized that Product Owners should have a deep understanding of market value, product feasibility, and the importance of making trade-offs to maximize value.
NEW QUESTION # 52
Negative value can be in the form of _________(choose ALL that apply)
- A. Decreasing system performance
- B. New defects
- C. Increasing system downtime
- D. Rendering a feature no longer usable
- E. A clunkier user interface
Answer: A,B,C,D,E
NEW QUESTION # 53
What typically happens if Product Backlog items are not sufficiently clear during Sprint Planning?
(choose the best answer)
- A. The meeting is cancelled so refinement can be done first.
- B. The Developers will have difficulty creating a forecast of work for the Sprint.
- C. Nothing, so long as the Product Owner gives the Developers a clear Sprint Goal.
- D. The Scrum Master should not allow this to happen. Look for a new Scrum Master and re-start the Sprint.
- E. Nothing in particular.
Answer: B
Explanation:
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
NEW QUESTION # 54
You have been a Product Owner at a new company for a few weeks. It has become clear to you that many people, both inside and outside the Scrum Team, expect close involvement in the decisions that you, as a Product Owner, are accountable for.
As a result, you find that it takes too long to make decisions. Which of the following are reasonable options you could take?
(choose the best three answers)
- A. Create and share a delegation board that displays your decision-making areas and work with your Scrum Team to clarify decision making accountability and responsibility.
- B. Demonstrate, with the help of data, how long it is taking you to make decisions and the impact that the long decision-making cycle has on delivering value to the customer.
- C. Start making all the decisions without consulting the others who have expressed interest.
- D. Work with your Scrum Master to better understand what next steps you can take to move the company's understanding of product ownership up in the maturity curve towards Entrepreneur.
- E. Allow other members of the Scrum Team and stakeholders to continue making decisions they are not accountable for; documenting which decisions do not deliver the intended value.
Answer: A,B,D
Explanation:
Explanation
As a Product Owner, you are responsible for making decisions that maximize the value of the product and align with the product vision and strategy. However, you also need to collaborate with the Scrum Team and the stakeholders, and respect their input and feedback. Making decisions without consulting them or allowing them to make decisions they are not accountable for can lead to confusion, conflict, and waste. Therefore, options A and B are not reasonable.
Option C is a reasonable option because it helps you communicate your decision-making areas and delegate some decisions to the appropriate level of the organization. A delegation board is a tool that shows who has the authority to make which decisions, and how much involvement is expected from others. By creating and sharing a delegation board, you can clarify your role as a Product Owner, empower the Scrum Team and the stakeholders, and reduce the time and effort spent on decision making.
Option D is also a reasonable option because it helps you improve the company's culture and mindset towards product ownership. As a Product Owner, you need to act as an entrepreneur, who is able to innovate, experiment, and validate assumptions. However, not all organizations are ready to support this kind of product ownership, and some may have a more traditional or bureaucratic approach. Working with your Scrum Master, you can identify the gaps and barriers that prevent you from being an effective Product Owner, and take steps to overcome them. For example, you can educate and coach the organization on the benefits of agile product management, create a shared product vision and roadmap, and foster a culture of trust and transparency.
Option E is another reasonable option because it helps you demonstrate the value of your decisions and the cost of delay. As a Product Owner, you need to use data and evidence to support your decisions and measure their impact. By showing how long it is taking you to make decisions and how that affects the delivery of value to the customer, you can justify your choices and persuade others to support them. You can also use data to identify the most important and urgent decisions, and prioritize them accordingly. This way, you can avoid analysis paralysis and focus on delivering value faster and more frequently.
NEW QUESTION # 55
Experimentation can help a Product Owner to: (select all that apply)
- A. Understand the Product/Market fit and business viability of a product.
- B. Make decisions on whether to invest and build something.
- C. Have complete certainty as to the future success of a product.
- D. Reduce waste
Answer: A,B,D
NEW QUESTION # 56
Your stakeholders are very demanding and each of them has at least one feature that they say is essential for the next release. As the Product Owner, you have validated that the feature requests are all valid requests and would likely add value to your product. What should you do?
(choose the best answer)
- A. Escalate to the steering committee to make the call.
- B. Wait until all essential features are complete before releasing the product.
- C. Release when you can satisfy at least a single outcome, even though not all features are implemented.
- D. Pick the two most influential stakeholders and satisfy their needs, then release.
Answer: C
Explanation:
Let's analyze each option and determine the best course of action for a Product Owner in this situation, keeping in mind the PSPO II objectives and competencies:
* C. Release when you can satisfy at least a single outcome, even though not all features are implemented.
* Verification: This is the correct answer.
* Explanation and References:
* Professional Scrum Competency: Managing Products with Agility - Product Value
* This option aligns with the principle of maximizing value by delivering value early and often.
* It emphasizes focusing on valuable outcomes rather than just completing a list of features.
* Professional Scrum Competency: Managing Products with Agility - Business Strategy
* Releasing a product increment that provides value allows for faster feedback and learning, which can inform future decisions and help to align the product with the overall business strategy.
* Professional Scrum Competency: Managing Products with Agility - Stakeholders & Customers
* While stakeholder management is important, focusing on delivering a valuable outcome is a better way to manage expectations and build trust in the long term.
* Scrum Guide: The Scrum Guide emphasizes the importance of delivering a "Done", usable, and potentially releasable product Increment every Sprint. This aligns with the concept of releasing when a valuable outcome is achieved.
* Additional Explanation: By focusing on outcomes, the Product Owner can prioritize the most valuable features that contribute to that outcome. This may mean that not all stakeholder requests are met in the initial release, but it allows for delivering value sooner and adapting based on feedback.
* A. Wait until all essential features are complete before releasing the product.
* Verification: This is incorrect.
* Explanation and References:
* Professional Scrum Competency: Managing Products with Agility - Product Value
* This approach delays the realization of value and increases the risk of building the wrong thing.
* Professional Scrum Competency: Managing Products with Agility - Forecasting & Release Planning
* Waiting for all features delays feedback and learning, making it difficult to adapt the product to changing market conditions or user needs.
* Scrum Guide: This contradicts the iterative and incremental nature of Scrum, where the goal is to deliver value frequently.
* B. Pick the two most influential stakeholders and satisfy their needs, then release.
* Verification: This is incorrect.
* Explanation and References:
* Professional Scrum Competency: Managing Products with Agility - Product Value
* Prioritizing based on influence rather than value can lead to building the wrong product.
* Professional Scrum Competency: Managing Products with Agility - Stakeholders & Customers
* While stakeholder management is important, the Product Owner's primary responsibility is to maximize product value, not to cater to the most influential stakeholders.
* Additional Explanation: This approach can damage trust with other stakeholders and create a political environment rather than a collaborative one.
* D. Escalate to the steering committee to make the call.
* Verification: This is incorrect.
* Explanation and References:
* Professional Scrum Competency: Evolving the Agile Organization - Portfolio Planning
* The Product Owner is empowered to make decisions about the product and should not routinely escalate prioritization decisions.
* Professional Scrum Competency: Understanding and Applying the Scrum
Framework - Applying the Scrum Framework - Self-Managing Teams
* The Product Owner is accountable for maximizing the value of the product.
Escalating to a steering committee undermines this accountability.
* Additional Explanation: This approach undermines the Product Owner's authority and can lead to delays and inefficient decision-making.
In conclusion, the best approach is to release when a valuable outcome can be achieved, even if not all requested features are implemented. This aligns with the principles of iterative development, value maximization, and frequent feedback, all of which are core to Scrum and emphasized in the PSPO II competencies.
NEW QUESTION # 57
Which of the following activities should a Product Owner never do?
(choose the best answer)
- A. Accept work done during the Sprint.
- B. Establish a Product Goal.
- C. Decide when to release the product Increment.
- D. Dictate the Sprint Goal.
Answer: D
Explanation:
According to the Professional Scrum Product Owner II certification guide1, the Sprint Goal is the single objective for the Sprint. It is a commitment made by the Scrum Team during Sprint Planning. The Sprint Goal provides guidance to the Developers on why it is valuable to build a coherent Increment. The Product Owner proposes how the product could increase its value and utility in the current Sprint. The whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders. The Product Owner should not dictate the Sprint Goal, but rather collaborate with the Developers and the Scrum Master to create a shared understanding and alignment. The other options are not activities that a Product Owner should never do, because they are either part of the Product Owner's accountabilities (A, C, D) or may be done in collaboration with others (A, D). References: 1: Professional Scrum Product Owner II Certification | Scrum.org
NEW QUESTION # 58
What is a benefit of frequent product releases? (choose the best answer)
- A. None of the above.
- B. They enable teams to inspect and adapt more frequently
- C. They help teams better understand and meet customer needs.
- D. They help teams to learn how to correct and eliminate errors.
- E. All of the above
- F. Smaller, more frequent releases are less risky
Answer: E
NEW QUESTION # 59
Which of the following are characteristics of a Product Goal?
(choose all that apply)
- A. It is a commitment contained in the Product Backlog.
- B. It enhances focus.
- C. It communicates the target future state of the product.
- D. It has the approval of all stakeholders.
- E. It provides a long-term objective for the Scrum Team to plan against.
- F. It forms a contract with the business, allowing change to be better managed.
Answer: A,B,C,E
Explanation:
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. References:
* 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
NEW QUESTION # 60
......
Ace Scrum PSPO-II Certification with Actual Questions Dec 05, 2025 Updated: https://pass4sure.testvalid.com/PSPO-II-valid-exam-test.html