Scrum Master Certification Training. Be a Master of Scrum

Explore what Scrum is, why it is a framework not a methodology, and how the Scrum Master role, simplicity, pragmatism, and leanness reveal efficacy for tailoring processes and delivering value.

Scrum is a lightweight, adaptive framework that generates value through a product backlog, sprint, and continuous inspection and adaptation, guided by a Scrum Master and Product Owner.

Position Scrum as a lightweight framework, not a methodology, highlighting its flexibility, sprints, daily scrums, and applicability beyond software development.

clarify the scrum master's role as an enabler and facilitator who coaches the team, removes impediments, and protects the process—not a controller or manager.

Explore how simplicity, pragmatism, and leanness make scrum effective by using a basic, pragmatic framework that delivers value incrementally and adapts through regular inspection.

View the Scrum Guide as a flexible framework, not a strict instruction manual, enabling teams to adapt, experiment with formats, tools, and timing in sprint planning.

Scrum reveals the efficacy of our processes by exposing productive versus wasteful practices through transparency, focus on value, and frequent inspect-and-adapt for continuous improvement.

Explore how Scrum can combine with Kanban, XP, DevOps, and design thinking to customize, continuously improve, and deliver value while keeping the core Scrum framework intact.

Explore theoretical foundations of scrum, grounded in empiricism and lean thinking, emphasizing experience, inspection, adaptation, waste reduction, and value creation. Learn how these ideas guide cross-functional teams and incremental delivery.

Compare rationalist and empiricist problem solving, and show how scrum relies on empiricism. Through inspection, transparency, MVPs, and iterative feedback, scrum addresses complex problems.

Emphasize empirical evidence and decision making by planning, conducting, collecting data, and analyzing puck drops from the CN Tower to draw conclusions and iterate.

Explore lean thinking and empiricism within scrum, focusing on maximizing value, eliminating waste, delivering minimum viable product increments, and iterating with stakeholder feedback to guide product development.

Learn how empiricism and lean thinking drive Scrum by inspecting the product increment, leveraging stakeholder feedback, and delivering working increments each sprint while removing impediments and minimizing waste.

Learn how scrum manages predictability and controls risk through iterative sprints and incremental delivery, delivering value in small increments with regular inspection and adaptation for early stakeholder feedback.

Scrum's incremental nature delivers small, valuable increments each sprint, enabling early feedback, flexibility, and risk reduction, with every increment potentially shippable and built from prior work.

Learn how cross-functional scrum teams possess all necessary skills, share knowledge, and acquire new ones to improve efficiency, collaboration, and flexibility in project delivery.

Explore how scrum teams move between sprints with no gap, starting the next sprint immediately after the previous ends, with testing, quality assurance, and integration completed within each sprint.

Focus on the official Scrum Guide to master the core concepts for the Scrum Master certification exam, and avoid non-guide practices like user stories and story points.

Focus on the official Scrum Guide and core Scrum concepts like the Sprint Goal and Definition of Done to efficiently prepare for the Scrum Master Certification exam, avoiding distractions.

Explore the foundations of scrum—the pillars and values, including transparency, inspection, adaptation, and the five values (commitment, focus, openness, respect, courage)—and how events and artifacts enable continuous improvement.

Discover the three pillars of Scrum: transparency, inspection, and adaptation, and how they enable empiricism through a visible Scrum board and continuous improvement.

Explore the five scrum values—commitment, focus, openness, respect, and courage—and see how they guide team collaboration, support transparency, and help tackle challenges in scrum practice.

Explore the endless feedback loop of scrum: transparency leads to inspection, inspection prompts adaptation, and adaptation returns to transparency for continuous improvement and deliver value.

Explore how frequent, diligent inspection detects variances and problems early, guiding adaptation across sprint planning, daily scrum, sprint review, sprint retrospective, and the sprint itself.

Explore how transparency in Scrum makes work visible to the team and stakeholders, using the product backlog, sprint backlog, and increment to inform decisions.

Adaptation in Scrum emphasizes timely, ongoing adjustments by self-managing teams, guided by inspection during daily scrum, sprint reviews, and retrospectives to deliver value across complex, unpredictable environments.

Explore the composition and responsibilities of cross-functional, self-managing scrum teams. Learn ideal team sizes, how multiple teams coordinate on a product, and common misconceptions.

The scrum team comprises one scrum master, one product owner, and developers who collectively create the product increment. There are no subteams or project managers, and developers are cross-functional.

Learn why scrum teams have no subteams or hierarchies, becoming a cohesive, cross-functional unit where all developers share responsibility for quality and adapt with flexibility toward the product goal.

Master cross-functional, self-managing Scrum teams that possess all the skills needed to create a valuable sprint increment, decide work internally, and deliver autonomous, flexible results.

Explains why scrum teams are limited to ten or fewer, highlighting direct communication, agility, productivity, and accountability within a cross-functional group, and recommends two smaller teams over one large team.

Explore whether developers can also be scrum masters, focusing on role clarity, time management, and potential conflicts of interest in scrum teams.

Coordinate multiple scrum teams on a single product by sharing one product goal, backlog, and owner, while each team maintains its own sprint backlog.

Demonstrate the scrum team's end-to-end responsibilities, from ideation to delivery and maintenance, including stakeholder collaboration, testing, quality assurance, and ongoing improvement.

Master end-to-end feature development in Scrum by empowering a cross-functional team to own design, development, testing, deployment, and documentation from conception to delivery, fostering ownership and accountability.

Explore sustainable, self-managed Scrum teams empowered by the organization to self-organize, maintain a sustainable pace, and deliver consistent value through two-week sprints and focused collaboration.

Explore how every sprint must produce a valuable and usable increment, with whole team accountability, to move the product toward the goal and deliver stakeholder value.

Clarify the three scrum accountabilities: developers, product owner, and scrum master, emphasizing accountability over fixed roles; product owner maximizes value, developers create increments, and scrum master coaches the team.

Balance precise terminology with accessibility in scrum by using accountabilities, not roles, while preserving empiricism, continuous improvement, and delivering value across formal and everyday contexts.

Redefine developers' roles in scrum beyond coding and explore how they own the increment, plan, ensure quality via the definition of done, and adapt daily toward a sprint goal.

In scrum, developers are anyone contributing to a usable increment, not just software engineers, across cross-functional domains to create value every sprint.

Clarifies the distinction in Scrum between accountability and commitment, showing that the entire Scrum team is accountable for the increment while developers commit to its specific features.

Developers in scrum focus on creating value by developing usable increments each sprint, guided by four accountabilities: sprint plan, sprint backlog, definition of done, and daily adaptation.

Developers own the sprint backlog, uphold the definition of done, and adapt daily to achieve the sprint goal, holding each other accountable through professional self-management.

Developers instill quality in scrum by adhering to the definition of done, building quality as a continuous process, and maintaining transparency through shared standards and collaboration.

Master daily adaptation in scrum by inspecting progress and adapting the sprint backlog as a living document. Balance flexibility with commitment to the sprint goal through the daily scrum.

Foster interpersonal accountability and self-management in Scrum by empowering developers to hold each other accountable for the team's work, with the Scrum Master as a coach and the daily scrum.

Explore unwritten scrum rules shaping developers' roles, including adding new developers anytime, onboarding impact on velocity, and sustaining a sustainable pace for long-term productivity.

Explore the product owner's role in maximizing value, managing the product backlog, and upholding accountability, while balancing stakeholder demands within a single product owner framework.

learn how product owners maximize value by deep product knowledge, effective backlog management, stakeholder collaboration, data-driven decisions, and a clear vision, supported by empowerment and trust.

Develop and communicate the product goal, create clear backlog items, and order them to maximize value. Maintain transparency through regular refinement so stakeholders understand the product direction.

Explore the product owner's accountabilities to maximize value through backlog management, clear product goals, stakeholder balance, and decision making, with practical examples in a mobile banking app.

Delegate tasks like user stories, market research, and stakeholder feedback within the backlog, but the product owner remains accountable; prioritization and setting goals cannot be delegated.

Master how trust empowers the product owner to make rapid, clear decisions, align the organization, and deliver value through transparent prioritization and collaboration.

The single product owner ensures clear accountability, efficient decision making, and a coherent vision in Scrum. They represent stakeholders and manage the backlog, but remain accountable even when delegating.

Explore how stakeholders and the organization monitor the product owner's decisions through the product backlog and the inspectable increment at the sprint review, fostering transparency.

Learn how trust and transparency animate the Scrum product backlog, making product owner decisions visible to the team and stakeholders, and how this visibility builds two-way trust.

Inspect the increment in scrum to detect variances, build trust, and enable stakeholder feedback during the sprint review, where a tangible, usable working increment demonstrates progress toward the product goal.

Master how the product owner negotiates features with stakeholders to maximize product value and balance competing priorities. Practice transparent decision making as backlog items reflect these choices.

Explore the Scrum Master as a servant leader who coaches, enables, and removes barriers, not a boss, guiding the team and stakeholders through empowered, time-boxed Scrum events.

Debunk common myths about the Scrum Master role and explain how true Scrum Masters coach teams, facilitate events, remove impediments, and enable self-organizing, high-performing teams across the organization.

Learn how Scrum Masters serve their teams by coaching self-management and cross-functionality, focusing on high-value increments and the definition of done, removing impediments, and ensuring productive, time-boxed events.

Explore real-world impediments a Scrum master helps resolve, from product owner availability and unsustainable pace to external micromanagement and unclear goals, using coaching, facilitation, and education within the Scrum framework.

Ensure all scrum events take place, stay timeboxed, and remain positive and productive through proactive facilitation. Coach the team on the sprint review’s purpose and facilitate a focused, timeboxed event.

Learn how the scrum master serves the product owner by defining a clear product goal, managing the backlog, enabling empirical planning, and facilitating stakeholder collaboration.

Encourage open, ongoing communication to remove barriers between stakeholders and scrum teams, with the scrum master facilitating for greater transparency, trust, and faster feedback.

Explore how Scrum masters plan and advise Scrum implementations across the organization, leading training, coaching, and organizational change to enable value-driven, empirical Scrum practices and continuous improvement.

Master the five key scrum events—from the sprint container to sprint planning, daily scrum, sprint review, and sprint retrospective—and discover how regularity, transparency, and empiricism drive agile success.

View the sprint as a container for scrum events, creating a continuous flow where sprint planning, scrums, sprint review, and sprint retrospective occur within the sprint to inspect and adapt.

Explore the heartbeat of scrum through its events, enabling feedback loops, transparency, and scheduled inspection and adaptation for continuous improvement, with time-boxed events from sprint planning to retrospective.

Regularity and consistency in scrum events create a predictable rhythm, improve focus, and reduce ad hoc meetings by maintaining fixed-length sprints, consistent timing, and timeboxed events.

Discover the purpose behind every scrum event and how the right number of meetings, including sprint planning, daily scrum, sprint review, and sprint retrospective, maximizes transparency and eliminates extraneous meetings.

Discover the sprint as the heartbeat of scrum, with fixed-length sprints, maximum sprint length, what happens during them, and how empiricism drives agile decision making.

Master fixed length sprints in Scrum, which are one month or less, to increase predictability, cadence, and focus. Changes to sprint length happen only during sprint retrospectives, not mid-sprint.

Set sprint lengths to one month or less, not calendar months, and maintain consistency for predictability, adaptability, and frequent inspection and adaptation.

A new sprint starts immediately after the previous sprint ends, with the sprint retrospective concluding it, all scrum events happen within a sprint, and there is no sprint zero.

Work toward the sprint goal by completing selected backlog items while maintaining quality. Refine the backlog and clarify scope with the product owner within the sprint.

Keep sprints short to improve predictability, manage risk, and accelerate learning through frequent feedback, stakeholder reviews, and flexibility within a maximum one-month sprint.

Explore why empirical evidence matters more than metrics in scrum. Learn how adaptability, continuous learning, and reality-based decisions arise from inspection and adaptation.

Only the product owner can cancel a sprint if sprint goal becomes obsolete. This protects the team, keeps focus on value, and reinforces the product owner's authority to maximize value.

Discover what the Scrum Guide omits, and learn how sprint start dates, synchronization, and sprint lengths for multiple teams shape self-organized, adaptable Scrum practice.

Explore burn down, burn up, and cumulative flow charts in scrum to gain insights into progress, flow, and bottlenecks, while understanding they support, not replace, empirical scrum practices.