Agile Coach Certification

Waterfall delivers a first release after six months through sequential requirement, design, implementation, and verification, while agile uses one-month cycles with MVP increments and customer feedback to reduce risk.

Learn how to build a minimum viable product through an incremental, feedback-driven approach, using early adopter input to deliver a usable board and progressively add features toward a full car.

discover how agile is a mindset guided by four values and twelve principles, shaping practices like scrum, self-organizing teams, definition of done, cadence, and retrospectives, plus design thinking, XP, SAFe.

Discover how agile values prioritize individuals and interactions over processes and tools, and working software over comprehensive documentation, to boost collaboration, efficiency, and adaptability in software teams.

Discover how agile values prioritize customer collaboration and responding to change over contracts and plans, enabling teams to build the right product by embracing feedback and flexibility.

Explore the agile manifesto and its 12 principles, including early delivery, welcoming changes, working software, business and developer collaboration, self-organizing teams, and face-to-face communication.

Define scrum as a lightweight framework, not a methodology, delivering value through adaptive solutions for complex problems. Outline roles, artifacts, and sprint cycle from backlog to increment with stakeholders' feedback.

Explore the scrum framework—based on empiricism and lean thinking, with transparency, inspection, and adaptation—covering accountabilities, events, artifacts, and rules for a lightweight, difficult-to-master agile approach.

Explore scrum artifacts and commitments, including the product backlog, product goal, sprint backlog, sprint goal, and definition of done, plus roles improving transparency and measurable progress.

Scrum theory builds on empiricism and lean thinking, with three pillars of transparency, inspection, and adaptation, using iterative, incremental work by a cross-functional team to maximize value via sprint events.

Master the scrum pillars of transparency, inspection, and adaptation, and see how product backlog, sprint backlog, and increment artifacts and events enable empirical progress toward sprint and product goals.

Explore the five scrum values—respect, openness, courage, commitment, and focus—as the lifeblood of scrum, guiding openness, commitment, and focus toward the sprint goal, product goal, and daily goal.

Explore the scrum team, its roles (product owner, scrum master, developers), and the one product goal, a self-managing, cross-functional unit delivering a valuable increment within ten or fewer members.

Developers in scrum teams drive a product increment by planning the sprint backlog, upholding the definition of done, adapting daily, and maintaining accountability without a manager.

Discover how the product owner maximizes value by directing the product goal, prioritizing and communicating the product backlog, and ensuring transparency for stakeholders and the scrum team.

The scrum master establishes scrum per the Scrum Guide, enables team effectiveness, and facilitates events, artifacts, time-boxing, and product backlog management with the product owner and stakeholders for high-value increments.

Explore how the Scrum Guide expansion pack formalizes stakeholders into a broad role, including customers, users, decision makers, regulators, sponsors, experts, and AI or laws to deliver value.

Explore the Tuckman model of group development, outlining forming, storming, norming, performing, and adjourning to guide leaders in navigating team dynamics and boosting collaboration.

Define and manage the product backlog as the scrum artifact that plans future sprints, prioritized by value and ROI, managed by the product owner, kept transparent, and is never complete.

define a product goal as a long-term, measurable target guiding the product backlog and sprint work toward a single active objective. it clarifies scope, boundaries, and progress through sprint reviews.

Learn to manage the sprint backlog as the plan for delivering the sprint goal, detailing selected PBIs, tasks, and acceptance criteria, with ongoing refinement and visibility to stakeholders.

Define the sprint goal as a commitment and single objective that explains why the sprint exists, guiding PBIs and allowing renegotiation with the product owner while keeping the goal intact.

Understand the increment in scrum as a concrete, additive step toward the product goal, delivering usable, quality value with each verification and definition of done.

Define the definition of done (DoD) as the formal state where an increment meets quality measures—code reviewed, tests pass, and docs updated—ensuring transparency and release readiness.

Explore how the scrum framework guides agile product development from a product idea to a shippable increment, prioritizing features and planning sprints for customer value.

Master the user story concept in agile product development, apply as a user I want so that format, and uphold invest criteria to deliver valuable, testable features.

Master the three Cs of good user stories: card, conversation, and confirmation, by crafting concise cards, fostering ongoing dialogue, and defining clear acceptance criteria for agile delivery.

Master the Rice framework to prioritize product initiatives by quantifying reach, impact, confidence, and effort. Learn to calculate the Rice score and make data-informed roadmap decisions.

Describe the sprint as scrum's heartbeat with fixed length and product backlog refinement. Deliver a product increment each sprint, protect the sprint goal, and forecast progress with burndown charts.

The sprint acts as a container for all other scrum events—planning, daily scrum, review, and retrospective—and ends with a product increment, with the next sprint starting afterward.

Inspect and adapt scrum artifacts: product backlog, sprint backlog, and product increment, at every scrum event. Follow the Scrum guide to enable transparency and regularity with fixed times and places.

Learn how sprint planning in the scrum framework defines the why, what, and how, guiding the sprint backlog and sprint goal into a forecasted plan for the team.

Inspect progress toward the sprint goal and adapt the plan for the next day during a 15-minute, time-boxed daily meeting for developers.

Lead sprint review as a time box, a core inspect-and-adapt event, aligning stakeholders with the sprint increment and updated product backlog through collaboration and feedback.

Master the sprint retrospective to inspect people, processes, tools, and the definition of done, producing actionable improvements and an adaptive definition of done for faster, more effective sprints.