Scrum Essentials & Scrum Master Certification Preparation

Identify the three scrum roles—scrum master, product owner, and developers—and drive value through the sprint cycle: product backlog, sprint backlog, daily scrum, increment, sprint review, and retrospective.

Guide a Scrum Master through a day of the daily scrum, backlog refinement, and sprint planning. Remove impediments, protect the team, handle conflicts, and align stakeholders to sprint goals.

Explore becoming a Scrum Master by embracing the agile mindset and applying Scrum. Certification offers a global credential and marks the start of ongoing practice toward the PSM journey.

Explore the origins of scrum, its empirical theory with the three pillars and five values, and learn to apply these concepts in daily work and behavior for your certifications.

Scrum addresses high uncertainty and complexity by combining incremental and iterative practices with agile principles, enabling frequent deliveries and client feedback to create value.

Compare agile principles with traditional plan-driven methods, emphasizing iterative development, progressive client testing, and ongoing inspection and adaptation within sprints and product backlogs.

Explore how Scrum serves as a lightweight framework that helps individuals, teams, and organizations create value through adaptive solutions for complex problems, guided by Scrum Master, product owner, and developers.

Embrace empiricism and lean thinking to learn by doing, eliminate waste, and measure value; guide Scrum with observed results, rapid delivery, and quality from the start.

Master the iterative and incremental approach in scrum by delivering each sprint as an increment, refining the user interface, validations, discount calculations, and csv exports based on user feedback.

Scrum operates on empiricism and lean thinking with an incremental, iterative approach. A cross-functional team shares skills, learns within, and builds trust through three pillars and five values.

Make transparency, inspection, and adaptation the foundation of scrum by making work visible to stakeholders. Use tools like Jira to share the product backlog and daily scrums to gather feedback.

Inspect progress frequently to verify objectives remain achievable and identify gaps without blame. Maintain transparency in daily scrums and sprint backlog updates to enable inspection and adaptation.

Teams adapt through inspection, implementing changes without formal management approval. Self-managed adaptation and short sprints, aided by transparency, backlog pacing, and test automation, build trust and Scrum effectiveness.

Explore how scrum succeeds through its five values—focus, openness, respect, courage, and commitment—alongside transparency, inspection, and adaptation that build trust with teams and stakeholders.

Focus drives the scrum team to achieve the sprint goal by aligning developers on tasks, the scrum master on transparency, and the product owner on backlog organization for maximum value.

Open the scrum team to feedback from members and outsiders, including newcomers, product owners, and the Scrum Master, enabling progress, adapting inspection procedures, and building trust with diverse ideas.

Respect, the third Scrum value, honors competent, independent team members and values stakeholder feedback. It promotes calm disagreement and mutual respect among developers, product owners, and management to build cohesion.

practice courage as the fourth scrum value by voicing opinions, choosing challenging backlog items, and delegating decisions, helping managers support autonomous teams and tolerate temporary failure.

Drive commitment across the scrum team to achieve the sprint goal and project success; product owner maximizes value, scrum master removes obstacles, and five values underpin three pillars, building confidence.

Explore Scrum origins, theory, and values that shape an adaptive, value-focused approach. Rely on empiricism, lean thinking, and iterative, incremental work grounded in the Agile Manifesto.

Explore the scrum team, its cross-functional and self-managed structure, and the three roles—developers, product owner, and Scrum Master—focused on delivering value through empowered, small teams.

Define scrum team as a unit of product owner, Scrum Master, and developers with no other roles; the owner defines why and what, developers determine how, and the Master coaches.

Discover how a cross-functional, self-managed scrum team stays multidisciplinary, shares skills, and self-organizes without a project manager, delivering value through sprints, sprint planning, and a shared definition of done.

Set team size to a maximum of ten for agility, with a product owner, a scrum master, and eight developers. Apply the two-pizza rule and adjust by sprint feedback.

Scrum teams own verification and testing across unit, integration, functional, security, and performance tests, manage maintenance and bug backlogs, and self-organize to deliver increments each sprint.

Developers in a Scrum team are self-organized, cross-functional, and responsible for transforming product backlog items into valuable increments each sprint, coordinating with the Scrum Master and Product Owner.

The product owner leads backlog prioritization and stakeholder collaboration to maximize product value. They own the product goal, ensure backlog transparency, and guide sprint refinement to meet quality criteria.

The scrum master promotes scrum, acts as a servant leader to coach a self-managing, cross-functional team, removes obstacles, and ensures scrum events occur with product owner and stakeholders.

The scrum team comprises a product owner, a scrum master, and up to eight developers, a multidisciplinary, self-managed unit that delivers at least one valuable increment each sprint.

Explore five scrum events in the sprint container, focus on sprint planning in three phases, and highlight roles, especially the scrum master, guiding inspection, adaptation, and achieving the sprint goal.

Explore how the sprint transforms ideas into value within a one-week to one-month duration, covering sprint planning, daily scrum, reviews, and retrospectives plus backlog refinement and tracking tools.

Master sprint planning by refining the product backlog, defining the sprint goal, and selecting value-driven items with planning poker estimates to form the sprint backlog.

Discover how the daily scrum helps developers review progress toward the sprint goal and adjust the sprint backlog in a 15-minute, self-managing meeting that emphasizes transparency, inspection, and adaptation.

Describe how the sprint review assesses outcomes, demonstrates completed increments, updates the product backlog with stakeholder feedback, and plans future adaptations toward the product goal.

Explore how the sprint retrospective gathers the whole scrum team to review the sprint, identify improvements, and define concrete actions for the next sprint to boost quality and efficiency.

Explore the core scrum events within a sprint - planning, daily scrum, sprint review, and retrospective - emphasizing the sprint goal, the sprint backlog, value delivered, and maximum durations.

Identify three Scrum work artifacts and three commitment artifacts—the product backlog with product goal, the sprint backlog with sprint goal, and the increment with the definition of done.

Maximize value by managing product backlog, sole source of work, ordered by the product owner, evolving through refinement to include functional stories, bug fixes, technical stories, and technical debt repayment.

Define and communicate a single, clear product goal that guides the scrum team toward a long-term objective, adaptable via user feedback and backlog updates.

The sprint backlog defines the sprint goal and plan of action to deliver the increment, created at sprint planning from accepted user stories and bugs, and remains dynamic.

Establish and fix the sprint goal with the sprint backlog at sprint planning; renegotiate scope within the sprint without changing the goal, and communicate value to stakeholders.

Define increment as the sum of completed sprint backlog items and increments toward the goal, with at least one increment created and delivered during sprint, meeting the definition of done.

Facilitate a definition of done across teams, with the scrum master guiding the inclusion of unit tests, code reviews, functional tests, and technical criteria to ensure increments meet release readiness.

Identify scrum artifacts for products and sprints, including product backlog, sprint backlog, and definitions of done. Align wi-fi sessions to ensure items meet sprint goals and form the product increment.

Explore the scrum master role, from prescriptive implementation to ensuring team effectiveness, including interactions with the team, product owner, organization, and the servant leader mindset.

Explore how Scrum Masters vary in practice and how organizational understanding shapes the role. Learn to align the Scrum Master with the framework and focus on team and organizational improvement.

Identify six postures to avoid as a scrum master: secretary, hero, scrum police, leader, scribe, and administrator, and learn to steer teams away from these roles during certification preparation.

Identify how an ineffective scrum master erodes self-management and creates zombie scrum. Recognize symptoms like excessive focus on story points and stalled retrospectives to uphold true leadership and value delivery.

Apply scrum values and principles to a scrum master's effectiveness by upholding transparency, inspection, and adaptation, and evaluate proposals against these pillars and the five values for exam readiness.

Adopt six Scrum Master postures—trainer, obstacle remover, mentor, facilitator, active agent of change, and agile coach—adapting to team needs, guiding practice, and enabling change.

Adopt a three-level focus as a scrum master: optimize the team’s effectiveness; collaborate with other teams and the scrum-master community; and drive organizational value by showcasing outcomes and involving users.

Foster collaboration with stakeholders through proactive outreach, practice patience to facilitate team solutions, and uphold transparency while protecting the team, by asking sharp questions and continuous Scrum learning.

Position the Scrum Master as a servant leader who leads by example, fosters trust, and creates a safe, collaborative environment for developers, product owners, and stakeholders.

Identify and manage five levels of team conflict as a Scrum Master, using facilitation, empathy, and pair programming to keep team collaboration constructive.

Assess whether the Scrum Master should be full-time, noting that forming teams need full-time guidance while mature teams may not, with the role driving Scrum adoption.

Identify effective behaviors for a scrum master, embody a hybrid servant leader role, and avoid common pitfalls across your team and organization as a change agent to enable agile adoption.

Explore how the scrum master boosts team effectiveness through concrete actions, with three scenarios showing guiding the team to define a sprint goal and done for valuable increments.

Identify stakeholders, gather regular feedback, and align with a shared sprint goal. Foster autonomy, transparency, collaboration, and continuous improvement through scrum artifacts and visible increments.

Explore Scrum Master actions that boost team performance through trust, clear objectives, and autonomy, using workshops, scrum artifacts, self-management rules, backlog refinement, and visual boards.

Facilitate cross-team collaboration on PBIs by guiding a 15-minute workshop where developers brainstorm, pair up, and present ideas categorized into goals, steps, and success measures.

Facilitate a collaborative sprint goal definition to align the Scrum team and stakeholders. Define the vision, product strategy, roadmap, backlog, and product goal to deliver a potentially shippable increment.

The scrum master guides a three-round case study to refine the definition of done for sprints, aligning a shared understanding through green and red cards.

Scrum teams stay courageous and respectful, celebrate successes, learn from failures, and avoid transparency-reducing tools; the scrum master guides self-management and cross-functionality to deliver high-value increments meeting definition of done.

Learn how the scrum master supports the product owner and enhances the scrum team's efficiency, with a case study to clarify the owner's role and define a clear strategy.

Define the product goal and backlog priorities. Involve stakeholders, say no to misaligned ideas, and deliver value by focusing on why, not how, as order givers.

Explore how the Scrum master helps the product owner understand their role through a workshop that clarifies responsibilities across development, product owner, Scrum master, and management to maximize enterprise agility.

Identify six ineffective product owner postures: secretary, writer, director, project manager, expert, and gatekeeper, and show impact on backlog value and product delivery, highlighting Scrum Guide responsibilities.

Guide the scrum master to facilitate the product owner in defining a concise product goal using a nine-box storytelling approach (303 framework) to connect problem, observations, story, solution, and benefits.

Shorten feedback loops with stakeholders. Engage them, focus on why and what, leave how to the team, deliver, say no when needed, remove obstacles with product owner, create business value.

Explore how the Scrum master guides the organization in adopting Scrum, offers implementation guidance, and promotes an empirical approach while removing obstacles between stakeholders and teams and communicating metrics.

Discover how scrum reshapes work with self-managing development teams, defined roles, events, and artifacts that deliver increments; managers shift to supportive roles while addressing accountability.

Scrum masters use a seven-section empathy map—covering situation, role, context, needs, see, say, do, hear, and think and feel—to better support middle management and identify actions for agile change.

Communicate sprint results with metrics such as story points, bugs, code quality, and coverage; the scrum master and product owner workshop metrics such as cycle time, WIP, satisfaction, ROI, morale.

Promote scrum within your organization as a scrum master by acting as a change agent, collaborating with scrum masters, revealing obstacles, empowering self-management, and inspecting and adapting based on results.

Define the Scrum Master’s strategic role within the organisation as a change agent driving agile transformation; collaborate with a community of Scrum Masters to share challenges and solutions.