Scrum Master Role: Responsibilities, Stances & Career Guide (2026)

The Scrum Master is the most misunderstood role in Scrum. Ask ten people what a Scrum Master does and you will likely hear "runs the stand-up," "updates the Jira board," or "is basically a project manager with a different title." None of those answers is correct.

Per the Scrum Guide 2020 (opens in a new tab), the Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, and for the Scrum Team's effectiveness. They do this by helping everyone - the team, the Product Owner, and the wider organization - understand Scrum theory and practice, both within the Scrum Team and the organization.

This guide covers what the Scrum Master role actually is according to the current Scrum Guide, the accountabilities that define it, the 8 stances effective Scrum Masters adopt, a realistic day in the life, how the role compares to a Project Manager and an Agile Coach, the most common misconceptions and mistakes, an industry-by-industry look at the job, a maturity model for growing in the role, and the certification path from entry-level to expert.

Quick Answer: What Is a Scrum Master?

Aspect	Description
Definition	A true leader who serves the Scrum Team and the larger organization, accountable for establishing Scrum
Accountable to	The Scrum Team, the Product Owner, and the organization (three distinct sets of services per the Scrum Guide)
Is not	A project manager, team lead, admin, or the boss of the Scrum Team
Core method	Servant leadership - removing impediments, facilitating events, and coaching self-management
Authority over the team	None - the Scrum Master has no command authority; the Development Team/Developers are self-managing
Primary certifications	Professional Scrum Master (PSM I/II/III) from Scrum.org, Certified ScrumMaster (CSM) from Scrum Alliance
Typical career path	Developer/Team Lead/QA -> Scrum Master -> Senior Scrum Master/Agile Coach -> Release Train Engineer/Head of Agile

What Is a Scrum Master?

The Scrum Guide describes the Scrum Master as "accountable for the Scrum Team's effectiveness" and as "a true leader who serves the Scrum Team and the larger organization." That single sentence carries more weight than most job descriptions ever capture.

Three ideas sit inside it:

• Accountable for effectiveness, not for output. The Scrum Master does not own the product, the backlog, or the code. They own whether the team can work effectively - whether Scrum's events, artifacts, and roles are actually functioning as intended.
• A true leader. Leadership here does not come from a title or command authority. It comes from expertise in Scrum, influence, and the trust the Scrum Master builds by consistently helping the team succeed.
• Who serves. The direction of service flows outward in three directions: to the Scrum Team, to the Product Owner specifically, and to the organization as a whole. This three-way service model is what most job postings - and most people new to Scrum - miss entirely.

Scrum Master Accountabilities per the Scrum Guide

The 2020 Scrum Guide replaced a long list of prescriptive duties with a shorter, clearer statement of accountability, organized around who the Scrum Master serves.

Accountability to the Scrum Team

The Scrum Master serves the Scrum Team in several ways:

• Coaching team members in self-management and cross-functionality
• Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done
• Causing the removal of impediments to the Scrum Team's progress
• Ensuring all Scrum events take place, are positive, productive, and kept within the timebox
• Helping the Scrum Team understand the need for clear and concise Product Backlog items

Accountability to the Product Owner

The Scrum Master serves the Product Owner in several ways:

• Helping find techniques for effective Product Goal definition and Product Backlog management
• Helping the Scrum Team understand the need for clear and concise Product Backlog items
• Helping establish empirical product planning for a complex environment
• Facilitating stakeholder collaboration as requested or needed - see stakeholder management strategies for how this plays out in practice

Accountability to the Organization

The Scrum Master serves the organization in several ways:

• Leading, training, and coaching the organization in its Scrum adoption
• Planning and advising Scrum implementations within the organization
• Helping employees and stakeholders understand and enact an empirical approach for complex work
• Removing barriers between stakeholders and Scrum Teams, including at the organizational level

The 8 Stances of a Scrum Master

According to Scrum.org's research, effective Scrum Masters adopt eight distinct stances depending on the situation. This multi-faceted approach allows them to address diverse challenges and team needs without ever slipping into command-and-control leadership.

1. Servant Leader

The Scrum Master prioritizes the team's needs above their own. They ask "How can I help?" rather than "What should you do?"

When to use: Always as a foundation, especially when team members need support or empowerment.

Example: A developer is blocked waiting for infrastructure access. The SM immediately contacts IT to expedite the request, removing the blocker.

2. Facilitator

The Scrum Master enables group processes without dominating them. They guide discussions, ensure everyone participates, and help the team reach consensus.

When to use: During Scrum events like Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospectives.

Example: In a heated debate about technical approach, the SM facilitates a discussion using timeboxing and voting to help the team decide.

3. Coach

The Scrum Master guides individual development through questions, observations, and feedback. They help people discover solutions rather than providing answers.

When to use: When team members face growth opportunities or need skill development.

Example: A new developer struggles with test-driven development. The SM pairs them with an experienced team member and asks reflective questions about their progress. See coaching and facilitation techniques for a deeper look at this stance.

4. Manager

The Scrum Master manages the Scrum process and logistics, including event scheduling, board administration, and ensuring the Definition of Done is met.

When to use: When organizational coordination and process management are needed.

Example: The SM maintains the team's Scrum board, ensures Sprint burndown is updated, and schedules all Scrum ceremonies.

5. Mentor

The Scrum Master shares wisdom from experience, offering guidance based on patterns they have seen before.

When to use: When the team faces situations the SM has navigated previously.

Example: A team struggles with technical debt. The SM shares how a previous team successfully dedicated 20% of each Sprint to debt reduction.

6. Teacher

The Scrum Master educates on Scrum principles and practices, explaining the "why" behind Scrum framework elements.

When to use: When the team or organization needs to understand Scrum theory and practices.

Example: The SM conducts a workshop on the empirical pillars of Scrum (transparency, inspection, adaptation) and how they apply to the team's work.

7. Impediment Remover

The Scrum Master actively eliminates obstacles that block team progress, escalating when necessary.

When to use: Whenever impediments arise that the team cannot resolve themselves.

Example: The team needs access to a production database for debugging. The SM negotiates with security and compliance teams to create a safe access path.

8. Change Agent

The Scrum Master drives organizational transformation, advocating for Agile principles and challenging existing structures that impede agility.

When to use: When systemic organizational issues limit team effectiveness.

Example: The SM presents data to leadership showing how annual budgeting cycles conflict with iterative delivery, proposing quarterly funding reviews instead.

Core Scrum Master Responsibilities

Day to day, the accountabilities above translate into a recognizable set of activities:

1. Facilitating Scrum events: Organizing and facilitating Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective so they are productive and meet their objectives.
2. Coaching the Scrum Team: Helping the team understand and apply Scrum, Agile principles, and best practices, fostering continuous learning.
3. Removing impediments: Actively identifying and eliminating obstacles that hinder progress, escalating what the team cannot resolve itself.
4. Protecting the Scrum Team: Shielding the team from external disruptions and unplanned work so it can focus on the Sprint Goal.
5. Promoting communication and collaboration: Fostering open communication within the team and with stakeholders, resolving friction through conflict resolution techniques when it surfaces.
6. Supporting the Product Owner: Providing guidance on Product Backlog management, refinement, and prioritization techniques.
7. Growing self-management: Actively promoting self-organization so the team increasingly resolves its own problems without SM intervention.
8. Driving organizational change: Working with leadership to remove structural barriers - budgeting cycles, approval chains, org-chart silos - that limit the team's agility.

A Day in the Life of a Scrum Master

No two days look identical, but most experienced Scrum Masters recognize this rhythm:

Time block	Typical activity
Morning check-in	Scan Slack/Teams, email, and the Scrum board for anything blocking the team before the Daily Scrum
Daily Scrum	Facilitate (or observe, for a mature team) the 15-minute event; note any impediments raised
Impediment follow-up	Work blockers raised in the Daily Scrum - contacting IT, other teams, or management as needed
1:1 coaching conversations	Informal check-ins with individual team members on growth, friction, or morale
Stakeholder and Product Owner support	Help the Product Owner prepare for refinement or an upcoming Sprint Review
Event facilitation (as scheduled)	Sprint Planning, refinement, Sprint Review, or Sprint Retrospective depending on the day in the Sprint
Organizational work	Meetings with other Scrum Masters, a Scrum of Scrums, or a coaching session with a manager
Deliberate white space	Unscheduled time reserved for whatever the team needs that day - this is intentional, not wasted time

Scrum Master vs Project Manager vs Agile Coach

These three roles get confused constantly, partly because a single person sometimes holds more than one at a time in smaller organizations. Understanding the distinct focus of each prevents both title confusion and, more importantly, role confusion inside a team.

Aspect	Scrum Master	Project Manager	Agile Coach
Scope	One or a small number of Scrum Teams	One project, often cross-functional	Multiple teams or an entire organization
Authority	None - no command authority over the team	Significant - assigns tasks, owns budget/schedule	Advisory - influences without direct authority
Success measure	Team effectiveness and Scrum adoption quality	On-time, on-budget, in-scope delivery	Organizational agility and mindset shift
Primary method	Servant leadership, coaching, facilitation	Planning, risk management, coordination	Systemic coaching, training, organizational design
Approach	Empirical - inspect and adapt	Predictive - detailed upfront planning	Empirical, applied at scale
Typical horizon	Sprint by Sprint, continuous	Project start to project close	Multi-team, multi-quarter transformations
Reports on	Team health, impediments removed, Scrum maturity	Schedule, budget, scope variance	Adoption metrics, culture indicators, coaching outcomes

An Agile Coach typically sits a level above individual Scrum Masters, working across several teams or an entire department. Where a Scrum Master serves one or two Scrum Teams directly, an Agile Coach often mentors Scrum Masters themselves, designs organization-wide Agile practices, and works with leadership on structural change. Many Scrum Masters treat Agile Coach as the natural next step in their career path.

Common Misconceptions About the Scrum Master Role

Even experienced organizations get the Scrum Master role wrong in predictable ways. Recognizing these misconceptions is often the fastest way to fix a struggling Scrum implementation.

• "The Scrum Master is the team's boss." Wrong - the Scrum Master has zero command authority. The Developers are self-managing and decide how to do their own work.
• "The Scrum Master is a meeting secretary." Facilitating events is one visible activity among many, not the job's substance. A Scrum Master who only schedules meetings and takes notes is not fulfilling the accountabilities in the Scrum Guide.
• "The Scrum Master updates the board so the team doesn't have to." Board administration should belong to the team wherever possible. An SM who does this indefinitely is training the team into dependency, not self-management.
• "The Scrum Master assigns tasks." Task assignment is exactly what the Scrum Master should never do - Developers select and manage their own work within the Sprint.
• "The Scrum Master reports team performance to management." The Scrum Master protects the team from being individually evaluated on Sprint data; performance reporting in the traditional sense undermines the psychological safety Scrum depends on.
• "Anyone can be a Scrum Master with no training." The role requires real skill in facilitation, coaching, conflict resolution, and organizational influence - it is not an entry-level administrative position, even though it is sometimes staffed as one.
• "A good Scrum Master becomes unnecessary once the team is mature." The stance shifts - less Manager and Impediment Remover, more Change Agent and Mentor - but a high-performing team still benefits from a skilled Scrum Master operating at a higher level.

Industry-Specific Scrum Master Checklists

What a Scrum Master focuses on shifts meaningfully by industry. These checklists highlight the standing concerns worth adding to a Scrum Master's radar in common contexts.

SaaS / Cloud Product Teams

• Track deployment frequency and lead time for changes as team health signals
• Facilitate CI/CD pipeline friction discussions and rollback retrospection
• Coach the team on balancing feature work with platform reliability investment
• Remove impediments around staging/production environment access

Healthcare Software Teams

• Ensure HIPAA and PHI-handling requirements are reflected in the Definition of Done
• Facilitate dual-review practices for code touching patient data
• Coach the team on documenting audit trails without slowing delivery unnecessarily
• Escalate compliance-related organizational impediments (e.g., approval bottlenecks) proactively

Financial Services Teams

• Track PCI-DSS and SOC 2 control adherence as a standing Sprint Review or retrospective topic
• Facilitate conversations between the team and compliance/security stakeholders
• Coach the Product Owner on balancing regulatory backlog items against feature velocity
• Remove impediments tied to lengthy change-approval boards common in regulated finance

E-commerce Teams

• Coach the team on Sprint Goals tied to measurable business outcomes (conversion, cart abandonment)
• Facilitate peak-season readiness planning (e.g., holiday traffic) well ahead of the event
• Remove impediments related to third-party payment gateway dependencies
• Support cross-functional collaboration between engineering, marketing, and customer support

Mobile App Teams

• Coach the team on app store review cycle timing relative to the Sprint cadence
• Facilitate discussions on iOS/Android parity and device fragmentation testing
• Remove impediments around app store rejection cycles or certificate/provisioning issues
• Track accessibility testing on real devices as part of the Definition of Done

Enterprise / DevOps Teams

• Facilitate Scrum of Scrums or cross-team dependency discussions
• Coach the team on infrastructure-as-code practices and security scanning integration
• Remove impediments tied to change-advisory-board approvals and legacy release processes
• Track rollback procedures and incident response readiness

Government and Public Sector Teams

• Ensure accessibility standards (WCAG 2.1 AA, Section 508) are part of the Definition of Done
• Facilitate conversations around procurement cycles and fixed-budget constraints
• Coach stakeholders unfamiliar with Agile on empirical planning versus fixed-scope contracting
• Remove impediments tied to lengthy public-sector approval chains

EdTech Teams

• Ensure FERPA and COPPA requirements are reflected in the Definition of Done
• Facilitate feedback loops between the team and actual teachers/students where possible
• Coach the Product Owner on balancing pedagogy-driven priorities with technical constraints
• Track accessibility testing for the Sprint's UI changes

Scrum Master Maturity Model

Scrum Master capability, like team capability, develops progressively. This model describes typical growth for someone new to the role.

Stage 1: New Scrum Master (Months 1-6)

Timeline: First 6 months in the role, often the first Scrum Master position held

Characteristics:

• Leans heavily on the Manager and Facilitator stances - scheduling events, keeping meetings on track
• Focuses on learning the mechanics of Scrum events and artifacts correctly
• Impediment removal is mostly reactive, addressing what the team explicitly raises

Focus for this stage:

• Master facilitation basics for all four Scrum events
• Study the Scrum Guide closely enough to explain the "why" behind each element, not just the "what"
• Pursue an entry-level certification such as PSM I if not already held

Stage 2: Developing Scrum Master (Months 6-18)

Timeline: Roughly 6 to 18 months into the role

Characteristics:

• Begins adopting the Coach and Mentor stances more deliberately, not just Facilitator and Manager
• Recognizes recurring impediments and starts addressing root causes rather than symptoms
• Builds real coaching and conflict resolution skills through practice

Focus for this stage:

• Practice powerful questioning instead of giving direct answers when coaching
• Start tracking impediment patterns across Sprints to spot systemic issues
• Begin engaging with stakeholder management proactively rather than only when asked

Stage 3: Experienced Scrum Master (Years 2-4)

Timeline: Roughly 2 to 4 years in the role

Characteristics:

• Comfortably shifts between all 8 stances based on context, including Teacher and Change Agent
• Actively promotes self-organization, deliberately stepping back from logistics the team can own
• Takes on organizational-level impediments, working directly with management on structural change

Focus for this stage:

• Pursue PSM II or equivalent advanced certification
• Mentor newer Scrum Masters within the organization
• Begin contributing to organizational Agile practices beyond a single team

Stage 4: Expert Scrum Master / Agile Coach (Year 4+)

Timeline: 4+ years, often transitioning toward an Agile Coach or Release Train Engineer title

Characteristics:

• Operates across multiple teams, coaching other Scrum Masters rather than facilitating single-team events
• Primarily uses the Change Agent stance, driving structural and cultural transformation
• Shapes organization-wide Agile practices, training programs, and Scrum Master communities of practice

Focus for this stage:

• Pursue PSM III or a recognized Agile Coach certification
• Lead or contribute to enterprise-level Agile transformation initiatives
• Measure and report on organizational agility, not just individual team health

Common Scrum Master Mistakes

Mistake 1: Acting as a Project Manager in Disguise

Problem: The Scrum Master assigns tasks, tracks individual hours, and reports status to management as if running a traditional project.

Why It's Problematic: This undermines the team's self-management and reintroduces command-and-control dynamics Scrum is designed to remove.

Fix: Redirect task selection back to the Developers; report on team-level outcomes, not individual performance.

Prevention: Regularly ask "Am I doing this for the team, or instead of the team?" before stepping in.

Mistake 2: Becoming a Permanent Meeting Scheduler

Problem: The Scrum Master remains solely responsible for scheduling and running every Scrum event indefinitely, even as the team matures.

Why It's Problematic: The team never develops the ownership and facilitation skills needed to self-organize fully.

Fix: Rotate facilitation duties to team members, starting with lower-stakes events like the Daily Scrum.

Prevention: Set an explicit goal each quarter for reducing the SM's logistical footprint as team maturity grows.

Mistake 3: Shielding the Team From All Difficult Conversations

Problem: The Scrum Master absorbs every piece of stakeholder pressure or conflict instead of helping the team develop the skills to handle it.

Why It's Problematic: The team never builds resilience or direct stakeholder relationships, creating a single point of failure.

Fix: Coach team members through difficult conversations rather than always having them instead of the team.

Prevention: Distinguish between protecting the team from disruption and protecting them from all discomfort - only the former is the job.

Mistake 4: Avoiding Organizational-Level Impediments

Problem: The Scrum Master resolves only team-level blockers and avoids escalating systemic issues like budgeting cycles or approval chains.

Why It's Problematic: The team hits the same organizational wall Sprint after Sprint with no path to resolution.

Fix: Document recurring organizational impediments with evidence and escalate them explicitly to leadership.

Prevention: Track impediments by category (team-level vs organizational) and review the organizational list quarterly.

Mistake 5: Using the Same Coaching Approach for Every Team Member

Problem: The Scrum Master applies one fixed coaching style regardless of an individual's experience, personality, or need.

Why It's Problematic: A junior developer needing more direction and a senior developer needing more autonomy get the same treatment, serving neither well.

Fix: Adapt coaching style situationally - more directive for a novice, more Socratic for an expert.

Prevention: Regularly check in on what kind of support each individual actually wants, rather than assuming.

Mistake 6: Neglecting the Product Owner Relationship

Problem: The Scrum Master focuses exclusively on the Developers and treats supporting the Product Owner as optional.

Why It's Problematic: Product Backlog quality, refinement effectiveness, and stakeholder collaboration all suffer, and Scrum's outcomes depend on the whole team, not just the Developers.

Fix: Schedule regular 1:1 time with the Product Owner specifically focused on backlog management techniques and stakeholder friction.

Prevention: Treat all three Scrum Guide accountabilities (team, Product Owner, organization) as equally weighted responsibilities.

Mistake 7: Measuring Success by Velocity Instead of Effectiveness

Problem: The Scrum Master (or their manager) treats Sprint velocity as the primary indicator of Scrum Master performance.

Why It's Problematic: Velocity is an internal planning metric, easily gamed, and says nothing about team health, impediment resolution, or Scrum maturity.

Fix: Track qualitative and structural indicators instead - see the measuring effectiveness section below.

Prevention: Explicitly push back when leadership requests velocity comparisons across teams.

Mistake 8: Letting the Role Stagnate at "Facilitator Only"

Problem: An experienced Scrum Master continues operating exactly as they did in month one, never adopting the Mentor, Teacher, or Change Agent stances.

Why It's Problematic: The team's growth outpaces the Scrum Master's, and organizational-level impediments never get addressed.

Fix: Deliberately practice underused stances - if Manager and Facilitator dominate, schedule time for Teacher and Change Agent activities.

Prevention: Revisit the maturity model above periodically and honestly assess which stage matches current practice.

How to Become a Scrum Master: Career Path and Certifications

Most Scrum Masters arrive at the role from adjacent positions - developer, QA engineer, business analyst, or traditional project/team lead - rather than starting there directly.

Certification Options: PSM vs CSM

Aspect	Professional Scrum Master (PSM)	Certified ScrumMaster (CSM)
Issuing body	Scrum.org (opens in a new tab)	Scrum Alliance
Format	Self-study plus a proctored online exam	Mandatory 2-day instructor-led course, then an exam
Levels	PSM I, PSM II, PSM III (progressively advanced)	CSM, then A-CSM, then CSP-SM
Renewal	No expiration once passed	Requires renewal every 2 years with continuing education
Best for	Self-directed learners who want a rigorous, content-focused test	Learners who want structured, live instruction and a cohort experience

Read the full breakdown in Difference Between PSM and CSM Certifications. For candidates specifically pursuing PSM I, the exam format and structure guide and the official Scrum Guide 2020 summary are the two most important preparation resources.

Other bodies - the Project Management Institute (PMI) with its Disciplined Agile credentials, and the Scaled Agile Framework (SAFe) with SAFe Scrum Master - offer adjacent certifications, particularly relevant once a Scrum Master starts working in scaled or enterprise contexts.

Skills Needed for the Job

• Facilitation - running events that stay on time and produce real outcomes, not just conversation
• Coaching - asking questions that help people find their own answers, rather than directing
• Conflict resolution - navigating disagreement productively without letting it fester or explode
• Organizational influence - persuading people with no formal authority over them
• Deep Scrum knowledge - understanding not just the mechanics but the reasoning behind every framework element
• Emotional intelligence - reading team morale and psychological safety, often before anyone says a word about it

Tips for Transitioning into the Role

• Learn the team and organizational culture first before trying to change anything - context earns credibility.
• Be open to feedback, including from people without formal authority over you; this is a service role, not a command one.
• Ask questions relentlessly - about timelines, blockers, and team dynamics - both to learn and to model the coaching stance itself.
• Start with a single certification (PSM I is the most common entry point) to build a shared vocabulary with other practitioners.

Tools Used by Scrum Masters

Scrum Masters rely on three broad categories of tooling to support the team:

• Agile project management software - Jira (opens in a new tab) and Trello (opens in a new tab) provide sprint boards, backlog management, and reporting. Purpose-built options like this site's Scrum board, sprint planning tool, and retrospective tool support specific Scrum events directly.
• Communication tools - Slack (opens in a new tab) and Zoom (opens in a new tab) keep distributed teams connected for daily coordination and event facilitation.
• Collaboration tools - Google Docs (opens in a new tab) and Microsoft Teams (opens in a new tab) support shared documentation and real-time collaborative editing.

Scaling the Scrum Master Role Across Multiple Teams

As organizations grow, a single Scrum Master rarely stays attached to just one team forever. Several patterns emerge at scale:

• One Scrum Master, multiple teams: Common in smaller organizations or with highly mature teams that need less day-to-day facilitation support. Requires disciplined time management and strong delegation of logistics back to each team.
• Scrum of Scrums: Representatives (often the Scrum Masters themselves) from each team meet regularly to surface and resolve cross-team dependencies and shared impediments.
• Release Train Engineer (RTE): In SAFe-based organizations, the RTE role sits above individual Scrum Masters, facilitating Program Increment planning and cross-team synchronization across an Agile Release Train.
• Scrum Master communities of practice: Groups of Scrum Masters within a single organization share techniques, mentor newer practitioners, and standardize practices without enforcing rigid uniformity across teams.
• Fractional or part-time Scrum Masters: Increasingly common in smaller or resource-constrained organizations, where one person splits Scrum Master duties across two or three teams or combines the role with another function.

Measuring Scrum Master Effectiveness

Scrum Master value is partly intangible, but several concrete signals indicate whether the role is functioning well:

Metric	What it indicates
Impediment resolution time	How quickly blockers raised by the team get resolved or escalated
Team-reported psychological safety	Whether team members feel safe raising real issues in retrospectives and elsewhere
Scrum event quality	Whether events consistently meet their stated purpose within their timebox
Self-management trend	Whether the team increasingly resolves its own logistics and minor conflicts over time
Organizational impediments escalated and resolved	Whether systemic issues get surfaced to leadership and actually addressed
Team retention and engagement	Whether team members report feeling supported, which correlates strongly with SM effectiveness

Conclusion

The Scrum Master role is essential to Agile project management, but its value lies precisely in what it is not: not a project manager, not a team boss, not a meeting secretary. It is a service-oriented accountability - to the Scrum Team, to the Product Owner, and to the organization - carried out through eight fluid stances rather than a fixed job description.

Your next three actions:

1. Audit which of the 8 stances you (or your Scrum Master) use most - if Manager and Facilitator dominate, deliberately practice Teacher and Change Agent this quarter.
2. Compare your current responsibilities against the common misconceptions list above - are you doing anything on that list that should belong to the team instead?
3. If you are pursuing certification, pick a track - PSM or CSM - using the comparison table above, and start studying with a target exam date.

At the heart of every successful Agile team is a skilled Scrum Master who removes what gets in the way, coaches what needs to grow, and steps back the moment the team can handle something on its own.

References

• Scrum Guide 2020 (official PDF) (opens in a new tab)
• What is a Scrum Master? - Scrum.org (opens in a new tab)
• The Difference Between Project Managers and Scrum Masters - Scrum Alliance (opens in a new tab)
• Scrum Master vs Project Manager - Scrum.org (opens in a new tab)

Frequently Asked Questions (FAQs) / People Also Ask (PAA)