Scrum master vs project manager — what is the difference?

A Scrum Master facilitates the Scrum process within a team and coaches them on Agile practices. A Project Manager oversees the broader project scope, including planning, execution, budgets, and resource allocation. The two roles have different accountability, authority, and working environments.

Here's the practical difference: a Scrum Master removes blockers and protects the team's sprint. A Project Manager manages stakeholder expectations, timelines, and whether the project stays on budget.

Key Responsibilities

Scrum Master:

• Facilitates Scrum events (standups, planning, retros, reviews)
• Removes impediments blocking the team
• Coaches the team on Scrum principles and practices
• Acts as a servant leader, not a directive manager

Project Manager:

• Develops project plans and schedules
• Manages budgets and resource allocation
• Coordinates between multiple teams and departments
• Reports progress to senior leadership and stakeholders

Accountability and Authority

Scrum Masters are accountable for the Scrum process and team dynamics. They don't have hiring or firing authority. They succeed when the team improves its velocity, reduces impediments, and delivers working software each sprint.

Project Managers are responsible for delivering the project on time and within budget. They often have more direct authority over resources and timelines. They answer to sponsors and executives about overall project health.

This distinction matters because it shapes how each role interacts with teams and stakeholders. A Scrum Master who acts like a project manager (assigning tasks, tracking individual hours) breaks the self-organizing team model. A project manager who ignores Scrum ceremonies misses early warning signs of scope creep or team friction.

Working Environments

Scrum Masters thrive in Agile environments where iterative development, frequent feedback, and team autonomy are the norm. You'll find them in software development, product teams, and increasingly in marketing and operations.

Project Managers operate in both Agile and traditional (waterfall) environments. They adapt their approach based on project methodology. In a waterfall project, they're managing a fixed scope and sequential phases. In Agile, they're managing evolving scope and stakeholder alignment across sprints.

Many organizations now hire both roles. The Scrum Master owns the team's process. The Project Manager owns the business outcome and stakeholder communication.

If you're considering either path, start with understanding Scrum fundamentals. Our CSM certification covers the Scrum Master role in depth and costs $349 to get started. We've trained over 55,000 practitioners since 2001, and most teams benefit from having at least one certified Scrum Master who understands the role's boundaries.

The confusion between these roles often surfaces when a company tries to hire one person to do both jobs. That rarely works. Each role requires different mindsets and skills.