Scrum Product Owner Professional - Preparation Course

Learn how Scrum uses short sprints to deliver a working product increment, incorporate client feedback, and adapt requirements within a framework built on roles, artifacts, events, values, and pillars.

Explore the scrum framework, its pillars of transparency, inspection, and adaptation. Learn how product backlog, sprint backlog, and increment drive commitments, roles, events, and values.

Explore how scrum theory, founded on empiricism and lean thinking, uses transparency, inspection, and adaptation to inform decision making from experience and deliver working software through increments.

Explore the five Scrum values—focus, respect, openness, commitment, and courage—and how they support transparency, inspection, and adaptation for a successful sprint and goal.

Scrum uses an incremental, iterative approach to solve complex adaptive problems and deliver complex products across software, hardware, and autonomous systems. Expands market research, operations, and sectors worldwide.

Explore how the three pillars sustain the scrum framework and enable transparency, inspection, and adaptation through five time-boxed events, including sprint, sprint planning, daily scrum, sprint review, and sprint retrospective.

A sprint is a container event comprising Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, delivering product increment with a flexible work plan while preserving sprint goal and quality.

Limit sprint duration to one month or less to enable frequent inspection and adaptation, reduce risk and complexity, and improve predictability, with fixed back-to-back sprints and no gaps.

Learn how fast-changing environments can render a sprint redundant and trigger cancellation. Timebox sprints to one month or less to reduce cancellation risk, with the product owner authorized to cancel.

Learn how sprint planning defines the sprint goal and creates the sprint backlog using inputs like product backlog, latest increment, team capacity, and past performance, within an eight-hour frame.

Coordinate the sprint planning to bring the entire scrum team together to set the sprint goal, clarify product backlog items, and form the sprint backlog within the eight-hour time box.

Explore why a sprint is valuable, what can be done this sprint, and how the work will be done, finalizing the sprint goal with the product owner guiding the team.

Explore the daily scrum as a 15-minute, same-time, same-place internal meeting for developers to synchronize work and support ongoing collaboration with sprint planning.

Answer three daily questions in a 15-minute daily scrum to inspect progress, plan next work, and surface impediments, guiding the team toward the sprint goal and enabling quick adaptation.

Inspect the increment delivered at the end of the sprint, gather feedback, and revise the product backlog to plan the next sprint within a time-boxed four-hour limit.

Sprint review demonstrates product increment and updates the backlog, inviting the product owner, development team, key stakeholders, and Scrum Master to inspect and provide feedback within a 4-hour time box.

The sprint review demos the product increment and answers questions about it. The product owner updates the backlog, noting done, partially done, and remaining items, informed by stakeholder feedback.

Learn how the sprint retrospective inspects the last sprint, identifies improvements, and creates an adaptation plan for the next sprint, guided by transparency, inspection, and adaptation.

Attend the sprint retrospective to inspect the last sprint and plan improvements with the scrum master, product owner, and development team, ensuring a focused, positive three-hour time-boxed event.

Inspect last sprint by evaluating people, relationships, processes, and tools; identify and prioritize improvements, and create a non-disruptive plan for the upcoming sprint within the Scrum framework.

The scrum team comprises product owner, scrum master, and developers, while experts and stakeholders advise during events; teams are self-organized and cross-functional, accountable for a valuable increment.

Keep scrum teams small and cross-functional, typically ten or fewer members, to stay self-organized and deliver increments; otherwise reorganize into teams sharing a Product Goal, Product Backlog, and Product Owner.