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.

Treat a sprint as a container event bundling the four scrum events into a small project with a sprint goal, a flexible plan, and a quality-focused product increment.

Learn why sprint duration is capped at one month or less and how shorter, fixed, back-to-back sprints without gaps improve inspection and adaptation, reduce risk, and boost predictability.

Learn why sprint cancellation occurs when rapid changes render a sprint redundant, and how shorter, time-boxed sprints, at most one month, reduce cancellation risk, with product owner authority.

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.

Examine why the sprint is valuable, what can be done, and how developers decompose backlog items into one-day tasks, guided by the product owner, sprint goal, and definition of done.

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.

The daily scrum centers on three questions to advance the sprint goal, enabling daily inspection, planning, and impediment removal by a self-organized team.

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.

Invite the product owner, development team, key stakeholders, and the scrum master to the sprint review to inspect the product increment and update the product backlog within a 4-hour timebox.

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.

Explore how the sprint retrospective reviews the last sprint to identify improvements and creates an adaptation plan for the next sprint, grounded in transparency, inspection, and adaptation.

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.