Definitive Scrum Product Owner and PSPO Certification Course

Explore why agile emerged from common values among 2001-era practices like scrum, how product owners benefit, and how agile enables teams to adapt quickly to changing customer needs and competition.

Explore the agile manifesto’s four values: individuals and interactions over processes and tools; working software over documentation; customer collaboration over contract negotiation; and responding to change over following a plan.

Explore the agile values and 12 principles that support agile, their overlap with scrum, and learn to summarize each principle in a single word to prioritize customer value.

Explore key agile principles for product owners, including simplicity and delivering value early and often, and learn how to apply these principles to prioritize work and validate outcomes.

Discover the agile mindset as a perspective shaped by values and principles, and learn how practices like standups deliver value when aligned with purpose, plus where agile fits and doesn't.

Explore Stacey complexity diagram to guide agile responses across simple, complicated, complex, chaos problems. Assess risks of waste vs effectiveness and apply empiricism to ensure we solve the right problem.

Embrace empiricism in agile by applying transparency, inspection, and adaptation to solve complex problems, guiding product owners to learn, test hypotheses, and adapt Scrum practices to reveal unknowns.

Anchor the agile mindset by using scrum to solve complex problems and validate hypotheses, and study the Scrum Guide as the single source of truth, originated in 1995.

Adopt Scrum as a lightweight framework—not a methodology—to help teams and organizations generate value through adaptive solutions for complex problems, driven by a shared goal and teamwork.

Read the scrum guide and highlight key sections, compare them to your organization’s approach, and identify gaps as we tie the scrum framework together in ten minutes or less.

Walk through the scrum framework, outlining the product goal, product backlog, and the roles of the product owner, developers, and Scrum master. See how sprints deliver an increment with transparency.

Examine the product owner role in scrum, its accountabilities to maximize product value, manage the product backlog, and act as an investment manager whose decisions earn organizational trust.

Learn how the scrum master acts as a servant leader who coaches, mentors, and facilitates to help the organization, product owner, and developers realize value from scrum.

Elevate the developers as a cross-functional, self-managing scrum team that turns ideas into working product by delivering increments and units of work, including designers, testers, and engineers.

Explore the five formal, timeboxed scrum events—the sprint, sprint planning, daily scrum, sprint review, and sprint retrospective—and how they promote transparency for inspection and adaptation.

A sprint is a time box of one month or less, containing all coding and testing toward a potentially releasable increment and representing maximum investment before we know we're wrong.

Plan the sprint by setting a feasible sprint goal with the product owner, scrum master, and developers, using the product backlog, increment, and velocity to define the sprint backlog.

Review the sprint backlog and progress toward the sprint goal in a 15-minute daily scrum. Identify impediments and collaboration needs to replan effectively.

Conduct a sprint review to inspect the increment, raise transparency with stakeholders, gather feedback, and adapt the product backlog and product goals for future work.

Learn how to run an effective sprint retrospective with the entire scrum team, inspect what happened, identify root causes, and create actionable improvements for the next sprint.

Discover how scrum artifacts raise transparency, enable inspection, and guide adaptations to deliver the most valuable product, focusing on the product backlog, sprint backlog, and increment.

Define the sprint backlog as the team's plan to meet the sprint goal, reviewed at scrums to enhance transparency and adapt by adding or removing work with the product owner.

Explore the increment as the product's current state, how incremental building adds pieces each sprint, and how commitments attached to artifacts raise transparency to inspect and adapt to maximize value.

Identify the commitments tied to each Scrum artifact: the product backlog's goal, the sprint backlog's goal, and the definition of done. These commitments show what we value for each artifact.

Define the product goal as the single, overarching objective guiding the product backlog beyond a sprint, aligning with roadmaps and OKRs, and guiding sprint reviews with stakeholders.

A sprint goal is a single, focused objective and stepping stone toward the product goal, balancing autonomy and alignment to unify dispersed teams and guide the definition of done.

Define the definition of done to establish a shared standard of quality across all backlog items, increasing transparency and enabling inspection and adaptation in scrum.

Explore the five scrum values: focus, openness, respect, commitment, and courage, and learn how applying them shifts teams from mechanical scrum to delivering value.

Explore the scrum values through a focus exercise and observe how context switching affects agility and creativity. Learn to guide teams toward cohesive work that strengthens sprint and product goals.

Recap the scrum framework’s elements—events, accountabilities, artifacts, commitments, and values—and explain how a product owner uses a habit formation, illumination, and validation framework to maximize value.

Explore how scrum empowers product owners to test and validate value, fill the backlog with hypotheses of value, and tackle challenges by developing essential skills and traits.

Explore the five core challenges of product ownership, including accountability, authority, availability, analysis, and experimentation, and learn practical steps to assess and improve your leadership.

Explore the essential skills and traits of product owners, including communication, collaboration, decision making, prioritization, negotiation, risk management, and stakeholder involvement, plus an introduction to evidence-based management.

Introduces evidence based management as an empirical approach that helps teams improve customer outcomes, organizational capabilities, and business results under uncertainty, aligning with scrum to help product owners think bigger.

Learn evidence-based management by aligning goals, evidence via key value areas, and empiricism, then test hypotheses through the empirical cycle to learn and steer toward strategic, product, and sprint goals.

Explore evidence-based management's four key value areas—current value, unrealized value, ability to innovate, and delivery time—and learn how to measure them with example metrics and questions.

Identify unrealized value by weighing potential opportunities against current value, guiding strategic investment decisions for product owners toward end-state goals and capabilities.

Assess the ability to innovate by examining how we deliver new capabilities, remove sludge from the development pipeline, and speed time to market to deliver value to customers.

Minimize time to market by using the time-to-learn metric to accelerate learning from experiments and deliver value, guiding product owners and executives in sprint planning and reviews.

Explore evidence-based management to sharpen strategic conversations for product owners, boost value to organizations, and understand how scaling impacts your role.

Scaling involves coordinating multiple teams or products, but scrum keeps one product owner, one backlog, and one product goal per product, to avoid slower decisions and diluted accountability.

Explore how the product backlog translates strategic goals to tactical work and maximizes the value of developers' efforts through evidence based management.

Articulate motivating product vision describing the desired future for external users and internal teams, aligned with company goals and Google's vision to organize the world's information and Airbnb's belong anywhere.

Product goals act as strategic stepping stones toward a product vision, guiding planning and focusing the team. They are discussed at every sprint planning and review to identify next objective.

Learn to manage a product backlog by keeping it ordered and transparent, evolving through adding, removing, reordering, and detailing items, with refinement and stakeholder collaboration to focus on top priorities.

Explore various product backlog items, including experiments, use cases, bugs, and tech debt, and learn how PBIs guide work while backlog actions prepare for user stories.

Learn how user stories fit agile practices, explore the three Cs—the card, conversation, and confirmation—and use as a I want so that format to refine backlog items.

Product owners frame backlog items as investments and run experiments to validate hypotheses of value. The invest-experiment-validate cycle with smaller backlog items guides prioritization and investment decisions.

Split product backlog items to deliver small increments, learn cheaper, faster, and easier, and shrink the investment cycle through independent, negotiable, valuable, estimable, small, testable items.

Collaborate with stakeholders to split backlog items effectively using data, goals, and experiments to maximize value. Avoid becoming a proxy for the loudest voices; earn trust through bets and wins.

Learn to collaborate with developers by aligning on why through vision and goals, delegate transparently using tools like delegation poker, and prioritize the backlog to maximize value.

Prioritize effectively as a product owner by balancing highest value, lowest cost, and highest risk; test small and learn early, defend your prioritization, and optimize the backlog investments.