Ag Certified Scrum Product Owner (CSPO®)

Scrum Theory

• How Scrum is aligned with the values and principles of the Manifesto for Agile Software Development.
• What is Scrum and what is its purpose.
• The five core Scrum values.
• Define Empirical process control and the three pillars of Scrum.
• Product planning in an empirical environment.
• Pitfalls of partially implementing Scrum.
• Benefits of an iterative and incremental approach.

The Scrum Roles

• How the Scrum Roles interact with each other to deliver the increment within a Sprint.
• The cross-functional team and the benefits of a cross-functional, self-organizing team.

Scrum Events

• The benefits of timeboxing.
• The five events within Scrum, the purpose of each event, and the participants, timing, and maximum recommended timebox.

Scrum Artefacts

• The three artefacts within Scrum and the purpose of each.
• The definition of “Done,” its purpose, and how it evolves over time.
• Why the Scrum Team dedicates time for Product Backlog Refinement.
• Activities that may occur as part of Product Backlog Refinement.

Fundamentals of the Product Owner Role

• Types of organizational contexts that affect the approach to the Product Owner role.
• Anti-patterns that might exist for Product Owners.

Working with Stakeholders

• Providing transparency to stakeholders on progress toward goals.
• Techniques to engage stakeholders to gather information or insights.
• Product Ownership with Multiple Teams
• Ways of overcoming the challenges of being a Product Owner for multiple teams.

Describing Purpose and Strategy

• Creating a product vision.
• Components of a product plan or forecast with stakeholders.
• How to plan a product release.
• Approaches to identify small, valuable, and releasable Product Increments.

Understanding Customers and Users

• Why a Product Owner performs discovery and validation work.
• How to segment customers and users.
• Prioritizing between conflicting customer (or user) needs.
• Aspects of product discovery and identify how each contributes to successful product outcomes.
• Techniques to describe users and customers: their jobs, activities, pains, and gains.
• Approaches to connect the Development Team directly to customers and users.
• Benefits of Development Team direct interactions.

Validating Product Assumptions

• How Scrum supports validating product assumptions.
• How to validate product assumptions by their cost and quality of learning.

Differentiating Outcome and Output