Practice Free PSPO-II Exam Online Questions
An analysis of the customers for your product reveals that you have several different kinds of customers that use your product in very different ways.
What should you do with this insight? (Choose the best answer)
- A . Evaluate building different products to better serve each group.
- B . Do nothing: invest in future features to attract new customers and drive revenue growth.
- C . Keep a single product, but market to the groups differently.
- D . Keep a single product, but make sure each release has something for each group.
C
Explanation:
In Scrum, the Product Owner is responsible for maximizing the value of the product by understanding and addressing customer needs effectively. When faced with multiple customer segments using the product in different ways, the best approach is to market the product differently to each group rather than fragmenting the product into multiple versions or ignoring existing customers.
Option A (Evaluate building different products): While segmentation can sometimes justify creating multiple products, it adds complexity in development, maintenance, and resource allocation. Scrum focuses on delivering incremental value in a single product rather than splitting efforts across multiple versions unless there’s a strong business case.
Option B (Do nothing and invest in future features): This is a risky and reactive approach. Ignoring existing customer groups and only investing in attracting new customers can lead to customer churn and dissatisfaction. A Product Owner should aim for continuous engagement with existing customers to ensure long-term success.
Option C (Keep a single product, but market differently to each group) [Correct Answer]: This aligns with Agile and Scrum principles because it allows the Product Owner to maintain a single product backlog while tailoring marketing messages for different user segments. It helps maximize value delivery without increasing complexity. Instead of fragmenting the product itself, communication and positioning strategies are adjusted to better resonate with different customer types.
Option D (Ensure each release has something for each group): While inclusivity in releases is valuable, forcing every release to cater to all groups can lead to inefficient backlog prioritization. Instead, the Product Owner should balance priorities based on value delivery and strategic goals rather than trying to satisfy all user segments in every release.
Reference: Scrum Guide 2020 C Role of the Product Owner: “The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.”
Scrum Product Ownership Best Practices C Focus on a single Product Backlog and strategic prioritization based on value.
Agile Manifesto C "Responding to change over following a plan" (customer preferences should inform how a product is marketed, not necessarily how it is built).
What activities would a Product Owner typically undertake in the phase between the end of the current Sprint and the next Sprint’s Sprint Planning? (choose the best answer)
- A . Working with the Quality Assurance departments on the Increment of the current Sprint.
- B . There are no such activities. The next Sprint starts immediately after the current Sprint.
- C . Updating the project plan with the stakeholders.
- D . Refining the Product Backlog.
My job as a Product Owner should focus on the following: (choose the best two answers)
- A . Clearly communicating product progress and strategies to customers and stakeholders.
- B . Writing clear, transparent User Stories.
- C . Being with the Developers all the time, just in case they need me to clarify a requirement.
- D . Collaborating with customers and stakeholders to identify the most important product requirements.
A,D
Explanation:
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. A major part of that accountability is working with stakeholders and making sure the Scrum Team is focused on the most valuable work.
Why A is correct:
A Product Owner must actively engage with stakeholders and ensure transparency around the product. While the Scrum Guide does not prescribe a specific reporting style, it clearly places the Product Owner in the role of managing value, aligning stakeholder needs, and making sure the Product Backlog reflects what is most important. Communicating product direction, priorities, and progress to customers and stakeholders is a key part of that responsibility.
Why D is correct:
This is one of the strongest descriptions of Product Owner work. The Product Owner collaborates with customers and stakeholders to understand needs, determine value, and order the Product Backlog accordingly. The Product Owner is accountable for effective Product Backlog management, which includes developing and explicitly communicating Product Backlog items and ordering them to best achieve goals.
Why B is not the best answer:
The Scrum Guide does not require User Stories. Scrum only requires that Product Backlog items be clear enough and ordered appropriately. User Stories are a common technique, but they are not mandated by Scrum. Therefore, “writing clear, transparent User Stories” is not an official Product Owner duty as defined by Scrum.
Why C is incorrect:
The Product Owner should be available to support clarity and decision-making, but Scrum does not say the Product Owner should be with Developers all the time. Scrum promotes self-managing teams, and the Product Owner is one member of the Scrum Team, not a constant on-demand requirement clarifier sitting with Developers at all times.
Reference: 2020 Scrum Guide C Product Owner accountabilities: https://scrumguides.org/scrum-guide.html#product-owner
2020 Scrum Guide C Product Backlog management: https://scrumguides.org/scrum-guide.html#product-backlog
Which of the following are required by Scrum? (choose all that apply)
- A . Burndown chart.
- B . Feature burn-up.
- C . Critical Path Analysis.
- D . Refactoring.
- E . Project Gantt chart.
- F . None of the above.
F
Explanation:
Scrum is a lightweight framework. It defines specific accountabilities, events, artifacts, and commitments, but it does not require any of the items listed in options A through E.
Why F is correct:
None of the listed practices or tools are required by Scrum.
Why A is incorrect:
A burndown chart is a common agile tracking technique, but Scrum does not require it. Teams may use it if helpful, but it is optional.
Why B is incorrect:
A feature burn-up chart is also optional. Scrum does not prescribe burn-up charts or any specific reporting chart.
Why C is incorrect:
Critical Path Analysis comes from traditional project management approaches and is not required by Scrum.
Why D is incorrect:
Refactoring is an excellent engineering practice and often very important for maintaining product quality, but it is not required by the Scrum framework itself. Scrum does not prescribe technical practices.
Why E is incorrect:
A Gantt chart is not required by Scrum. Scrum uses empiricism, iterative delivery, and adaptive planning rather than relying on predictive project scheduling tools as a requirement.
The Scrum Guide only mandates the framework elements of Scrum itself:
Scrum Team accountabilities
Scrum Events
Scrum Artifacts
Artifact Commitments
It does not require specific charts, project-planning tools, or engineering techniques.
Reference: 2020 Scrum Guide C Scrum framework overview: https://scrumguides.org/scrum-guide.html
2020 Scrum Guide C Scrum Events: https://scrumguides.org/scrum-guide.html#events
2020 Scrum Guide C Scrum Artifacts: https://scrumguides.org/scrum-guide.html#artifacts
You are the Product Owner for a product with diverse stakeholders with differing opinions that sometimes conflict.
Your Director of Marketing strongly believes that you should add a major new feature to reach a new market. Your CEO believes that the new feature is too expensive and thinks you should focus on other features to make existing customers happier. The CEO says that as Product Owner it is ultimately your decision.
You think both perspectives have merit, but you cannot do both.
How should you proceed? (choose the best answer)
- A . Devise an experiment that will help the company to better understand the newmarket and its potential.
- B . Trust the Director of Marketing’s opinion and add the features; when revenues increase, you will be vindicated.
- C . Better understand the positions of other stakeholders to gather more information, then make a decision.
- D . Trust the CEO’s opinion and focus on current customers, since you cannot affordunhappy customers.
A
Explanation:
= 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.
Reference: = Scrum Guide, Managing Products with Agility, Evidence-Based Management
Why does a Scrum Team need a Sprint Goal? (choose the best answer)
- A . A Sprint Goal ensures that all the Product Backlog items selected for the Sprint are implemented.
- B . A Sprint Goal only gives purpose to Sprint 1.
- C . The Scrum Team is more focused through a common yet specific goal.
- D . Sprint Goals are not valuable. Everything is known from the Product Backlog.
C
Explanation:
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.
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 . Wait until all essential features are complete before releasing the product.
- B . Pick the two most influential stakeholders and satisfy their needs, then release.
- C . Release when you can satisfy at least a single outcome, even though not all features are implemented.
- D . Escalate to the steering committee to make the call.
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 Reference: 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 and 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 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.
The leading revenue-producing product in your portfolio has:
. High Current Value
. Low Unrealized Value
The product has been losing customers for several years and revenues are down.
Using those two data points and the options below, what is the first action you should take? (choose the best answer)
- A . Increase investment in the product to create greater interest and bring old customers back.
- B . Maintain the product, but begin reducing investment; seek other opportunities for future growth.
- C . Drop the price for the product to attract new customers.
- D . Increase marketing for the product.
B
Explanation:
According to the PSPO II resources, a product with high current value and low unrealized value is in the harvest stage of the product lifecycle1. This means that the product has reached its peak and is facing increasing competition and decreasing customer demand. The best strategy for this stage is to maintain the product quality and customer satisfaction, but reduce the investment in new features or enhancements. The product owner should seek other opportunities for future growth, such as developing new products or exploring new markets23.
Reference: 1: Product Lifecycle Management
2: Product Strategy
3: Evidence-Based Management
If a Product Owner finds themselves with more work to do than they can give attention to, what strategy can help them achieve the things that need to be done? (choose the best answer)
- A . Break the product into components, each with their own Product Owner, and create a "Chief Product Owner" role who is responsible for the integrated product.
- B . Split the Product Owner role into "Business Product Owner" and "Technical Product Owner" roles to spread the work.
- C . Delegate tasks like detailing Product Backlog items, interviewing users, and analyzing data to Developers.
- D . All of the above.
- E . None of the above.
C
Explanation:
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.
How much of the Sprint Backlog must be defined during Sprint Planning? (choose the best answer)
- A . Enough so the Developers can create a forecast of what they can do during the Sprint.
- B . All of the potential work. Sprint Planning is not over until 100% of the work is identified and estimated.
- C . Just enough to understand design and architectural implications.
- D . Just enough tasks for the Scrum Master to be confident in the Developer’s understanding of the Sprint.
A
Explanation:
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal1. The Sprint Backlog is a forecast by the Developers about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment2. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum2. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Developers work through the plan and learn more about the work needed to achieve the Sprint Goal2. The Sprint Backlog is not a commitment to deliver a fixed scope of work, but rather a forecast of what the Developers believe they can do in the Sprint3. Therefore, the Sprint Backlog does not need to be fully defined during the Sprint Planning, but only enough so the Developers can create a realistic forecast of what they can do during the Sprint.
Reference: 1: Sprint Backlog, 2: The Scrum Guide, 3: Commitment vs. Forecast
