What the Scrum Guide actually says about the Scrum Master
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. This is a coaching and teaching accountability, not a command-and-control one. The Scrum Master serves the Scrum Team, the Product Owner, and the organization in distinct ways described directly in the Guide.
Notably, the Scrum Guide gives the Scrum Master no authority over what the team builds or how much it commits to; those decisions sit with the Product Owner and the Developers respectively. The Scrum Master's leverage is removing impediments, facilitating events, and coaching the organization toward empirical practices.
What a traditional Project Manager typically does
A Project Manager in classic project management is generally accountable for scope, schedule, budget, and resource allocation, often reporting status upward and assigning work downward. That role assumes a predictive, plan-driven approach where a detailed plan is made up front and then tracked against actuals.
Scrum's empirical process control, inspecting and adapting frequently based on real outcomes, does not have a natural home for that kind of centralized planning and reporting authority, which is exactly why simply renaming Project Managers to Scrum Masters without changing their behavior tends to produce a Scrum Master who still assigns tasks and tracks status like a Project Manager, undermining the Developers' self-management.
Where the confusion causes real damage
When a former Project Manager becomes a Scrum Master but keeps assigning work, the Developers stop practicing the planning and estimation skills Scrum expects them to own, and the team's forecast becomes something imposed rather than something forecast. When a Scrum Master starts managing budgets and staffing decisions instead of coaching the team, they lose the neutrality needed to facilitate a hard Sprint Retrospective conversation.
Organizations that need both project coordination across multiple teams and Scrum Team-level coaching sometimes split these into two separate people or accountabilities, rather than compressing both into one role and hoping nothing gets shortchanged.
- Scrum Master coaches and removes impediments; does not assign tasks
- Project Manager traditionally owns scope, schedule and budget centrally
- Developers, not the Scrum Master, own the how and the forecast
- Blending both roles without changing behavior tends to recreate command-and-control
How to tell which job someone is actually doing
Look at who decides what the team commits to each Sprint. If it is the person with the Scrum Master title, that is Project Manager behavior wearing a Scrum Master title, regardless of what the org chart says. Look at whether that person is protecting the team's focus and coaching self-management, or reporting status upward and pushing deadlines downward; the former is Scrum Master work as described in the Scrum Guide, the latter is not.
How it connects to the rest of Scrum
The Scrum Master's accountability touches every event: ensuring Sprint Planning, the Daily Scrum, Sprint Review and Sprint Retrospective happen, stay timeboxed, and stay useful. None of that requires the authority a Project Manager traditionally holds, which is precisely the point: Scrum distributes planning and delivery authority to the Developers and value decisions to the Product Owner, leaving the Scrum Master to serve rather than direct.
Frequently asked questions
Can a Project Manager become a Scrum Master?
Yes, many do, but it requires a real shift in behavior, from assigning and tracking tasks to coaching, facilitating and removing impediments. Keeping Project Manager habits while holding the Scrum Master title tends to undermine the Developers' self-management.
Does the Scrum Guide mention Project Managers at all?
No. The 2020 Scrum Guide does not define a Project Manager role or map one onto any Scrum accountability. The Scrum Master, Product Owner and Developers are the only accountabilities it defines within the Scrum Team.
Who owns the schedule in Scrum if not a Project Manager?
There is no single schedule owner in the traditional sense. The Sprint length sets a fixed cadence, the Developers forecast what fits in each Sprint, and the Product Owner orders the Product Backlog by value, so scheduling emerges from these decisions rather than being centrally managed.
Is a Scrum Master a management position?
Not in the traditional sense of having authority over people or budgets. It is a servant-leadership accountability focused on the effectiveness of the Scrum Team and the organization's understanding of Scrum, rather than line management of the Developers.