Professional Scrum Product Owner Training Course

Explore the essentials of scrum by introducing the events, roles, and artifacts that drive a professional scrum product owner project.

Explore an introduction to scrum for product owners that highlights teamwork, accountability, and progress toward a well-defined goal, with the pillars of transparency, inspection, and adaptation.

Explore how Scrum, a collaborative framework for complex, adaptive problems, delivers incremental, iterative increments through two-week sprints, enabling continuous learning, inspection, and adaptation.

Survey agile methodologies and the Agile Manifesto, introducing key approaches like BDD, DDD, XP, ASD, Crystal, DSDM, Scrum, and Kanban, and explain how organizations select a suitable method.

Explore the Agile Manifesto's four values and how Scrum prioritizes individuals and interactions, working software, and customer collaboration over processes and tools, documentation, contract negotiation, and responding to change.

Explore the scrum guide as the authoritative reference for scrum, detailing roles, events, artifacts, and rules. Encourage every scrum practitioner to review it and access scrumguides.org.

Explore scrum events as a framework for inspection and adaptation that uses time-boxed meetings, including the daily scrum and sprints, to focus the development team's work and feedback.

Discover how a two-week sprint delivers a potentially realizable increment, drives continuous customer feedback, and aligns with the product backlog and sprint events in Scrum.

Explore sprint planning by using the product backlog, increment, and velocity to define the sprint goal and sprint backlog for a checkout feature, with time-boxing for four-week sprints.

Participate in the daily scrum, a 15-minute development team meeting where members share yesterday’s work, today’s plan, and blockers.

During sprint review, stakeholders and customers provide feedback as the team presents the increment for acceptance; inputs are product backlog and increment, outputs a revised backlog and an accepted increment.

The sprint retrospective invites the scrum team to evaluate itself, discuss what went well and what went badly, and identify improvements using velocity and the definition of done.

Participate in a sprint exercise that tests your understanding by analyzing an email scenario. Identify missing events, participants, and text, and anticipate the forthcoming solution in the next video.

Prioritize items in the product backlog, move them into sprint planning, and transfer to the team-owned sprint backlog. Execute daily scrums, deliver increments, and conduct sprint reviews and retrospectives.

Identify the key scrum roles—the product owner, scrum master, and development team—and see how domain familiarity and team composition shape sprint backlog ownership.

Discover how scrum artifacts—the product backlog, sprint backlog, and increment—provide transparency, adapt to market or regulatory changes, and guide sprint outcomes.

The product backlog, owned by the product owner, defines work to be done and serves as input for sprint planning. Each backlog item includes business value, description, and acceptance criteria.

Learn how the development team owns the sprint backlog, two parts—work to complete and a plan to complete it—driven by high-value or regulatory-impact product backlog items.

Estimate product backlog items with planning poker using Fibonacci story points to establish relative sprint velocity and avoid treating forecasts as promises of delivery, fostering collaboration.

Explore the scrum board as a sprint snapshot that provides transparency to stakeholders. Visualize stories across backlog, in progress, testing, and done, guided by the definition of done.

Explore the essentials of Scrum through a quick exercise, covering agile methodologies, the Agile Manifesto, and core Scrum events, artifacts, and story points, including minimum Scrum board columns.

Recaps the essentials of Scrum from the professional scrum product owner training and previews the upcoming videos covering the product.

The product owner defines product features, determines business value for each backlog item, and prioritizes items by value, while representing the customer's voice to the scrum team.

The product owner is the domain expert and customer representative who aligns the sprint increment with customer needs. They own the product backlog and maximize value for the organization.

Identify essential product owner attributes in part 1: decisive decisions and transparency. Negotiate between business and development, maintain team spirit, and trust the team to forecast and own the sprint.

Balancing customer, team, and organizational needs, product owner attributes part 2 champions the development team, boosts morale by recognizing good work, and uses velocity to address strengths and weaknesses.

The product owner is a single person who speaks for the product, while the team and stakeholders influence it but are not the product owner.

Understand what a product owner is not: project manager, manager, or customer, and how they represent the customer with continuous feedback to drive value in a self-organizing development context.

This video presents a diagram of the product owner's role within a scrum team, clarifying what the product owner is and isn't, and how they influence the product backlog value.

Empiricism forms the foundation of scrum, guiding the product owner through inspection, adaptation, and transparency in decisions with customers and stakeholders.

Explore inspection as a core scrum pillar with formal opportunities in sprint planning, daily scrum, sprint review, and sprint retrospective, guiding product backlog and increment evaluation.

Learn how adaptation drives Scrum success by embracing frequent feedback, inspecting and adapting every sprint, and aligning the product backlog, definition of done, and workflows with customer needs.

Explore how transparency across scrum artifacts and events provides visibility to stakeholders and customers. Learn how sprint planning, backlogs, increments, and retrospectives build trust and a clear definition of done.

Discover how transparency applies to artifacts like the product backlog and sprint backlog, and how open sprint reviews with customer demos foster early feedback and a shared language.

Engage in an exercise on inspection, adaptation, and transparency in the professional scrum product owner course, mapping items to the three pillars by marking I, A, or T.

Explore how transparency appears in visible artifacts like the backlog and scrum board, and how inspection, adaptation, and test-driven development shape the definition of done and daily scrum.

Explore the roles within a scrum project, including the scrum master, the solution development team, and stakeholders, and learn how they collaborate for successful product outcomes.

Discover the Scrum Master’s role as coach and facilitator, removing impediments, guiding events, mentoring the team on time-boxes, and fostering collaboration to deliver high-quality increments.

The solution development team is a cross-functional, self-organizing group that owns the sprint and product backlogs to deliver a valuable increment.

Define customers as external clients and stakeholders as internal interests, and have the product owner interface with them for continuous feedback on backlog items, business value, and increments.

Practice a hands-on exercise to apply your product owner role within a scrum team by matching behaviors to solutions in a task table.

Product owners gain from a solution-oriented exercise that emphasizes active listening, backlog refinement, sprint planning preparation, consistent leadership, and open communication through face-to-face channels.

Engage in an exercise on the product owner role within a scrum project for online sales. Spot flaws such as incomplete backlog before sprint planning and external QA.

Highlight correct product owner practices: the owner must be a single, dedicated role, visible to the team, responsible for a backlog, consistent sprint cycles, and quality assurance within the sprint.

Recap the current stage of the professional scrum product owner training and refresh the essentials of scrum. Review previous videos and preview the upcoming focus on the product backlog.

The product backlog is a prioritized, living list of uncompleted work from the customer perspective. It is created collaboratively, owned by the product owner, and feeds the sprint backlog.

Identify product backlog items as the building blocks of the product backlog, each with a name, description, business value, and forecasts, addressing features, requirements, enhancements, or maintenance.

Explore how a PBA card visually represents a product backlog item, detailing fields like name, description, priority, forecast date, sequential number, dependency, and sprint.

Explore pba categories in the product backlog, including implementation, design tbi, architectural, security, and performance, with a focus on quality assurance and definition of done.

Explore compulsory pbis that must appear in every sprint, using a parking lot visual template, and understand the definition of done and organizational requirements.

Explore how scrum's iterative and incremental approach uses ongoing inspection and adaptation to evolve the product backlog item while continually aligning architecture with the baseline across sprints.

Assess the product backlog by stakeholder influence and sprint priorities. Deliver the best value for stakeholders and the organization, and introduce the deep backlog concept.

explains the deep backlog concept, showing that upcoming sprint items must be detailed, near-term estimates precise, the backlog is emergent and dynamic, and items are prioritized from top to bottom.

Detail the top product backlog items with detailed clarity and priority for the next sprint, using the stacking books analogy to illustrate sequencing.

Estimate every product backlog item before sprint planning, using fibonacci sizing, and break large items into smaller backlog items to fit within a sprint, illustrated with an e-commerce logging example.

Understand the emergent, living product backlog that evolves over time as new regulations, new features, or developments arise, causing priority changes among estimated backlog items from sprint to sprint.

Organize your product backlog with deep visuals, detailing high-priority items, prioritizing top items, estimating efforts, and ensuring they're ready for the sprint to flow smoothly.

Discover the attributes of a quality product backlog, including fit for purpose, two to three sprints worth of work, forecasted items, visible, ordered by value, collaborative inputs, dynamic living document.

Learn to manage the product backlog by segmenting into categories (maintenance, technical debt, UI) and planning in two to three sprints, using a parking lot diagram to align with releases.

Learn how the product backlog is a living, dynamic document and how the refinement meeting, with stakeholders and the development team, reviews and updates items within a 10 percent sprint.

Explore how a technical planning meeting identifies and intervenes on software technical debt, clarifies team knowledge, and creates backlog items for features, bugs, quality assurance, maintenance, and technical debt.

Understand rough order of magnitude estimation, its plus/minus 50 percent accuracy, and how subject matter experts, small/medium/large sizing, and executive prioritization guide planning.

Apply the 20/30/50 rule to the product backlog to balance refinement, ensuring 20 percent has complete user stories while 50 percent remains loosely defined or technical debt.

Create and order a 20-item product backlog, move the top five items to a ready backlog, and document scope, stakeholders notes, plan, and release readiness to strengthen product owner practice.

Richmond Farms outlines a B2C marmalade website that lets consumers buy directly, sources marmalade from suppliers, and aims to be a one-stop worldwide hub for all things marmalade.

Take on the product owner role to design a secure B2C Richmond farms retail site with two-day delivery and supplier portals for B2B inventory, pricing, and ordering.

Explore a secured retail B2C PBI items approach, detailing security epics and prioritized user stories for registering, logging in and out, basket management, checkout, delivery details, and newsletters.

Explore the proposed B2B PBI items for admin teams, detailing epics like security, sales, and contact management, plus user stories for register, log in, log out, and offline access.

Present the proposed solution for inventory management backlog items, including a separate portal to set retail prices, place reorders, and group epics with PBI cards on the B2C site.

Recap the essentials of scrum, review the product backlog and sprint backlog, and clarify the product owner's role, while previewing the next focus on the product vision.

Define your product vision with an elevator-pitch statement that shows how the product supports the organization, and follow eight tips to keep it short, motivating, and guiding decisions.

Define a motivating product vision that guides every stakeholder and aligns with the company vision, and look beyond the product to describe the change it should create.

Distinguish between product vision and product strategy; keep vision as the goal and path, not a plan, and use collaborative visioning workshops to create a shared, aligned vision among stakeholders.

Discover how to craft an inspiring, big, and concise product vision, and use it to guide decisions, help stakeholders understand the vision, and drive strategy, backlog, and marketing planning.

Learn how to define a vision and mission statement at the executive level, covering nine components from customers and products to employees and public image, and align stories to value.

Analyze Toyota's mission and vision, evaluating alignment with Nikon core components such as customers, products, technology, self concept, planet, public image, and employees, using a framework for strengths and gaps.

Assess mission and vision statements by rating how they cover nine areas—customers, products, markets, technology, survival, philosophy, self-concept, public image, and employees—and test alignment with product and company vision.

Recap the essentials of scrum, the product owner, and the product and sprint backlogs, plus key events, the product vision, and upcoming user stories.

Understand how a user story, owned by the product owner, describes a user’s task, adds backlog item context, and defines user role, action, and value with acceptance criteria.

An epic is a large user story spanning multiple sprints, with no standard definition, that groups stories into backlog hierarchy such as a security epic with login and logout.

Identify how themes group user stories by topic across teams, not backlog levels. See how database, infrastructure, user interface, and reports can be organized under separate teams for two systems.

Discover tips for creating effective user stories: begin with an epic capture, write from the customer perspective, tell the story accurately, and foster collaboration.

Discover tips for straight, concise, effective user stories in scrum. Begin with a broad epic, refine in scrum sessions, and use simple cards or Jira with transparency.

Explore why user stories need dates, including regulatory deadlines, resource constraints, market forces, organizational constraints, and competitive advantage to accelerate time to market.

Discover the 3c's model, the strategic triangle of company, customer, and competitor, to align project value with organizational goals. Apply SWOT analysis and market understanding to guide product decisions.

Align strategic vision with user stories via a collaboratively built user story map with stakeholders. Explore relative sizing by placing stories side by side for a sizing baseline and visualization.

Collaboratively build a user story map with stakeholders and team, from vision to goals to activities, then create epics or user stories for each activity and decompose them into tasks.

Explore a visual user story map that links vision, goals and activities, user stories, and tasks, showing how they align toward the product vision and documenting the map.

Create a user story for the security logging feature, using the three Ws: who, what, and when, based on the previous exercises and the blank story card.

Write a concise user story for the security logging feature of the rich man farms website, detailing login acceptance criteria, priority, business value, and story points, using Jira or CAD.

Review the essentials of scrum, including the product backlog, sprint backlog, scrum artifacts and events, and the product vision, while highlighting user stories and the path to determining product value.

Define and measure product value for backlog items, and compare subjective versus objective value through everyday examples.

Explore whether value is subjective and essential for aligning with the product vision. Prioritize the backlog to guide the development team and estimate return on investment across sprints.

Measure product value by profit using value equals benefits over cost to provide a concrete, quantifiable metric, but profit may overlook user value and be affected by external factors.

Measure product value by market position and market share. It shows how consumers view the product relative to competitors.

Learn to measure product value by utility through quantitative methods and swot analysis, linking customer perception to loyalty and competitive insights.

Measure product value by customer perception to reflect brand and compare over time to competitors; use surveys to gather feedback and gauge item-level utility.

Collaboratively measure product value by estimating level of effort, risk, and cost, then prioritize features while clarifying requirements and communicating profit, utility, and market position.

Discover metrics to measure product value, including revenue, market share, customer satisfaction, cost savings, customer acquisition, customer retention, and user engagement, and use them to inform product improvements.

Learn to measure product value with rice scoring, multiplying reach, impact, and confidence and dividing by effort to compute a score that guides prioritization across projects.

Apply Rice scoring to three hypothetical projects, evaluating reach, impact, confidence, and effort. Decide which project to tackle first based on the results and any prerequisites.

This lecture explains how value drives Scrum planning by prioritizing product backlog items, guiding the team to deliver high-value increments, and releasing frequently to align with customer feedback.

Discover how to ensure your product delivers optimum value by applying technical depth, value, Pareto principle, and MoSCoW, with these principles explored in upcoming videos.

Learn to deliver optimum product value by managing technical debt and delivering minimum viable products, using epics and user stories for debt reduction in sprints.

Apply the Pareto principle to identify the 20 percent of backlog items that deliver 80 percent of product value, guiding focus to reduce technical debt and dependencies.

Explore the MoSCoW prioritization framework and MVP as the bare minimum to validate a software idea, aligning with business goals and target users through sprint-based duration estimates.

Explore MoSCoW prioritization and MVP validation through a hands-on exercise, including an example of Facebook MVP and sprint planning with story points, velocity, and two-week sprints.

This lecture explains applying MoSCoW prioritization to define an MVP, balancing must-haves with technical depth across two-week sprints and velocity planning.

An agenda recap covers the essentials of scrum, including product backlog, sprint backlog, and sprint events, plus product vision, user stories, and using rice to determine product value.

Explore scrum reports that track progress and provide transparency for the development team, including sprint reports and potential reports based on sprint data with upcoming visuals.

Explore a visual representation of scrum reports, including sprint, release burn-down, velocity charts, epic reports, flow diagrams, and how Jira can generate these from software tools.

Discover how to use a burn down chart to track work remaining and sprint goal likelihood, showing progress with days on the x-axis and story points on the y-axis.

Engage in a burn down chart exercise for a two-week sprint, estimating user stories with story points to define mvp scope in a professional scrum product owner course.

Plot a burn down chart by listing backlog items with story points and tracking remaining effort by date, using spreadsheet template, noting negative values for scope changes and ideal trend.

Explore how a burn up chart tracks completed story points toward the sprint total, with story points on the y-axis and days on the x-axis.

Track the release burn down to keep the e-commerce site on track to the projected release date. Use completed and remaining story points to forecast remaining work for each sprint.

Forecast the release of a billing system by estimating 43 story points and applying a four-point average velocity to predict sprint completion.

Explore the release burn down solution by calculating sprint-by-sprint progress using an average velocity of four story points, reducing a total of 26 story points across sprints.

Use parking lot reports to show project health by grouping features into themes and functional areas, with yellow in-progress and green completed status and a percent complete gauge.

Demonstrates using a parking lot technique to visualize feature areas on a project dashboard, using a spreadsheet or Jira to track progress and highlight overdue deliverables.

Recap the essentials of scrum, artifacts, events, and the product owner role, including backlog items, product vision, and user stories. Cover Rice scoring, reporting templates, and release management.

Plan release management to ensure a successful product launch by aligning sprints to release milestones, considering minimum realizable features, product vision, product planning, and capacity with business input.

Explore scrum release planning as a high level, multi-sprint plan (3 to 12 iterations) that defines feature delivery timing, progress monitoring, and release types, using backlog, velocity, and resource goals.

Explains a scrum release planning exercise, estimating sprints and releases under feature-driven and data-driven goals, with a velocity of three points per sprint and two-week sprints.

Learn feature driven release planning in scrum by estimating points, calculating velocity, and scheduling releases after milestones like sign up, log in, and time tracking options.

Master the essentials of scrum, artifacts and events, align sprint and company vision, and apply user stories, story points, RICE, reports, Jira, and bogged down charts templates for release management.

Explore the key references for the professional scrum product owner training, including the Scrum guide and Agile Manifesto, with acknowledgments to contributors.