Scrum Developer Professional - Preparation Course

Explore the Scrum framework with its pillars—transparency, inspection, adaptation—and artifacts—product backlog, sprint backlog, increment—along with commitments, roles, events, and values.

Explore how scrum theory rests on empiricism and lean thinking. See how transparency, inspection, and adaptation guide processes and artifacts toward delivering working software in increments.

Explore the five scrum values: focus, respect, openness, commitment, and courage, and how they underpin transparency, inspection, and adaptation within the scrum team.

Explore how Scrum, since the early 90s, uses incremental, iterative methods to tackle complex adaptive problems across software, hardware, embedded systems, autonomous vehicles, networks, and product and service domains.

Explore how scrum events create transparency, inspection, and adaptation, defining the five time-boxed events: sprint, sprint planning, daily scrum, sprint review, and sprint retrospective, and their roles in focused teamwork.

Learn how to plan a sprint with Sprint Planning, define a clear sprint goal and sprint backlog, and prepare inputs like product backlog, latest product increment, capacity, and past performance.

Discover how the Scrum Master keeps sprint planning within an eight-hour time box and how the development team selects product backlog items to form the sprint goal and sprint backlog.

Explore the daily scrum as a 15-minute, daily, same-time, same-place internal meeting for developers, responsible for its conduct and for brief follow-up meetings as needed.

During daily scrum, the development team leads, with optional observers from product owners and stakeholders who do not disrupt, while the scrum master enforces the 15-minute timebox and removes impediments.

Demonstrate the product increment during sprint review, answer questions, discuss what went well and issues solved, then product owner updates the backlog with items and priorities.

The Scrum team gathers for a sprint retrospective to inspect the last sprint and plan improvements, with the Scrum Master guiding attendance and ensuring a productive, time-boxed discussion.

Inspect the last sprint's people, relationships, processes, and tools to identify and prioritize improvements, then create a non-disruptive plan for the upcoming sprint within the Scrum framework.

The Scrum team comprises the Product Owner, Scrum Master, and developers, with external experts invited as needed. It is a small, self-organized, cross-functional unit accountable for delivering a valuable increment.

Balance self-organization and cross-functionality by sizing the Scrum team for optimal delivery. Reorganize into teams when the team exceeds 10, sharing the common product goal, product backlog, and product owner.