Complete Scrum Master Certification Training

Scrum is an iterative and incremental agile framework that fosters a cohesive team and continuous improvement. It defines Product Owner, Scrum Master, Developers, and artifacts—Product Backlog, Sprint Backlog, Increment—and events.

Clarify the three Scrum pillars by explaining transparency, inspection, and adaptation, including a shared definition of done and frequent inspection to detect variances, followed by timely adjustments when needed.

Explore the five Scrum values—commitment, focus, openness, respect, and courage—that guide the team toward sprint goals, with decisions and actions reinforcing these values.

Form the scrum team with a product owner, a scrum master, and developers as a cohesive, self-managed, cross-functional unit. Deliver increments each sprint within a small, nimble 3–9 member size.

Own the scrum product owner role by prioritizing requirements, managing the product backlog, aligning goals with development, engaging stakeholders, and ensuring backlog transparency and sprint readiness.

Learn how the Scrum Master, as a servant leader, champions Scrum, facilitates events, empowers a self-organizing team, and drives value, transparency, and organizational adoption.

Developers are a self-organizing, cross-functional team that translates Product Owner priorities into tangible outcomes, plans the sprint, and upholds the definition of done through daily Scrum.

Identify prohibited items in Scrum and reaffirm roles: Product Owner, Scrum Master, and Developers, while noting developers form a single, cohesive team and the Scrum Master covers the framework.

Explore how four Scrum events—Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective—enable inspection, transparency, and adaptation within a sprint, using the Product Backlog, Sprint Backlog, and Definition of Done.

Examine sprint as a timeboxed container for all Scrum events delivering a releasable increment. Learn how scope is managed, sprint goals, and benefits of short sprints for feedback and value.

Collaborate to create the sprint plan in sprint planning by selecting product backlog items, defining the sprint goal, and forming a sprint backlog to deliver a valuable increment.

Learn how the daily scrum, a 15-minute timeboxed meeting for developers, synchronizes progress toward the sprint goal, plans the next 24 hours, and identifies impediments.

The sprint review is a timeboxed, working session where the team demonstrates completed work to stakeholders, collects feedback, reviews sprint goals, and updates the backlog.

Explore the sprint retrospective, a timeboxed private scrum team meeting that includes the product owner, scrum master, and developers, reflecting on the sprint, identifying improvements, and selecting 2–3 actionable items.

discover how the four scrum events work together: sprint planning, daily scrum, sprint review, and sprint retrospective, detailing purposes, timeboxes, frequencies, and participants for a one-month sprint.

Identify practices not part of Scrum, such as sprint zero and extending the timebox, and affirm Scrum uses sprints, not iterations, with no mandated sizing or backlog refinement.

Explore Scrum artifacts including the product backlog, sprint backlog, and increment, and learn how prioritization, refinement, sprint planning, and the definition of done drive transparency and value.

Learn how the product backlog serves as a dynamic, prioritized source for features, bugs, and requirements in Scrum, guided by the product goal and maintained by the product owner.

The sprint backlog is the developers' plan for the sprint, containing the sprint goal, selected product backlog items, and tasks to deliver the increment.

An increment sums work integrated and tested to meet the Definition of Done, delivering a potentially releasable product and may include increments presented at the Sprint Review to support empiricism.

Identify terms not related to Scrum artifacts, such as definition of ready, continuous integration, test-driven development, and behavior-driven development, and learn to avoid them in Scrum exams.