The Ultimate Agile Leader Certification Training

Explore agile principles and scrum fundamentals, contrasting adaptive agile with predictive waterfall approaches, to refresh knowledge and prepare for certification.

Explore predictive, plan-driven waterfall versus adaptive agile development, and see how Scrum uses one-month sprints to deliver incremental, iterative software in a dynamic environment.

Explore how the agile manifesto guides flexible, collaborative software development with four core values, iterative delivery, and twelve principles that prioritize customer value and responding to change.

Agile rejects detailed upfront plans, using incremental planning with a transparent product backlog and sprint backlog, guided by adaptation and value from customer feedback.

Discover how Scrum, a lightweight framework, uses empiricism and lean thinking to deliver value through transparency, inspection, adaptation, and cross-functional, self-managing teams with product backlog, sprint backlog, and increment.

Explore the scrum framework with sprint planning, daily scrums, reviews, and retrospectives, and learn about product and sprint backlogs, the increment, and definitions of done for adaptive delivery.

Maximize product value by delivering frequent increments, eliminating waste, and releasing small increments early; inspect and adapt to shorten time to market and boost customer happiness.

Outline agile fundamentals, contrast agile with waterfall, and cover iterative and incremental development, time boxing, and Scrum roles, events, and artifacts for value maximization.

Meet the scrum team, a cross-functional, self-managing unit including a scrum master, product owner, and developers, focused on delivering a valuable increment each sprint toward the product goal.

Act as the product owner to maximize value by managing the product backlog, defining the product goal, ordering items, and communicating with stakeholders and the development team.

Learn how the product goal anchors backlog, guides the Scrum team toward the product vision, and how the product owner ensures backlog clarity and value through sprint planning and review.

The scrum master establishes scrum per the Scrum Guide, coaches the team and organization, removes impediments, and facilitates backlog management, self-management, and empirical planning for delivering value.

Learn how the scrum master acts as a facilitator and true leader, enhances team effectiveness, and guides stakeholder collaboration while distinguishing servant leadership from leadership that serves.

Developers in Scrum create a usable increment each sprint by sizing backlog items with story points and forecasting the sprint backlog toward the sprint goal with the product owner.

Explore how the scrum team defines roles and crafts a product definition, refines backlog items, and turns PBIs into increments through developer-led planning and a shared definition of done.

Discover how the Scrum value of commitment urges teams to pursue the sprint goal, even as plans change and PBIs shift.

Clarify the scrum roles—Scrum master, product owner, and developers—within a cross-functional, self-managing team accountable for product backlog management, sprint goals, and a valuable increment each sprint.

Explore the five official scrum events—sprint planning, the sprint, daily scrum, sprint review, and sprint retrospective—timeboxed to enable transparency, inspection, and adaptation, with the sprint as their container.

Discover the sprint container, the heartbeat of scrum, where sprint planning, daily scrums, sprint preview, and sprint retrospective create usable increments toward the product goal.

Plan the sprint through collaborative sprint planning, defining sprint goal, selecting sprint backlog items, refining backlog, forecasting capacity, delivering an increment.

The Scrum Master ensures the 15-minute time-boxed daily scrum occurs, mandatory for developers, as they inspect progress toward the sprint goal, plan the next day, and product owners may attend.

Inspect and adapt the sprint increment with the Scrum team and key stakeholders, reviewing what was accomplished against the product goal, and adjust the product backlog to seize new opportunities.

After the sprint review, the sprint retrospective time-boxes up to 3 hours to inspect the last sprint and boost quality and effectiveness, focusing on context over content and identifying improvements.

Master how sprints turn ideas into usable increments and drive value through sprint planning, daily scrum, reviews, and retrospectives that refine the backlog and definition of done.

Explore scrum artifacts and their commitments, the product goal, sprint goal, and definition of done, to maximize transparency and enable inspection and adaptation.

Maximize value by ordering the product backlog, the single source of work, with the product owner accountable and developers selecting top items through ongoing backlog refinement.

The sprint backlog combines the sprint goal, the selected backlog items, and a plan for delivering the increment, and is updated throughout the sprint and highly visible.

Learn how increments build the product by adding usable, verified features each sprint. The whole Scrum team decides releases, and only work meeting the definition of done becomes an increment.

Define the definition of done as a formal description of the increment that meets quality measures and is usable for end users, following organizational standards or a team-created definition.

Define the product goal as the future-state target guiding the Scrum team's backlog and increments, with a single protocol at a time, measurable and refined via sprint reviews.

Recap the product backlog, sprint backlog, and increment with their commitments: product goal, sprint goal, and definition of done; outline ownership and alignment toward the product goal.

Explore agile leadership concepts, including the top four leader behaviors, empiricism, motivation, and managing sprint interruptions, to build high-performing co-located or distributed teams.

The top four behaviors empower agile leaders to foster thriving teams through experimentation, leading by example, facilitation, and collaboration with the product owner and Scrum teams.

Learn how agile leaders apply empiricism—making decisions from evidence and experience, guided by transparency, inspection, and adaptation, using small experiments and frequent releases to navigate complex product development.

As an agile leader, navigate conflicts and complaints by asking questions, fostering openness, and facilitating a self-managing environment that respects Scrum values and team autonomy.

Explore intrinsic vs extrinsic motivation in agile teams, emphasizing mastery, autonomy, and purpose to boost long-lasting engagement while avoiding reward systems that single out individuals and micromanagement.

Learn how evidence based management guides agile leadership to improve value through empirical experimentation, inspection and adaptation, transparency, and Kaizen improvement under uncertainty.

Apply evidence-based management to focus on outcomes over activities and outputs. Monitor unrealized value, current value, ability to innovate, and time to market to drive customer value.

Minimize interruptions during the sprint by exploring knowledge transfer to fill missing skills, leveraging solutions outside the Scrum team, and planning sprint goals conservatively without extending the sprint.

Let teams self-organize into small, cross-functional units of ten or fewer, centered on end users, and measure success with metrics like conversion rate.

Explore how great scrum teams form, including co-located and distributed setups, overcome time-zone and trust challenges, progress through forming, storming, norming, and performing to achieve high performance.

Learn how velocity measures a scrum team's completed work using average story points across sprints to forecast future work, while noting it does not directly reflect value.

Avoid comparing scrum teams by velocity and story points, as these are team-specific and not direct value; instead maximize product value through knowledge work, flexible utilization, and multi-skilled collaboration.

The recap highlights agile leadership that creates thriving teams, encourages experimentation, removes impediments, and relies on empiricism and small increments to deliver value through collaboration.

Explore six agile leadership stances from facilitator to systems thinker, and apply practical techniques to foster true team ownership, shape culture, and develop emotional intelligence for lasting impact.

Explore the six key agile leader stances, starting with the facilitator who creates space for all voices and builds trust across distributed teams.

Lead through coaching by asking powerful questions, encouraging reflection, and unlocking team potential, then reimagine scrum to emphasize why, focus on sprint goals, and meaningful stakeholder feedback.

Lead with a visionary stance that links daily work to the future, and serve the team by removing obstacles and prioritizing long-term quality.

Learn to adopt systems thinking and situational leadership across six agile stances—from facilitator to systems thinker—aligning end-to-end value streams, cross-functional feature teams, and continuous integration for better organization-wide performance.

Learn how to facilitate true team ownership by establishing conditions that foster intrinsic motivation, empower teams to make domain decisions, and avoid anti-patterns that suppress initiative.

Learn to foster true team ownership by cultivating psychological safety, applying decision clarity, maintaining outcome focus, enforcing bounded autonomy, and promoting continuous learning.

Explore common ownership killers—swooping, helicopter, safety net, and pressure cooker leaders—and learn practical techniques to foster owner mindset, including questions, decision frameworks, outcomes, sprint goals, and ownership retrospectives.

Establish celebration, transparency, question, and retrospective habits to deliberately shape agile culture with psychological safety, learning, customer focus, collaboration, and adaptability.

Lead agile culture by practicing gemba walks and a decision journal, making context visible, and address hero, permission, and perfection anti-patterns.

Develop self-awareness and emotional intelligence to navigate uncertainty and balance leadership tensions in agile leadership. Practice daily intention, reflection, and feedback to foster team ownership and shape organizational culture.

Develop agile leadership by adopting diverse stances—facilitator, coach, catalyst, visionary, and systems thinker—fostering ownership, psychological safety, and continuous learning to unlock team impact.

Unlock a quick roadmap to the certified agile leader exam, focusing on exam approach, dos and don'ts, plus updated practice resources and eight tips in the next video.

Aim for an 85% passing score by applying eight practical tips to ace the agile leader exam: eliminate wrong options, read questions carefully, pace yourself, minimize distractions.

Celebrate completing the ultimate agile leader certification training. Embrace the Kaizen spirit of continuous improvement through experiments, inspect, and adapt in product management and life.