Professional Scrum Product Owner II (PSPO)

For IT leaders: When leadership asks why so much work produces so little measurable improvement, the cause is often not delivery. It is product ownership. Product Owners who mainly refine backlogs and run meetings keep teams busy without moving outcomes like adoption, renewal, or customer satisfaction.

Who to assign: Experienced Product Owners, product-minded Team Leads, and agile leaders who already know Scrum basics and are preparing for the Professional Scrum Product Owner II assessment. Learners new to the role should finish Professional Scrum Product Owner I first.

Time investment: About 9.7 hours across 11 skills, most under an hour each. That fits a two- to four-week cadence alongside normal sprint work.

What changes on your teams: Product Owners learn to treat products as investments and use the product vision to accept or decline requests. They size experiments to the riskiest assumption, separate evidence from interpretation, and make trade-offs visible when stakeholders compete for limited capacity. Expect tougher, better-reasoned prioritization conversations. Prepare sponsors for the change.

How CBT Nuggets supports the outcome: An Integrated Product Simulation follows one product scenario from evidence to direction. The Assessment & Decision Lab walks through 40 scenario questions and explains why the wrong answers look attractive. Team Reporting lets Training Managers track progress toward certification.

Many IT and product organizations keep teams busy without seeing measurable improvement. This course reframes that as a product ownership problem, not a delivery problem. Your Product Owners will learn to manage for outcomes customers experience instead of outputs like velocity and burndown charts.

The training follows a running case study, PulsePoint, through decisions your teams face every quarter. Examples include a customer request for an executive dashboard that hides the real problem, a patient feature resting on untested assumptions, and a rollout where an 83% activation rate masks weak sustained use. Real-world cases, including Zoom's reprioritization during its 2020 growth surge, show how competing pressures from customers, technology leaders, and executive sponsors play out at scale.

• Fewer wasted investments: Product Owners rank assumptions by uncertainty and consequence. They then design the smallest useful experiment, which is credible but not just the cheapest, before committing major capacity.
• Better discovery: Teams ask about the last time a problem happened, not the ideal process, and pair interviews with product usage data to find where real value lies.
• Defensible priorities: Leaders make trade-offs visible by naming what each priority displaces, rather than hiding behind a scoring model.
• Clearer evidence conversations: Product Owners separate facts, interpretations, and assumptions so stakeholders don't argue from the most persuasive statistic.

The result is product direction that stakeholders can follow and that holds up when leadership asks why the work matters.

Knowledge

• Why backlogs organize work but don't create value, and how to tell outputs (velocity, burndown, stories completed) apart from outcomes like adoption, renewal, and customer satisfaction
• How a product vision and Product Goal guide real decisions, including why a reasonable request may not belong in the product right now
• How to uncover the customer problem behind a requested solution, using questions about specific recent experiences alongside product usage data
• How to rank assumptions by uncertainty and the consequence of being wrong, so the riskiest ones get tested first
• Why prioritization is a leadership responsibility, where frameworks fall short, and why a priority is only real once you name what it displaces
• How to separate facts, interpretations, and assumptions when evidence supports competing conclusions

Ability

• Shift team conversations from delivery activity to measurable outcomes the organization actually cares about
• Design the smallest useful experiment: credible enough to test the riskiest behavior without overstating how far the results apply
• Reprioritize under competing pressure from customers, technology leaders, and executive sponsors without creating chaos, and make trade-offs visible
• Treat stakeholders as a system and align them through influence, even when they disagree on individual decisions
• Read mixed rollout data without grabbing the most persuasive statistic, and decide whether evidence supports continuing, adapting, or stopping an investment
• Work through ambiguous, scenario-based PSPO II questions by spotting the principles and trade-offs inside each scenario