Agile Trainer Certification

Compare waterfall and agile, showing how waterfall delays value with six-month cycles and upfront requirements, while agile delivers MVP-backed monthly increments with continuous customer feedback to reduce risk.

Define a minimum viable product that is usable and inexpensive to change, and use an incremental agile approach to gather early adopter feedback.

Agile is a mindset of four values and twelve principles guiding leadership and team practice, with timebox, cadence, definition of done, and retrospective, supported by Scrum and self-organizing teams.

Explore agile values that prioritize individuals and interactions over processes and tools, and working software over comprehensive documentation, driving collaboration, efficiency, and an adaptive team mindset.

Explore agile values that prioritize customer collaboration over contract negotiation and responding to change over following a plan, guiding teams to build the right product through close customer work.

Explore the agile manifesto and its 12 principles, including delivering valuable software early, welcoming changing requirements, and fostering self-organizing teams with face-to-face collaboration.

Scrum is a lightweight framework, not a methodology, that enables the Scrum Master, Product Owner, and Scrum Team to deliver value through adaptive solutions, and to inspect results with stakeholders.

Explore the scrum framework, rooted in empiricism and lean thinking, with pillars of transparency, inspection, and adaptation, and master its roles, events, artifacts, and commitments for agile trainer certification.

Explain scrum artifacts and commitments, including product backlog and its structure, PBIs, sprint goals, the definition of done, and how the team uses them to measure progress and deliver increments.

Scrum theory rests on empiricism and lean thinking, emphasizing knowledge from experience and waste reduction through iterative, incremental approach with cross-functional team and sprint planning, scrum, daily scrum, and retrospective.

The scrum pillars of transparency, inspection, and adaptation govern visible artifacts like the product backlog, sprint backlog, and increment, with events enabling inspection and guiding adaptation.

Go through the five scrum values—respect, openness, courage, commitment, and focus—and see how their embodiment guides teams, decisions, and learning through transparency, inspection, and adaptation.

The scrum team, up to ten people, includes a product owner, a scrum master, and developers, and works self-managing to deliver a useful increment each sprint.

Contribute to architecture, servers, documentation, tests, and UI to deliver a usable product increment each sprint, while maintaining sprint backlog and upholding the definition of done in a managerless scrum.

The product owner maximizes product value by guiding the scrum team toward a clear product goal and prioritizing the product backlog, while maintaining transparency and accountability to stakeholders.

The Scrum Master establishes the scrum per the Scrum Guide, coaching the product owner and developers to use empirical planning, clear backlog items, and timeboxed events while removing impediments.

Identify stakeholders as formal roles in the Scrum Guide Expansion Pack, including customers, users, decision makers, sponsors, regulators, experts, and AI, and engage them regularly to drive value.

Explore the Tuckman model of group development, from forming to adjourning, to understand team dynamics, collaboration, and leadership across stages.

Understand how the product backlog prioritizes backlog items by ROI to maximize customer value and align the team with the product goal, under the product owner's transparent, dynamic guidance.

Articulate a single, measurable product goal that guides the product backlog and sprint planning, aligning the scrum team toward a long-term objective, refined during sprint reviews.

Explore sprint backlog, a key scrum artifact detailing the product code, sprint goal, and PBIs, plus the plan for delivering each PBI through refining, coding, and testing as it evolves.

Define the sprint goal as the sprint's single objective that explains why the sprint exists, guiding focus and flexibility on how PBIs are implemented within the sprint backlog.

Discover how increments in scrum deliver usable value by building on prior increments toward a product goal, ensuring cohesion and quality through the definition of done and continuous release.

Define the definition of done as a formal description of the increment state when it meets quality measures. This practice creates transparency, quality control, and accountability across Scrum teams.

Agile product development using scrum guides teams from product idea to a potentially shippable increment, aligning vision, market insights, and prioritized features through backlog, sprints, sprint planning, and continuous improvement.

Learn how user stories break down complex software into valuable, testable pieces by focusing on who, what, and why, guided by the invest criteria for agile delivery.

Explore the three Cs of good user stories: card, conversation, and confirmation, to help agile teams write clear, actionable stories with defined acceptance criteria that deliver real value.

Learn to prioritize product initiatives using the rice framework—reach, impact, confidence, and effort—calculate a score, and make data-informed roadmap decisions.

The sprint, scrum's heartbeat, uses fixed lengths (two weeks, max one month) to deliver increments, protect the sprint goal, refine the product backlog, and negotiate scope with the product owner.

Explore how a sprint acts as a container for all Scrum events: planning, daily scrums, reviews, and retrospectives, while delivering a product increment at sprint end.

Follow the Scrum Guide to inspect and adapt artifacts through every scrum event, ensuring transparency and regularity. Maintain fixed times and places to minimize unrelated meetings and clutter.

Discover how sprint planning aligns the scrum team to answer why, what, and how for upcoming sprint, using the product backlog to create a forecasted sprint goal and sprint backlog.

Explore how the daily scrum, a 15-minute time-boxed event, helps developers inspect progress toward the sprint goal and adapt the plan for the next 24 hours.

Inspect the sprint outcome within a four-hour time box, have stakeholders test the product, and update the product backlog with feedback for strategic planning.

Discover how sprint retrospectives drive continuous improvement by inspecting people, processes, tools, and the definition of done, turning insights into timeboxed, actionable changes for the next sprint.