PSPO-II Exam Dumps - Scrum PSPO Questions and Answers

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 should collaborate with the Developers and the Scrum Master to find the best way to deliver value in the current Sprint, even if the initial forecast is not met. The Product Owner should not change or abandon the Sprint Goal, as it is a commitment made by the Scrum Team during Sprint Planning. The Product Owner should also not skip Product Backlog refinement activities, as they are essential for preparing the Product Backlog for future Sprints. The Product Owner should not end the Sprint prematurely, as it may cause more disruption and waste than delivering a potentially releasable Increment. The Product Owner should not inform management that more resources are needed, as it may imply that the Scrum Team is not self-organizing and cross-functional. The Product Owner should respect the Developers’ autonomy and professionalism and support them in finding the best solution to the problem. Therefore, the best answer is to reduce the scope of the Sprint, if possible, to still meet the Sprint Goal. This means that the Product Owner and the Developers should negotiate the scope of the Sprint Backlog within the Sprint, removing or adding Product Backlog items that are aligned with the Sprint Goal and the value delivery. References: 1: Professional Scrum Product Owner™ II Certification | Scrum.org

Option B is the best answer because it reflects the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is a living artifact that represents the current understanding of what the product needs to be most valuable for the customers and the stakeholders1. The Product Backlog 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 managing the Product Backlog and ensuring that it is transparent, ordered, and refined2. The Product Owner collaborates with the Scrum Team and the stakeholders to inspect and adapt the Product Backlog items based on the new insights, opportunities, and learnings that arise from the changing environment34. The Product Owner also uses various techniques, such as product vision, value proposition, user stories, experiments, and evidence-based management, to define, validate, and prioritize the Product Backlog items5 .

Option A is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a requirements specification document, but rather a list of hypotheses and assumptions that need to be tested and validated in the real world5. The Product Backlog items are not detailed or fixed upfront, but rather refined and clarified as they get closer to implementation2. Updating the requirements specification document to ensure stability implies a plan-driven and predictive approach that does not embrace change and feedback, and that does not optimize value delivery.

Option C is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a project plan, but rather a product roadmap that guides the development of the product. The Product Backlog does not have a predefined end date or scope, but rather evolves and changes as the product grows and matures1. Keeping the Product Backlog the same until the end of the project implies a plan-driven and predictive approach that does not embrace change and feedback, and that does not optimize value delivery.

Option D is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a disposable artifact, but rather a cumulative and iterative one that builds on the previous work and learnings1. The Product Backlog items are not discarded or replaced, but rather refined and updated as the product evolves and changes2. Archiving the Product Backlog and creating a new one implies a disruptive and wasteful approach that does not leverage the existing knowledge and feedback, and that does not optimize value delivery.

1: Product Backlog

2: Product Backlog Management

3: Empiricism

4: Stakeholders and Customers

5: Product Vision

 Product Value

 Evidence-Based Management

[Agile Manifesto]

[Product Roadmap]

 Product Owner Accountabilities

 Sprint Review

 Product Backlog Refinement

[User Stories]

[Value Proposition]

[Experiments]

The value of a product is not determined by how many features it has, how much it costs, or how fast it is delivered, but by how well it meets the needs and expectations of the customers and stakeholders. Therefore, the best measure of value is how often and how effectively the customers use the product to achieve their goals and solve their problems. This can be assessed by using metrics such as customer satisfaction, retention, engagement, loyalty, referrals, revenue, or any other indicators that reflect the desired outcomes and benefits of the product.

The other options are not the best measures of value, because they either focus on the output rather than the outcome, or they do not reflect the customer perspective. The number of “must-do” Product Backlog items delivered in a release may indicate the scope or the quality of the product, but not necessarily the value. The average cost of the product release may indicate the efficiency or the profitability of the product, but not necessarily the value. The on-schedule performance of the Scrum Team may indicate the predictability or the agility of the product development process, but not necessarily the value. References := Professional Scrum Product Owner™ II Certification, Managing Products with Agility, Evidence-Based Management

The Professional Scrum Product Owner™ II (PSPO II) emphasizes the importance of a strategic approach to product management. According to the PSPO II resources, it is essential to:

Continually measure the impact of new investments or marketing efforts for both products (Option A). This aligns with the PSPO II focus on evidence-based management and making decisions based on empirical data.

Invest in Product A to increase its market share, customer satisfaction, and revenue (Option B). The PSPO II materials suggest that a product with a greater potential market but lower customer satisfaction requires attention to improve its standing and capitalize on its market potential.

Investigate an increase in marketing for Product B to grow its market share (Option C). Even though Product B is currently generating more revenue, the PSPO II guides recommend exploring opportunities to expand its market share, which could lead to even greater revenue.

Therefore, a comprehensive investment strategy that includes all the above actions is recommended for managing products with agility, as per the PSPO II guidelines. This approach ensures that both products are given the opportunity to maximize their market potential while maintaining a focus on customer satisfaction and revenue growth. It’s a holistic strategy that considers the different strengths and opportunities of each product.

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

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.

A. Increase transparency: The Definition of Done (DoD) creates transparency by providing everyone a shared understanding of what work was completed and what standards were met as part of the Increment1.

C. Create a shared understanding of when work is complete: The DoD is a shared understanding among the team members of when a product increment is ready for release2.

D. Describe the work that must be done before the Sprint can be declared complete: The DoD includes all of the characteristics and standards an Increment needs to meet in order to be released1. Once the Definition of Done is met, the Increment is Done and can be delivered1.

Self-Management: The Developers have autonomy over how they achieve the Sprint Goal. The Sprint Backlog reflects their plan for turning Product Backlog items into a valuable Increment.

Accountability: The Developers are held accountable for delivering the Sprint Goal, and thus own the detailed plan within the Sprint Backlog.

Scrum Guide: The Scrum Guide explicitly states, " The Sprint Backlog is a plan by and for the Developers "

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are also accountable for effective Product Backlog management, which includes ordering the Product Backlog items to best achieve goals and missions1. The Product Owner should consider various sources of information to make informed decisions about the product, such as customer feedback, market trends, stakeholder input, and data analysis2.

When deciding whether to drop the price of the product, the Product Owner should consider the following sources of information:

Customer satisfaction: The Product Owner should measure and monitor how satisfied the customers are with the product, and how likely they are to recommend it to others. Customer satisfaction is a key indicator of product value and quality, and it can also influence customer retention and loyalty. The Product Owner should use various methods to collect customer feedback, such as surveys, interviews, reviews, ratings, and net promoter score23.

Market share: The Product Owner should track and compare the product’s market share with its competitors and potential customers. Market share is the percentage of the total market that is captured by the product, and it reflects the product’s popularity and demand. The Product Owner should use market research, sales data, and industry reports to analyze the market share and identify opportunities and threats24.

Unmet customer needs: The Product Owner should identify and prioritize the customer needs that are not yet met by the product or its competitors. Unmet customer needs are the gaps or problems that the customers face, and that the product can solve or address. The Product Owner should use techniques such as user stories, personas, value proposition canvas, and jobs to be done to discover and validate the unmet customer needs25.

Competitor pricing: The Product Owner should benchmark and compare the product’s pricing with its competitors and alternatives. Competitor pricing is the amount of money that the customers have to pay to acquire or use a similar or substitute product. The Product Owner should use competitive analysis, price elasticity, and value-based pricing to determine the optimal pricing strategy for the product2 .

The other option, company earnings targets, is not a relevant source of information for the Product Owner, as it does not reflect the value or the demand of the product. The Product Owner should focus on delivering value to the customers and the stakeholders, rather than meeting arbitrary financial goals. The company earnings targets may also change over time, and they may not align with the product vision or the market reality2 . References: 1: Scrum Guide 2: Managing Products with Agility 3: Customer Feedback 4: Market Share 5: Unmet Customer Needs : [Competitor Pricing] : [Company Earnings Targets]

Product Backlog involves the following activities12:

Reducing or eliminating dependencies between Product Backlog items. This helps to increase the flexibility and adaptability of the Product Backlog, and enables the Developers to select the most valuable and feasible items to work on in each Sprint3.

Reviewing the Product Backlog with stakeholders. This helps to ensure that the Product Backlog reflects the needs and expectations of the customers and users, and that the Product Owner receives feedback and input from various perspectives4.

Breaking large Product Backlog items into multiple smaller Product Backlog items. This helps to create a more granular and transparent Product Backlog, and allows the Product Owner to prioritize and refine the items more effectively5.

Ordering the Product Backlog. This helps to communicate the relative importance and urgency of the Product Backlog items, and guides the Developers to select the most valuable items for the next Sprint.

Forecasting the effort of Product Backlog items is not an activity that is explicitly required for managing a Product Backlog. The Product Owner is mainly responsible for maximizing the value of the product, not the effort or cost of development. The effort of Product Backlog items may be estimated by the Developers, but this is not a mandatory practice and it does not affect the ordering of the Product Backlog. References: 1: Product Backlog Management, 2: Managing Products with Agility, 3: Reducing Dependencies, 4: Reviewing the Product Backlog, 5: Breaking Down Product Backlog Items, : Ordering the Product Backlog, : The Product Owner, : Estimating Product Backlog Items