Free Access Scrum PSPO-II New Release

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, anddomains, 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 discourageteams 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

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.

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

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

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

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

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.

B is correct because the Product Owner is accountable for maximizing the value of the product and the work of the Developers1, and delaying answers to the Developers can cause waste, rework, and missed opportunities2. E is correct because the Product Owneris responsible for ensuring that the product Increment is valuable and useful for thestakeholders and customers3, and this requires close collaboration and feedback with the Scrum Team and the users4. A is incorrect because the Product Owner does not need to dedicate 100% of their time to the Scrum Team, as they also have other accountabilities such as engaging with the market, managing the product vision, and aligning with the business strategy5. C is incorrect because the Product Owner is not a proxy for the stakeholders, and they should not delegate their role to business analysts or anyone else. D is incorrect because the Product Owner does not need the approval of the stakeholders to decide how much time they spend with the Scrum Team, as they are empowered to make the best decisions for the product. F is incorrect because the Product Owner should not base their time allocation on the complaints of the Developers, but on the value and quality of the product.