Scrum Master Certification 2026 + Agile Scrum Certification

Explore the world before agile and scrum, framing the course aims for scrum master certification and agile scrum mastery with a bright upbeat music cue.

The birth of agile unites iterative development over waterfall, enabling early releases and periodic replanning, with scrum as one framework under the agile umbrella.

Compare the waterfall model's phased flow with agile reforms, highlighting how requirement changes trigger delays and defects, and how scrum emerged to manage change and blockers.

Explore the learning objectives for an introduction to scrum, aligning with the scrum master certification track. Gain foundational insights for agile scrum certification in 2025.

Explore scrum as a framework for developing complex products with self-organizing, cross-functional teams. Learn how product and sprint backlogs, daily scrum, and releasable increments enable transparent, adaptive progress.

Master the Scrum Guide as the definitive rule book for Scrum, essential for exam prep and real-world practice. Use the framework for developing complex products, not overkill for simple tasks.

Scrum is a framework, not a complete process, using empirical process control theory to inspect, adapt, and deliver high-quality, shippable increments through transparency, the definition of done, and sprint cadence.

Emphasizes the four formal scrum events—planning, daily scrum, sprint review, and retrospective—and their time-boxed nature, with product backlog grooming recommended as an additional practice.

The scrum team includes the product owner, developers, and the Scrum Master, with developers inside the team and the Scrum Master facilitating to solve impediments.

Explore how incremental deliveries in scrum ensure a potentially useful working product each sprint by defining and refining the definition of done to guarantee a shippable increment.

Maximize the value of the product and the scrum team's work as the product owner, who alone manages the backlog and prioritizes items amid organizational realities.

Learn how the Scrum Master ensures Scrum is understood and enacted, and leads through servant leadership to facilitate events, remove blockers, and enable self-organizing teams.

Discover the learning objectives of scrum events and how they support agile practices for scrum masters.

Learn how time boxes, or events, structure scrum ceremonies, from sprint planning through sprint retrospective, with the Scrum Master ensuring on-time meetings, clear goals, and continuous improvement.

Scrum events are time-boxed to create regularity and minimize meetings to a maximum duration, ensuring the team inspects progress, adapts plans, and delivers a product increment.

Compulsory scrum events preserve transparency and enable inspection and adaptation, with standups and planning ensuring coordination, while the sprint is the heart of Scrum as a time-box delivering an increment.

Learn how sprint planning structures work, including the three topics why, what, and how, assess development team capacity, and set a clear sprint goal to guide the product backlog.

The sprint review brings the scrum team and stakeholders together to inspect work and update the product backlog for the next one-month sprint, a four-hour time-boxed event.

Use scrum artifacts—the product backlog, sprint backlog, and final increment—to maximize transparency and foster a shared understanding of project status, enabling inspection and adaptation via sprint and release burndowns.

Learn how the product owner and team refine the backlog through dedicated meetings, clarify stories, acceptance criteria, and ensure items are ready for sprint planning.

Prioritize the backlog through refinement to clarify high-priority items, break down complex work into stories or features, refine acceptance criteria, and ensure readiness for the sprint with product owner oversight.

Cultivate artifact transparency by revealing the product backlog, sprint backlog, and increment to all stakeholders. The scrum master ensures visibility and tracks sprint progress with the burndown.

Define a shared definition of done within the team and, if multiple teams exist, mutually agree on it; align with organizational conventions or tailor it to the product.

Mutually define the definition of done when multiple scrum teams work on the same system or product release, ensuring aligned back end and front end teams to avoid disjointed work.

Define the sprint goal from the sprint backlog to guide team. Describe what the product owner wants to achieve by sprint end, including live match stats and a circuit map.

Product owner explains backlog items and criteria in sprint planning topic 2, while the team asks questions to clarify requirements and commit to prioritized work, with later renegotiation.

Break stories into subtasks and estimate each in hours to plan daily progress toward targets. Product owners, the scrum master, and the team discuss trade-offs and finalize sprint commitment.