Scrum Product Owner

Explore the course structure, learning objectives, and how to use the courseware and course book. Prepare effectively for the certification exam and map your path to success.

Welcome to the course; learn the skills to become an effective Scrum product owner and prepare for a Scrum product owner certification exam.

Define why these particular skills are important for your scrum team, tailor your learning style, and craft a plan to apply course insights to your organization to boost performance.

Explore how to leverage course and third-party materials, engage with peers and instructors in the mentoring community, and set expectations to own your Scrum skills for productive, controlled team outcomes.

Print a copy of the courseware and follow along to use the course's consistent conventions—chapter learning objectives, key terms, concepts to know, and the iconography used to illustrate examples.

Engage with quizzes and exercises to confirm your understanding of learning objectives and reinforce key Scrum concepts, skills, and readiness for the certification exam.

Examine scrum certification exams, featuring objective, multiple-choice tests that assess how you apply scrum practices. Know the range of questions and durations, from 75–140 questions and 90–180 minutes, online proctored.

Begin with a detailed study plan aligned to core scrum concepts and learning objectives, then use practice exams to master sprint review and retrospective in the scrum body of knowledge.

Explore key terms such as adaptation, the Agile Manifesto, information radiators, inspection, portfolios, programs, projects, scrum, a scrum guidance body, time boxing, transparency, and waterfall.

Explore the origins of scrum, its key benefits, and how it scales to enterprise projects, then examine the key aspects and processes that make scrum work.

Explore how project management acts as a framework to allocate time, resources, and people to deliver valuable products. Coordinate stakeholders, teams, artifacts, and deliverables to customers.

Explore how project management establishes how to plan and design, initiate, execute, monitor and control, and finally close resources and people to achieve a goal across methodologies.

Explore software development lifecycle management and agile approaches that enable initiating, planning, executing, controlling, and delivering projects while adapting to changing customer needs, markets, and regulations.

Waterfall provides structure and control by locking down requirements, design, and architecture; however, in six-month projects up to 60 percent of requirements change, demanding a flexible change-management approach.

The lecture explains the shift from traditional waterfall to agile, highlighting the agile manifesto's emphasis on individuals, collaboration, working software, and responding to change over heavy documentation and fixed contracts.

Explore agile principles that emphasize face-to-face collaboration, one cross-functional team delivering high-value working software aligned with customer needs, sustainable pace, technical excellence, refactoring, and continuous improvement through reflection.

Explore agile methodologies—Lean, Kanban, Extreme Programming, Crystal, Feature-Driven Development, Test-Driven Development, Adaptive Software Development, Unified Process, and Domain-Driven Design—and see how Scrum leverages these techniques.

Reframe development as a rugby approach emphasizing teamwork in the 1980s by Takeuchi and Nanako. Define scrum in 1995 by Ken Shabir and Sutherland as an empiricism-driven approach.

Scrum delivers benefits by enabling adaptation to changing requirements and risks, transparent delivery to stakeholders, continuous feedback, and high-value, working software through self-organizing teams.

Explore the core concepts and principles of scrum and how they support project management. Learn the processes within the scrum lifecycle to effectively carry out and deliver solutions for customers.

Employ empirical process control to use tangible results as feedback for evolving solutions that meet customer needs. Self-organize the team to deliver high-value outcomes through time-boxed iterations.

Learn that self-organization in scrum empowers teams to own solutions, remove roadblocks, and improve outcomes through servant leadership, buy-in, and space for innovation.

Create collaborative environments with broad visibility into who has what to clearly partition and reintegrate work while reusing technologies for better customer solutions; co-located teams maximize Scrum efficiency.

Maintain a prioritized product backlog to adapt to changing customer needs, risks, and dependencies, continually reordering work to maximize business value and deliver highest-value features first.

Time boxing in scrum allocates fixed durations for key events, such as a 15-minute daily standup and four-hour sprint planning for two-week sprints, improving efficiency and enabling more delivered value.

Iterative development delivers higher value early by breaking work into sprints, re-prioritizing based on changing requirements and risks, and continuously managing risks to maximize customer value.

Explore the core scrum processes, organized into five groups: initiation, planning and estimation, implementation, review in retrospect, and release—highlighting all eighteen activities.

Explore the five phases of a Scrum project, from initiation and planning with estimation, through implementation, to sprint reviews and retrospectives, culminating in releasing solutions to production.

Implement the project by delivering outputs from user stories, conducting daily standups, and grooming the backlog to reflect new change requests, risks, and changing priorities for upcoming sprints.

Use a scrum of scrums to align with other teams in a program, conduct sprint review with the product owner and stakeholders, and perform sprint retrospective to improve team processes.

Coordinate and plan a release to ensure shippable sprint outcomes deploy into production. Retrospect the project to capture lessons for the scrum guidance body and extend team capabilities across organization.

Explore the core of scrum, including what it is, its benefits, and how to scale it, along with the key principles and the 18 processes associated with it.

Explore how scrum and agile methods address issues of documentation over collaboration and deliver working software, while enabling empirical process control, scalability, and self-organization.

Discover the key roles, responsibilities, and authorities in scrum, including the product owner's duties and the specific responsibilities of the scrum master and scrum team within the project flow.

Define the key scrum roles—the scrum master, product owner, and scrum team—and introduce the scrum guidance body, outlining reusable structures for conducting successful scrum projects.

Define the product owner's role and capabilities to support the scrum team's work, outlining responsibilities, authorities, and interactions with other roles within the project.

Identify the product owner who owns the project's business value, collaborates with stakeholders, articulates requirements, and serves as the voice of the customer with the scrum team and scrum master.

Own and prioritize the product backlog with customers and stakeholders to rank features by value. Guide sprint planning and release decisions as the voice of the customer with clear authority.

Learn how the scrum master supports the product owner by coordinating sprint activities and delivering key deliverables that advance the product owner's objectives.

Identify the scrum master role as a servant leader who facilitates the scrum team and stakeholders, mentors, and removes roadblocks to optimize value and performance.

Coach and teach Scrum practices to help the team maximize value, challenge the team when needed, protect them from interruptions and impediments within the sprint, and prioritize product backlog items.

Explore how the scrum master earns authority through knowledge and stakeholder advocacy, including the product owner, while guiding the team without directing decisions and removing roadblocks.

Explore the scrum team's role in a scrum project, delivering user stories through self-organisation and task execution to empower and support them in producing effective solutions.

Form a cross-functional scrum team that delivers whole, potentially shippable solutions each sprint by combining requirements solicitation and validation with design, development, testing, and documentation.

Teams own delivering fully designed, integrated, and potentially shippable sprint outcomes, planning, daily stand-ups, backlog and burn-down chart tracking, and reviews and retrospectives to improve value delivery.

The scrum team self organizes to commit to user stories and estimate tasks, while the product owner clarifies which stories to tackle and the team collaborates to remove roadblocks.

Identify and engage stakeholders including customers, users, sponsors, and vendors, collaborate with the scrum master on a communications plan, and elicit and prioritize product backlog requirements for delivery visibility.

Outline roles and responsibilities in scrum, highlighting product owner's role in defining requirements and prioritized product backlog, with support from the scrum master and team, collaborating with customers and vendors.

Define and groom the prioritized product backlog, collaborate with the scrum team to select sprint user stories, define acceptance criteria, and accept deliverables that meet the definition of done.

Align the project vision with customer stakeholders and the product backlog, using workshops to define and prioritize user stories, estimate effort, and prepare the backlog for sprint planning.

Learn essential terms including business case, epic, gap analyses, JAD sessions, Kano analysis, sprint length, minimum marketable features, personas, prioritized product backlogs, user stories, and release plans.

Establish the project vision in this chapter and learn how to use it to align all stakeholders around a common set of goals and objectives.

Define a clear project vision with customers and stakeholders to establish shared goals. Use it to guide teamwork, track performance, and align features with user needs and a revenue model.

Create the project vision with customers and stakeholders by aligning the business case, mission, and desired end state, using a vision meeting, JAD sessions, and swat and gap analyses.

The project vision meeting engages customers, users, and stakeholders to define the business context, success metrics, and requirements, with the product owner championing stakeholder expectations in scrum.

Learn how requirements gathering workshops, such as jam sessions or join application development, align development teams and customers to define scope, objectives, and constraints within a time-boxed session.

Use swot analysis to define a desired end state, assess internal readiness, and identify external opportunities and threats to guide actions for a new line of business.

Use gap analysis to compare current performance with the desired end state, identify the gap in processes and capabilities, and determine the needed changes before proposing solutions.

Create a simple project vision that aligns stakeholders on shared goals, minimizes pre-work, and guides roadmaps to deliver high value despite changing requirements.

Articulate a project vision that defines the problem and end state for an easy to use expense management system, and secure charter and budget through collaboration with the scrum team.

Facilitate user group meetings and workshops to gather customer and user requirements, then document them to populate the product backlog.

Create and maintain a dynamic, prioritized product backlog that captures epics, user stories, risks, and changes to reflect customer needs, with the product owner leading workshops and prioritization efforts.

Explain epic as a big story and break it into user stories, then create personas to show value and challenges for a traveler’s expense management scenario.

Turn epics into detailed user stories in meetings and workshops, building a prioritized product backlog by capturing who uses the system, what it does, and why it matters to cost.

define done and establish acceptance criteria to objectively test, document, and integrate each user story, while the product owner and scrum master protect the sprint.

Explore how estimation shapes product and sprint backlogs, and learn techniques to estimate and prioritize effort for user stories and epics, with team support for planning and delivering sprint work.

Improve estimation in scrum by distinguishing accuracy from precision, using measurements and ranges (story points plus or minus) to inform best and worst-case scenarios.

Understand how to estimate size and duration honestly, using velocity and story points to plan sprints and releases, while fostering collaboration and high-quality delivery.

Learn how estimates, as predictions with uncertainty, drive sprint commitments; as teams gain familiarity, estimate ranges tighten, and early projects with limited visibility require cautious commitments.

Learn how to build and maintain a prioritized product backlog through creation, grooming meetings, and risk and change integration, using the backlog to drive product actions across activities.

Focus the backlog in Scrum on broad objectives to optimize business value with continuous delivery, delivering potentially shippable solutions each sprint and inviting changes to reduce risk.

Prioritize features by weighing business triggers, customer benefits, costs, opportunity costs, and risks to deliver the most valuable outcomes quickly, delivering value back to the customer within time scales.

Explore the product backlog as a living list of needs, including user stories, nonfunctional requirements, and risks, and see how the product owner groom and prioritize it for sprint planning.

Prioritize the product backlog to deliver high-value user stories early, guiding customer value and releases. Collaborate with stakeholders and developers, using prioritization techniques to balance minimum features, costs, and risks.

Prioritize the backlog using net present value and internal rate of return, and apply value stream mapping, minimum marketable features, and story mapping for early value.

Apply the one hundred point method, a multi voting technique by Leffingwell and Widick (2003), where each user allocates 100 points across stories to drive initial prioritization.

Learn Kano analysis for strategic planning by prioritizing features as exciting, performance, dissatisfiers, and indifferent types, and watch how value shifts through a product lifecycle, illustrated with an 8-track player.

Track value and budget with earned value analysis and cumulative flow diagrams, prioritizing completed user stories by business value while embracing changing requirements under scrum to optimize resources.

Establish the definition of done and acceptance criteria for each user story. Validate DoD, size stories for a sprint, and manage the backlog for future sprints.

Define the product owner's responsibilities to maximize business value by securing sponsor funding, collaborating with customers and users, and prioritizing the product backlog of user stories for sprint reviews.

Define the product owner's role with customers to plan and manage a release plan across sprints, aligning shippable deliverables with minimum functionality and minimum marketable features for production releases.

Lead release planning meetings with the scrum team, product owner, sponsors, and users to define minimum marketable features and delivery readiness, guiding continuous or phased deployment and customer value realization.

Establish a fixed sprint length and release planning schedule, map features to sprints, and update the backlog. Pilot feedback with target customers to validate benefits realization and costs.

Define a high-level communications plan identifying stakeholders—including product owner, project sponsor—and what, when, and by whom to communicate, guided by Scrum practices that enhance collaboration and visibility into value delivery.

Use release burndown charts to track progress across sprints, estimate with user stories and story points, and plan early, meaningful releases that deliver value to customers and stakeholders.

Learn how a release burndown chart tracks 120 story points across nine sprints, burning down remaining work to meet release objectives as deliverables pass acceptance criteria and definition of done.

Plan and align on well-defined requirements, create and prioritize project backlog, coordinate with scrum team and stakeholders to establish levels of effort, resource prioritization, and release planning for customer value.

Align stakeholders on a shared, generic project vision and manage a backlog by eliciting requirements, estimating effort for epics and user stories, and aligning with release plans to deliver value.

Test your understanding of planning activities for product owners by taking the chapter 04 quiz. See how you perform and where you stand.

Explore how scrum practices drive quality and quality assurance, address requests for change, and use the product backlog to identify risks and mitigation activities while supporting changing requirements.

Explore key terms for the Scrum product owner chapter, including business case, criteria, issues, analyses, DDCA, risk concepts, burn down charts, and quality.

Define and measure quality using the definition of done and acceptance criteria to drive quality metrics and ensure deliverables align with business objectives.

Define quality across deliverables and business value by integrating acceptance criteria, whole and end solutions, and a product backlog that prioritizes potentially shippable user stories in each sprint.

Identify measurable acceptance criteria for every user story and confirm they are met before considering a story done, using minimum criteria guided by program or portfolio resources.

Define an overarching definition of done for all user stories, including unit testing, code reviews, documentation, and a successful sprint preview, to measure acceptance and handover in scrum.

Improve software value by applying quality management in scrum through test driven development, refactoring, continuous integration, automated testing, and sprint retrospective to sustain quality today and tomorrow.

Explore how changes are requested and assessed for risk, cost, and value. Learn how to decide on approval and integrate changes into the prioritized product backlog.

Embrace change as a driver of value in scrum product ownership, using regular sprint reviews for customer feedback and backlog grooming to prioritize and integrate changes.

Assess change requests through a formal RFC process, weighing cost, value, and risk, and determine who approves them, with approved changes becoming prioritized user stories in the product backlog.

Balance flexibility with stability by integrating changes into the prioritized product backlog and protecting the sprint backlog, while using value-based prioritization, cross-functional teams, and continual integration.

Integrate changes into the prioritized product backlog during backlog creation and grooming, update prioritization, honor acceptance criteria, and protect the sprint by deferring major changes to the next sprint.

Identify and assess risks, differentiate them from issues, and manage risk mitigation activities while integrating them into the prioritized product backlog.

identify, assess, and manage risks vs. issues to protect the project vision, evaluating likelihood, budget, time, and value to inform mitigation and decision making.

Recognize that risk is not inherently bad; set the organization's risk tolerance to balance rewards with its mission. Align scrum practices with risk appetite across risk-averse, risk-neutral, and risk-seeking contexts.

Mitigate risks by lessening them and tracking progress with a risk burn down chart. The product owner emphasizes business value while the scrum master coordinates risk responses and stakeholder communication.

Track risks across sprints with a risk burndown chart to manage exposure, monitor risk levels, and drive their timely reduction throughout the project.

Guides the product owner to facilitate awareness of change requests, identify risks, and assure quality across all scrum projects.

Drive iterative quality improvements and reduce technical debt by prioritizing backlog changes for optimized business value, while actively identifying and mitigating risks across product owner, scrum team, and scrum master.

Familiarize yourself with quality management, risk management, and change. Test your knowledge with the chapter five quiz to see how you perform.

Learn how the sprint planning meeting lets the product owner request user stories and the team commit to a sprint, while backlog grooming and sprint review decisions shape deliverables.

Identify key terms in this chapter, including daily stand up, daily scrum, planning poker, scrum board, sprint burn down charts, sprint review meetings, story points, tasks, and user stories.

Explore the product owner's role in sprint planning, negotiating with the team to select user stories for a sprint, and coordinating efforts to align with business needs.

conduct sprint planning with the product owner and scrum team to select backlog items, discuss user stories, and estimate tasks within a timeboxed sprint.

planning poker helps scrum teams estimate user story effort with cards, while the product owner provides business value and the scrum master facilitates consensus for sprint readiness.

Use a relative story points system to estimate costs and effort, benchmarking a known story to gauge others and avoid overcommitment while ensuring delivery.

Explore diverse estimation techniques for Scrum product owners, including wideband Delphi, affinity estimations, and story point ranges, to assess effort levels and project baselines with confidence.

Use index cards to document user stories and tasks with essential details and acceptance criteria, enabling transparent, highly visible sprint planning and risk reduction for the product owner.

Identify and manage dependencies among user stories and tasks, distinguishing mandatory, discretionary, external, and internal dependencies, and plan their order to synchronize team delivery and resource availability.

Learn to estimate user stories using relative criteria and story points, and explore ideal time to gauge effort and manage team workload effectively.

Track and manage user stories with a scrum board, using the sprint backlog, story points, and tasks that move from the to-do list to in process, verification, and done.

A sprint burn down chart helps the team track remaining work against the sprint timeline, showing progress over the 19 working days before the sprint review.

Measure velocity—the number of user stories completed in a sprint—to guide release planning and estimate minimum marketable features. Improve processes and teamwork to deliver a high quality product.

Track sprint progress by linking user stories to overall business value and measurable metrics like revenue, profit, market share, and reduced costs, while monitoring velocity via story points.

Approve initial user stories, estimate effort, and define the sprint backlog and scrum board; trust the team to commit to a realistic workload and deliver high-quality solutions.

Discover the product owner's role during the sprint, engaging daily with the scrum team, answering questions, and fostering collaborative environments that drive the team's success.

Kick off the day with the daily stand-up, a 15-minute standing meeting where the team reports progress, plans the day’s activities, and the scrum master identifies roadblocks.

Learn to run an efficient daily stand-up by reporting what you completed yesterday, what you will complete today, and any impediments, so the team and scrum master can address blockers.

Learn how co-located teams maximize collaboration in a war room, using a scrum board, burndown chart, and cross-functional skills to plan and deliver user stories.

Explore stand-up activities and collaboration in a war room that foster self-organization, motivation, and a results-only culture, with transparency through burn-down charts and scrum boards.

Groom and review the product backlog with stakeholders, the scrum master, and the team to confirm user stories, acceptance criteria, and prioritize changes and risks for the next sprint.

Facilitate ongoing conversations among stakeholders to ensure the Scrum team delivers the most value to the business, and continually groom the product backlog to reflect changing priorities and needs.

Examine the product owner's role during the sprint review and verify that the deliverables meet the acceptance criteria, confirming they are ready for handover.

Sprint review outputs include accepted or rejected deliverables, with rejected work returning to product backlog for next sprint planning, and risks, changes, and earned value updates to the release plan.

The product owner coordinates sprint goals and release plans to ship deliverables, handling their transfer into organizational release and deployment plans that ensure minimum marketable features.

Define potentially shippable sprint deliverables as fully tested and documented features ready for deployment, and determine with customers when to package and release them.

Outline key outputs from ship deliverables, including the deliverables, customer sign-off, and handover to operations and support. Relate transition planning and release plan to revenue recognition triggers for external organizations.

Explore the product owner's responsibilities across a sprint, from sprint planning and daily activities to backlog grooming, deliverable acceptance at sprint review, and handoff to customers.

The product owner stays available across the sprint to support the team, facilitate questions, and groom the backlog to reflect business priorities and risks. By answering why questions and aligning the backlog with business workflows, the PO serves as the voice of the customer and bridges business and technical perspectives.