Scrum Master vs project manager: the real difference
By Scrumagic Team Last reviewed 6 min read
In short
A project manager is accountable for delivering a project to plan: scope, schedule, budget and risk. A Scrum Master is accountable for the team using Scrum well, and for removing what holds it back. The first manages the work. The second serves the team that manages itself. They overlap less than their job titles suggest.
When an organisation adopts Scrum, someone usually asks which existing job turns into the Scrum Master. The project manager is the obvious candidate, because both roles seem to be about keeping a team on track. That assumption is the source of most of the trouble that follows.
Two accountabilities, side by side
The Association for Project Management defines project management as "the application of processes, methods, skills, knowledge and experience to achieve specific project objectives according to acceptance criteria within agreed parameters." On its description of the role, a project manager is accountable for things like capturing requirements, estimating resources, preparing business cases, developing management plans, managing risks, issues and changes, monitoring progress against the plan, managing budgets, and keeping stakeholders informed. They also lead and motivate the delivery team.
The Scrum Guide describes the Scrum Master as accountable for establishing Scrum as defined in the Guide, and for the team's effectiveness. It then lists what that means for three audiences:
- For the Scrum Team: coaching members in self-management and cross-functionality, helping them focus on creating high-value Increments that meet the Definition of Done, removing impediments to progress, and making sure all Scrum events take place and are positive, productive and kept within the timebox.
- For the Product Owner: helping find techniques for defining the Product Goal and managing the backlog, helping the team understand the need for clear and concise items, establishing empirical planning in a complex environment, and facilitating stakeholder collaboration as requested.
- For the organisation: leading, training and coaching in Scrum adoption, planning and advising implementations, helping people understand empirical approaches to complex work, and removing barriers between stakeholders and Scrum Teams.
Read them next to each other and the difference is plain. The project manager's list is about the project: its plan, its money, its risks. The Scrum Master's list is about the team and the system around it: how well it works, and what stops it working.
A comparison
| Project manager | Scrum Master | |
|---|---|---|
| Accountable for | Delivering the project to scope, schedule and budget | The team using Scrum well, and its effectiveness |
| Plan | Writes it, then manages progress against it | Doesn't own one: the Developers plan each Sprint, and the Product Owner orders the backlog |
| Decides what is built | Often, through scope control | Never: that is the Product Owner's accountability |
| Decides how it is built | Often assigns the work | Never: the Developers decide, as a self-managing team |
| Authority over the team | Usually line or delegated authority | None by right. The role works by coaching and by removing obstacles |
| Success looks like | On time, on budget, to scope | A team that delivers valuable Increments and improves |
The row to look at is the third. In Scrum the three decisions a project manager typically holds, what, how and who, are spread: the Product Owner decides what, the Developers decide how, and the team organises itself. A Scrum Master who takes any of them back has stopped being one.
Where they genuinely overlap
They do share ground, and pretending otherwise isn't helpful.
- Both care about risk and impediments, and both need to see problems early.
- Both communicate with stakeholders, though the Scrum Master does it to help the Product Owner and the team do it well, rather than to be the channel.
- Both need facilitation and influence skills, since neither can simply order people about.
A good project manager brings real strengths to a Scrum Master role: an eye for dependencies, comfort with stakeholders, a habit of asking what could go wrong. The adjustment is in giving up control of the plan.
Example: One delay, two responses
Suppose a team realises on day four of a Sprint that an integration with a payment provider will take longer than they thought. A project manager would likely update the plan, assess the effect on the release date, and report the change upwards. A Scrum Master would make sure the Developers and the Product Owner both know, help them look at the Sprint Goal and ask what could change to protect it, and take the cause of the delay, such as slow access to the provider's sandbox, to whoever can fix it. Both responses are reasonable. The difference is who owns the decision and where the energy goes. The example is invented.
What goes wrong when one becomes the other
The Scrum Master as task allocator. Assigning work, chasing status and reporting progress make the team dependent on one person, and a self-managing team becomes a managed one with Scrum vocabulary.
The Scrum Master as secretary. At the other end, a Scrum Master who only books rooms and writes up notes is missing most of the role. The Guide's list is about coaching and about change, not clerical support.
The Scrum Master as police. Enforcing the rules of Scrum without helping people see why they exist produces compliance and resentment. The Guide describes the role as true leadership that serves the team and the organisation.
The project manager who stays beside the Scrum Master. Some organisations keep both. That can work if the project manager handles budget, contracts and cross-team dependencies that the Scrum Team doesn't. It stops working if the project manager keeps the right to re-plan the Sprint.
Can one person do both?
It's possible in the sense that nobody will stop you, but it is a bad bet. The two roles pull in different directions at the moments that matter. Asked to protect a delivery date, a project manager will want to cut scope or add pressure. A Scrum Master's job in the same moment is to protect the team's ability to inspect and adapt. One person can't do both in the same conversation.
Two perspectives
The Scrum Guide and SBOK agree here.
Scrum Guide
The Scrum Guide makes the Scrum Master accountable for establishing Scrum and for the Scrum Team's effectiveness, as a true leader who serves the team and the organisation. It has no project manager role.
SBOK®
The SBOK® Guide describes the Scrum Master as a facilitator and servant leader who helps the team follow Scrum, removes impediments and shields the team, and it does not make a project manager part of the Scrum core team.
Same thing, different words
- Scrum Master (Scrum Guide) = Scrum Master (SBOK)
Both sources agree that the Scrum Master is not a project manager. Neither says what an organisation should do with the project managers it already has.
If you are moving from one to the other
Many Scrum Masters began as project managers, and the move is easier if you know which habits to keep and which to let go. Keep the eye for risk, the comfort with stakeholders and the discipline of following things up. Let go of owning the plan, of deciding who does what, and of being the person every question goes through. A useful sign that the transition is working is that the team stops waiting for you: it holds its own events, raises its own blockers, and makes decisions without checking.
It takes longer than a job title change. The first months often feel like doing less, because the visible work of managing a plan has gone and the work of coaching a team is slower to show. That feeling is normal, and it is worth asking the team, now and then, what would make it easier for them to work without you.
Where to practise
The distinction is easy to state and hard to feel until you're in a situation where the old reflex, taking over, is the quick fix.
Sources
- The 2020 Scrum Guide, Scrum Guides. Read on 8 October 2026.
- What is project management?, Association for Project Management. Read on 8 October 2026.
SBOK® is a registered trademark of its owner. Scrumagic is independent and is not affiliated with the owners of SBOK®.
Nothing opened? This computer may have no email program set up. Write it in Gmail or use the copy button and paste the link into your email.