The Ultimate Product Owner Certification Training

Explore the scrum team as a cross-functional, self-managing unit, detailing stakeholders, the product owner, the scrum master, and developers, and how they collaborate to maximize product value.

Discover how a cross-functional, self-managing scrum team delivers usable increments each sprint, with the product owner guiding backlog, product goal, and responsiveness to market feedback.

Maximize product value by identifying and understanding stakeholder needs, translating them into a clear product backlog, and balancing competing demands as the product owner and voice of the customer.

The product owner maximizes value by managing the product backlog, communicating the product goal, and collaborating with the Scrum team to decide releases, refine items, and align with market needs.

Learn how the product goal guides the product backlog and how the product owner leads sprint planning and reviews, prioritizes work, and communicates acceptance criteria to maximize value.

Own the product outcomes with accountability, center decisions on customer needs, reduce the satisfaction gap through evidence-based testing, and align vision, strategy, and goals to deliver measurable value.

Define the scrum master's role, accountability for the team's effectiveness, and coaching for self management. Explore removing impediments, guiding events within timebox, and supporting the product owner and organizational collaboration.

Lead the scrum team as a true leader, remove impediments, and ensure productive scrum events. Facilitate stakeholder collaboration for the product owner and the organization.

Developers form the single scrum team responsible for creating a usable increment each sprint, sizing PBIs, collaborating with the product owner, and guiding the daily scrum toward the sprint goal.

The Scrum team now defines the definition of done for the product, with the product owner and Scrum Master guiding it; developers turn backlog items into increments.

See how I-shaped, T-shaped, Pi-shaped, and comb-shaped skills address scarcity of skills in a Scrum team, driving collaboration, learning, and an integrated increment.

Explore the three Scrum team roles—scrum master, product owner, and developers—and their accountabilities for delivering valuable increments, sprint goals, and backlog management.

Explore the five formal scrum events—sprint, sprint planning, daily scrum, sprint review, and sprint retrospective—and learn how each uses time-boxed ceremonies to inspect, adapt, and deliver value.

Master the sprint as the heartbeat of Scrum, a timeboxed cycle turning ideas into value through sprint planning, daily scrum, sprint review, and sprint retrospective toward the product goal.

Explore how sprint planning unites the entire scrum team to define the sprint goal, select PBIs, and shape the sprint backlog to deliver value aligned with the product goal.

The daily scrum inspects progress toward the sprint goal, adapts the sprint backlog, and lets developers plan the next day’s work; the Scrum Master and Product Owner may attend.

Inspect the sprint outcome with the scrum team and stakeholders to progress toward the product goal, and present only 100% done items while the product backlog may be adjusted.

The sprint retrospective inspects the last sprint's individuals interactions, processes, tools, and definition of done to focus on context, not content, and plan improvements that boost quality and effectiveness.

Clarifies the length of scrum events and sprint duration, balancing rules with practice, emphasizing timeboxing, consistency, and adjusting sprint length through the sprint retrospective.

Explore the purpose and flow of the five scrum events: sprint, sprint planning, daily scrum, sprint review, and sprint retrospective, linking them to the product goal and definition of done.

Explore how scrum artifacts carry commitments, the product goal, sprint goal, and definition of done, to maximize transparency, accountability, and empiricism within the product backlog, sprint backlog, and increment.

Understand how the product backlog is an ordered, value-driven source of work, prioritized by the product owner, refined into ready PBIs, sized with the developers, and continually evolving.

Define and pursue a single, measurable product goal within a protocol, guiding the backlog while incrementally delivering value; refine goals through sprint reviews and stakeholder validation.

Define the sprint backlog as a flexible, visible plan created during sprint planning, updated throughout the sprint, centered on the sprint goal, with incomplete items moved to the product backlog.

Define the sprint goal as the single objective created by the whole team during sprint planning, guiding the work with focus, flexibility, and a shared mission.

An increment is a concrete stepping stone toward the product goal; each increment is additive to prior ones, verified, and usable, with the whole Scrum team deciding when to release.

The definition of done describes the increment and quality. When items meet the definition, the increment is born, transparent, with improvements guided by the product owner and scrum master.

Summarizes the three scrum artifacts: product backlog, sprint backlog, and increment, and their commitments to transparency. The summary highlights product goal, sprint goal, and definition of done.

Master advanced product ownership by linking the product vision and strategy to daily execution, measure value with evidence-based management, refine backlog, planning poker, and scale scrum across multiple teams.

Define the product vision as the chief product visionary to guide the scrum team toward success and meet the target audience’s needs, with an emotional, persuasive focus, and communicate frequently.

Visualize a simple product strategy with the product vision board, outlining vision, target group, customer needs, features, and business goals. Validate insights with customers to secure buy-in and guide decisions.

Maximize value as a product owner by balancing financial and societal value, understanding the market and end users, and releasing increments to deliver value.

Discover how evidence based management helps the product owner maximize value by applying empiricism to four key value areas: current value, unrealized value, time to market, and ability to innovate.

Maximize value for product owners using the evidence based management framework and the experiment loop, prioritizing outcomes over outputs and balancing four key value areas.

Apply empiricism and evidence based management to product value by setting goals, testing ideas, and inspecting results to adapt toward strategic outcomes.

Explore evidence-based management and empiricism for navigating uncertainty by setting strategic, intermediate, and tactical goals, measuring outcomes, and aligning teams through transparent goals and experiments.

Learn how evidence based management guides agile teams to measure business value and improve outcomes through empirical decisions, beyond velocity and code practices.

Learn evidence based management four key value areas—current value, time to market, ability to innovate, unrealised value—and the learning loop that uses key value measures to deliver value.

Define and communicate a clear product vision, use the five-section vision board to align target group, needs, product, and business goals, and deliver value via releasable increments.

Shift from project thinking to product thinking by delivering customer-focused value through agile, with success measured by user adoption, retention, revenue, cost savings, and frequent increments.

Discover how to refine product backlog items by focusing on non-technical, independent PBIs described with user stories, sized with story points, and ordered to maximize value, cost, risk, and dependencies.

Learn how product backlog refinement turns backlog items into ready, well-defined PBIs that developers can size and select in a sprint, with the product owner guiding trade-offs.

Identify how backlog items vary from tasks to epics and themes and how readiness guides refinement and prioritization, noting that ready is not a Scrum definition.

compare product and project management in scrum, emphasize delivering value over traditional metrics, and explain ongoing product backlog refinement, readiness, and team roles that drive adoption, retention, and cost savings.

Learn how story points serve as a relative measure of effort to estimate product backlog items, calculate team velocity, and plan sprints using planning poker in agile projects.

Use planning poker to assign story points by voting face down with cards, reveal results to discuss discrepancies and avoid anchoring, then re-vote and average.

Define the definition of done as the formal increment state meeting quality measures, mandatory for transparency, and apply planning poker with story points for backlog refinement and velocity.

Use information radiators, burn down and burn up charts, to measure sprint progress, ensure transparency, and focus on delivering value while tracking scope changes.

The cone of uncertainty shows that uncertainty is highest at the start of a project and declines as time passes and knowledge increases through iterations, improving forecast accuracy mid-project.

Explore how technical debt accrues when teams fast-track delivery, and learn how refactoring and thoughtful planning reduce future costs, improve scalability, and align with Scrum practices.

Learn how code refactoring tidies internal code without changing behavior, and how continuous integration merges changes into the codebase, distinguishing integration from release for faster, quality delivery in scrum.

Explore information radiators and progress measurement by the product owner, using burn down charts and a trend line to forecast end, and explain the cone of uncertainty and continuous integration.

The team decides releases for releasable increments using the definition of done, and validates ideas through marketplace feedback to ensure timely value.

Explore how scaling Scrum affects multiple teams on one product, emphasizing dependencies, shared definition of done, and keeping the product owner accountable without proxies.

Explore fixed price and time and material contracts within an agile budget, detailing how sprint budgeting works, scope discovery, risk allocation, and maintaining a cap in time and material.

The whole scrum team guides release decisions, verifies increments for usability, embraces major and minor releases, and emphasizes one product backlog with a single product owner toward the product goal.

Follow a practical, step-by-step scrum case study from idea to release for a chiropractor's website. Learn how the backlog forms from user stories.

John, a chiropractic clinic owner, partners with Intelligent Web Solutions to build a conversion-focused website for Facebook-led lead generation, shifts from newspaper ads, and guides a Scrum team.

Gather user stories in the first meeting to define website features like a marketing funnel, scheduling, and payment processing, and record them in a backlog using a simple user-story template.

Create a Jira project, build the product backlog with user stories and tasks, set up a Scrum board, and plan the first sprint with story points on the sprint backlog.

Lead a two-week sprint with a four-hour sprint planning session to define the sprint value and outline how the team will build a chiropractic clinic information website.

discover how daily scrums keep sprint on track with three questions, and distinguish the definition of done from acceptance criteria—as defined by the product owner and refined by backlog work.

Attend the sprint review to capture timely client feedback on the completed increment, and see how the product owner discusses hosting, payment options, and Facebook pixel needs.

During a one-and-a-half hour sprint retrospective, the team identifies ways to improve workflow, praising communication and feedback, and tests a code-first approach before QA to reduce back-and-forth.

Refine the backlog during sprint planning, target the free adjustment feature, design a lead-generation page, build a MySQL database with CRUD services, and integrate MailChimp and Facebook pixel.

Track project progress through four sprints: test a free adjustment landing page, demo a lead-generation page, implement a payment tool sandbox, and add analytics to optimize campaigns.

Identify the seven most common mistakes on the certification exam, learn to avoid them, and use updated practice questions and resources as your preparation checklist to pass with confidence.

Read the questions carefully to spot changes in wording that alter the correct answer. Stay focused on Scrum questions, avoid panic, and answer first, then revisit difficult items later.

Prepare for the official Product Owner certification exam by completing a warm-up quiz and two full-length practice tests, study feedback, and aim for a perfect score to build confidence.

Discover strategies to tackle difficult, long exam questions and build a product owner mindset. Follow a structured workflow: read options aloud, pause to answer, then review your thought process.

Define value by outcomes, including customer happiness, feature usage, and employee happiness, while using evidence-based management to distinguish outputs from outcomes.

Learn how to handle a decline stage product using an experimenter stance to empirically validate feature ideas, protect unrealized value, and balance stakeholder input.

As the product owner, improve sprint forecasts by refining the product backlog toward readiness and staying available to answer questions, while collaborating with the Scrum Master to boost team effectiveness.

Examine the product owner's accountability in backlog management, including delegation of backlog item creation and avoiding bottlenecks, ultimately confirming that none of the options are correct.

Learn how the product owner maximizes value by managing an emergent, transparent backlog that developers and the Scrum Master can contribute to, visible to stakeholders, not exclusively controlled.

Evolve the product vision as the team understands end users. Communicate the vision early and often, with the product owner as chief visionary, to align the team and stakeholders.

Explains that scrum has no mandatory product owner practices, while exploring common tools like value points, burn down charts, business model canvas, goal oriented product roadmaps, and stakeholder analysis.

Identify who writes acceptance criteria for product backlog items, clarifying that the product owner remains accountable while delegation to the Scrum team is allowed, per the Scrum guide.

As a product owner, balance influential stakeholders' opinions, validate proposed features with experiments and MVPs before updating the backlog, and safeguard the current sprint while prioritizing value.

Develop strategic product ownership skills by crafting a North Star vision, building a roadmap, engaging stakeholders, and running experiments to validate ideas with data and improve user satisfaction.

Define and articulate a concise product vision that serves as a north star for your team, detailing target audience, product category, key benefit, primary differentiation, and future state.

Craft a compelling product vision by starting with why and using a vision board, elevator pitch, and stakeholder interviews to align target group needs with business goals.

Communicate and align the product vision through repetition, visual aids, and storytelling, connect daily work to the vision, and lead by example to sustain alignment.

Learn how to create and use product roadmaps, align vision, strategy, and execution, and choose from templates like the goal oriented roadmap to guide planning, communication, and flexibility.

Explore the goal oriented product roadmap, focusing on aligning goals with business targets, setting a date, naming milestones, listing three to five features per goal, and defining measurable metrics.

Explore product roadmap templates—timeline, now/next/later, and team-based—and learn to choose a flexible, outcome-focused approach. The lesson highlights milestones, user research, wireframes, and backlog items.

Explore stakeholder management and learn to identify and prioritize stakeholders using a power–interest grid, illustrated with a mobile banking app example to secure buy-in and guide product success.

Identify and understand stakeholders, engage them throughout the product development cycle, share roadmaps, solicit feedback, and diplomatically say no to manage expectations and foster collaboration.

Run small, data-driven experiments to validate product ideas, reduce risk, and accelerate learning, embracing empiricism and evidence-based management while aligning with user needs.

Learn to run experiments with A/B and multivariate tests, apply feature flags, beta and fake door testing to drive data-driven product decisions.

Craft a concise, future-oriented product vision statement using vision board and elevator pitch techniques; practice stakeholder management, storytelling, and data-driven experimentation to align teams.