Agile Trainer Certification

Compare waterfall and agile approaches, and learn how to build an MVP through short cycles that deliver increments, gather customer feedback, and reduce risk.

Learn to define minimum viable product and apply incremental agile approach that delivers a usable version early, gathers customer feedback, and evolves from a skating board to a car.

Explore agile as a mindset guided by four values and twelve principles, applied through practices like scrum, self-organizing teams, cadence, time boxes, and retrospectives, with design thinking, XP, and SAFe.

Learn how agile values prioritize individuals and interactions over processes and tools, and working software over comprehensive documentation, to boost collaboration, productivity, and adaptability.

Explore agile values of customer collaboration over contract negotiation and responding to change over following a plan, driving adaptability and customer satisfaction.

Explore the agile manifesto and the 12 principles, from delivering valuable software to satisfy the end customer early and continuously, to self-organizing teams and continuous improvement.

Define scrum as a lightweight framework, not a methodology, that enables value through adaptive solutions for complex problems, with backlog, commitments, and roles like Scrum Master and Product Owner.

Explore the scrum framework, grounded in empiricism and lean thinking, with pillars of transparency, inspection, and adaptation, plus accountabilities, events, artifacts, and commitments like product goal and definition of done.

Learn how Scrum artifacts and commitments drive transparency and progress, focusing on the product backlog structure, sprint backlog, and defining product and sprint goals, plus the definition of done.

Learn scrum theory grounded in empiricism and lean thinking, focusing on waste reduction, iterative and incremental delivery, cross-functional teams, and sprint events promote transparency, inspection, and adaptation to maximize value.

Explore how the Scrum pillars—transparency, inspection, and adaptation—drive visibility of the product backlog, sprint backlog, and increment, enabling progress toward sprint and product goals via formal inspection events.

Scrum values: respect, openness, courage, commitment, and focus drive agile culture and align the team with goals. They guide behavior and decisions toward sprint goal, reinforcing transparency, inspection, and adaptation.

Discover the scrum team's ten or fewer people structure and accountabilities, including product owner, scrum master, and developers, focused on one product goal, self-managing and responsible for all product-related activities.

Plan the sprint backlog, ensure quality by following the definition, adapt daily toward the sprint goal, and deliver a usable product increment within a scrum team.

Learn how the product owner maximizes value by developing and communicating the product goal, managing and ordering the product backlog, and ensuring backlog transparency for all stakeholders.

The scrum master establishes scrum per the scrum guide, ensures time box events and artifacts are used, and coaches the product owner and team to deliver high value increments.

Identify stakeholders defined in the Scrum Guide Expansion Pack, including customers, users, regulators, sponsors, and AI, and understand how regular engagement delivers value.

Discover Tuckman's five stages—forming, storming, norming, performing, and adjourning—revealing how teams evolve and how leaders guide collaboration for stronger, more productive outcomes.

The product backlog is a living, ordered list of product backlog items and product code for sprints, managed by the product owner to maximize value through ROI, dependencies, and risk.

The product goal is a long-term objective guiding the product backlog and one active goal at a time, crafted by the product owner and refined in sprint reviews.

Explore how the sprint backlog defines the sprint goal, selected PBIs, and plan to deliver the increment. It is highly visible and evolves while the sprint goal remains intact.

define the sprint goal as a single objective that explains why the sprint exists, guides the sprint backlog, and provides focus and flexibility for the team.

Explore what an increment is in scrum, and how each additive, usable increment advances the product goal while delivering value and being thoroughly tested before release.

Define the definition of done as a formal description of the increment that meets quality measures, ensuring transparency and a shared understanding, with increments released only when criteria are met.

Learn how the scrum framework guides agile product development from idea to market with a vision, backlog, sprints, and improvement, using the Book Wonder AI bookstore to illustrate value delivery.

Master user stories from the end-user perspective to express who, what, and why, deliver valuable, testable features, and apply invest criteria for independent, negotiable, estimable, small, testable work.

Learn the three Cs of good user stories—card, conversation, and confirmation—and how ongoing dialogue and clear acceptance criteria help agile teams deliver real value.

Apply the Rice framework to objectively prioritize product initiatives by evaluating reach, impact, confidence, and effort, then compute a score to rank features and guide roadmaps.

Discover how WSJF, a SAFe prioritization method, ranks backlog items by cost of delay over size. Learn to estimate value, time criticality, and risk reduction to prioritize features.

Learn how sprints drive scrum by maintaining fixed lengths, protecting the sprint goal, and delivering incremental product increments for shorter learning cycles and actionable customer feedback with empirical risk reduction.

Learn how a sprint acts as a container for all Scrum events, including planning, daily scrum, sprint review, and retrospective, while delivering a product increment each sprint.

See how each scrum event inspects and adapts product backlog, sprint backlog, and product increment through feedback. Emphasize transparency and adherence to the Scrum guide with fixed times and places.

sprint planning brings the scrum team together to decide why, what, and how for the one-month sprint within a timebox of eight hours, producing the sprint goal and sprint backlog.

Daily scrum is a 15-minute time-box for developers to inspect progress toward sprint goal and plan the next 24 hours, with optional attendance by the Scrum Master and Product Owner.

Master sprint review as an inspect-and-adapt event in scrum. Align the team and stakeholders to inspect the increment, time-boxed to four hours, and update the product backlog for future work.

Boost team performance with sprint retrospectives that inspect past sprints, identify actionable improvements to people, processes, and tools, and refine the definition of done for faster, better sprints.