Module 1 – Process Domain

Scrum theory includes time-boxing, and specific roles, rules, and artifacts. All elements of Scrum complement each other to form a consistent whole. All work is performed in Sprints. All base rules, events, and roles are described in the Scrum Guide, the acknowledged Scrum body of knowledge. Each part of Scrum ties back to the principles and theory.
This is foundational knowledge for every Scrum Team member and anyone involved with Scrum. Product Owners know how to take advantage of the business opportunities unlocked with the Scrum framework in delivering value to the market place every 30 days, or less.

Module 2 – Scrum Theory And Principles

Scrum is founded on empirical process theory to deal with the complexity typical to software development. All principles and values of Scrum are based on the fundamental view of software development as creative and complex work.
Scrum Masters know how Scrum implements empiricism in software development. They explain how the Scrum principles tie back to the empirical nature of Scrum, and how they are fundamentally different from those of more traditional software development approaches.
Scrum Masters understand the impact of the transparency that Scrum brings and requires, and how Scrum is best used to increase an organization’s agility.

Module 3 – Cross-functional, Self-organizing Teams

Scrum Teams are self-organizing and cross-functional; which is very different from traditional development groups.
Product Owners acknowledge the self-organizing skills of Development Teams and how Development Teams organize their development work in creating Done Increments of product. Product Owners understand how their accountability is complementary to that of a Development Team, and not conflicting.

Module 4 – Maximizing Value

Scrum is a foundation to unlock business agility. Scrum in itself however is–by design–incomplete. Agility will be much higher if Scrum is complemented by strategies for Agile product management and when metrics are in place to track the creation and delivery of value to the market place.

Module 5 – Product Backlog Management

A Product Owner is accountable for the Product Backlog, and the ordering of all work that is identified for the product. Product Backlog is used to manage the requirements and can be used to plan releases, and track and report on progress.

PSPO: Professional Scrum Product Owner