Professional Scrum Product Owner I (PSPO)

For IT leaders: When no one owns the product backlog, teams build features stakeholders didn't ask for, release dates slip, and forecasts get treated as promises. This course prepares IT Managers, Team Leads, product managers, and developers moving into a Product Owner role to maximize value, order the backlog, and connect business goals to team execution with Scrum.

• Role fit: Best for staff who already work on or alongside Scrum teams and now need to own product decisions. It also suits Scrum Masters who want to understand the Product Owner's side of the framework.
• Time investment: About 8 hours across 10 skills of roughly 45–56 minutes each. That fits a two- to four-week assignment without pulling people off delivery.
• Risk framing: Learners revisit refinement as the bridge from product vision to actionable backlog items, sprint goals, and working increments. The course also frames Scrum events as reliable forums for stakeholder alignment, so product direction is less likely to surprise the team or leadership.
• Change management: The course stresses that a forecast is not a commitment. It also covers how Product Owners use refinement, Scrum events, and sprint goals to reset expectations with stakeholders and keep leadership aligned on value delivery.

The final five skills revisit Scrum foundations from the Product Owner's perspective, focusing on Scrum framework review, people and teams, and managing products with agility. Prior PSM I training is helpful but not required, though IT Directors can pair this course with Professional Scrum Master I in a Playlist so Product Owners and Scrum Masters train on a shared vocabulary.

IT teams complete this training so the people who own product decisions can connect business goals to what the team actually builds. The course grounds Scrum theory in practical scenarios. Product Owners practice using empiricism, refining backlog decisions, and connecting product goals to the work selected by the team. They also evaluate which increments are truly usable and ready to deliver value.

• Clearer, more actionable backlogs: Team Leads and Product Owners learn refinement techniques that surface technical, security, and dependency details before work enters a Sprint. That means fewer surprises mid-Sprint.
• Realistic release expectations: The course reinforces that product planning should be grounded in evidence, inspection, and adaptation. Stakeholders get roadmaps shaped by what the team is learning, not promises the team can’t keep.
• Stronger artifact decisions: Hands-on artifact exercises help practitioners select backlog items that support the goal and set aside work that doesn’t. The focus stays on valuable, goal-aligned increments.
• Better stakeholder alignment: Facilitation scenarios help Product Owners steer conversations toward the problems the business needs solved, not feature wish lists.

The result is a team that makes evidence-based product decisions rather than relying on gut feel.

Knowledge

• How the Product Owner role differs from and overlaps with the Scrum Master role, and where PSPO competencies build on Scrum foundations
• The three Scrum artifacts and their commitments: product backlog and product goal, sprint backlog and sprint goal, increment and Definition of Done
• Why empiricism — transparency, inspection, and adaptation — guides decisions in complex environments, and why data outperforms gut instinct
• How forecasting supports planning in complex environments, and why a forecast is not a contract or a commitment
• Product Owner responsibilities for value maximization, product vision, stakeholder management, and product economics
• How the Scrum Team, Scrum Master, and Scrum events support incremental value delivery and continuous improvement

Ability

• Order and refine product backlog items, including capturing technical details, acceptance criteria, and dependencies
• Evaluate whether work meets the Definition of Done and whether backlog items align with the product goal
• Connect product backlog ordering to the product goal, stakeholder needs, and incremental value delivery
• Facilitate stakeholder conversations focused on outcomes rather than features
• Partner with the Scrum Master to guide retrospectives when delivered value falls short
• Prepare for the PSPO I exam using the Scrum.org open assessment and a structured review of core competencies