A, B, C, and D are correct because they are all measures of the value that a product delivers to the customers and the organization1. Revenue per Employee indicates the efficiency and productivity of the product development2. Market Share shows the competitive advantage and customer satisfaction of the product3. The average selling price as compared to close competitors reflects the perceived value and quality of the product4. Product profitability measures the financial return and viability of the product5. E is incorrect because the weekly velocity of the Developers is not a measure of value, but a measure of output and capacity. Velocity does not indicate whether the product is meeting the needs and expectations of the customers and the stakeholders.

Explanation
A “cone of uncertainty” is a graphical representation of the evolution of the amount of uncertainty during a project. It shows that at the beginning of a project, there is a high degree of variability and unpredictability in the estimates of the scope, cost, time, and value of the product. As the project progresses, more information and feedback are gathered, and the uncertainty decreases, reaching zero when the product is delivered and validated. A “cone of uncertainty” can be used to visualize the uncertainty of the potential value thata Scrum Team delivers over time, and to guide the empirical process of inspection and adaptation. By using a “cone of uncertainty”, a Scrum Team can:
* Align the expectations of the stakeholders and customers with the reality of the complex and dynamic environment.
* Avoid making premature or unrealistic commitments based on inaccurate or incomplete estimates.
* Embrace change and experimentation as opportunities to learn and deliver more value.
* Inspect the actual value delivered and the feedback received, and adapt the product vision, strategy, and backlog accordingly.
* Forecast the range of possible outcomes and the level of confidence for each Sprint and release.
The other options are not valid uses of a “cone of uncertainty”. A “cone of uncertainty” does not represent the relative level of difficulty for predicting the velocity of individual team members, as velocity is a measure of the amount of work done by the whole Scrum Team, not by individuals. A “cone of uncertainty” does not rapidly identify and prioritize all uncertainties, as uncertainties are not always known or quantifiable, and may change over time. A “cone of uncertainty” does not determine whether to cut quality, similar to the “Iron Triangle” of project management, as quality is not a variable that can be traded off in Scrum, but a non-negotiable aspect of the Definition of Done and the value proposition of the product.
References:
* Professional Scrum Product Owner™ II Certification
* Managing Products with Agility
* Cone of Uncertainty – Wikipedia

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

As a Product Owner, you need to embrace agility and empiricism in your product development. This means that you should be able to inspect and adapt your product based on feedback from the market, customers, users, and stakeholders. You should also be able to experiment and learn from your failures and successes. To do this, you need to have a flexible and adaptable product architecture that can support frequent changes and new features. You also need to collaborate with your Scrum Team and other teams in the organization to deliver value incrementally and iteratively. Therefore, leaning on your organizational efficiency and existing architecture to build your product aligned to the current organization is the least effective way to enhance your agility. This approach can limit your innovation, creativity, and responsiveness to the changing needs and expectations of your customers and users. It can also create silos, dependencies, and conflicts within and across teams, and reduce the quality and value of your product.
Professional Scrum Product Owner II Certification
Evolving the Agile Organization
Managing Products with Agility

A good Product Vision and Strategy should have the following attributes12:
It describes who will use the product and what they would like to achieve. This helps to define the target market, the customer segments, and the user personas, as well as their needs, goals, and problems.
It describes how people will use the product to achieve potential outcomes. This helps to articulate the value proposition, the benefits, and the features of the product, as well as the assumptions and hypotheses that need to be validated.
It describes what value means in the context of the product, and how it can be measured. This helps to establish the objectives, the key results, and the metrics that will guide the product development and evaluation.
It is not necessary for a good Product Vision and Strategy to describe how the product compares to competitor products. This may be part of the market analysis or the competitive advantage, but it is not a core attribute of the Product Vision and Strategy. Moreover, focusing too much on the competitors may distract from the customer needs and the product value. References: 1: Product Vision, 2: Product Strategy

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.

A; To influence the Total Cost of Ownership of the product: Adhering to the Definition of Done ensures that the product meets the required quality standards, which can influence the Total Cost of Ownership1.
B: To have transparency into what has been done at the end of each Sprint: The Definition of Done provides a shared understanding of what work was completed and what standards were met as part of the Increment2. This creates transparency and allows the Product Owner to understand what has been accomplished at the end of each Sprint12.

According to the Professional Scrum Product Owner II (PSPO II) guidelines, the best indicators of value delivery are those that reflect the product’s impact on customers and its usage in the market.
* Customer satisfaction (Option A) is a direct measure of how well the product meets customer needs and expectations. High customer satisfaction is a strong indicator that the product is delivering value1.
* Frequency of feature use (Option D) provides insights into which features are most valuable to users by showing how often they are used. This metric helps Product Owners understand user behavior and prioritize features that deliver the most value1.
On-time release trends (Option B) and velocity (Option C) are more about the process and efficiency of the development team rather than direct indicators of value to the customer. Scope implemented (Option E) measures the amount of work done but does not necessarily correlate with customer value. Therefore, options A and D are the best choices for measuring value delivery as per the PSPO II resources.

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