A scrum master is not a project manager, though the two roles overlap enough that many people (and many job postings) blur the line between them. A project manager owns the plan, the budget, and the timeline for a project from start to finish. A scrum master owns the process a team uses to deliver work, coaching that team to manage itself rather than directing it from above. The distinction matters for your career path, your day-to-day responsibilities, and the kind of authority you carry.
What a Project Manager Actually Does
A project manager is responsible for getting a defined piece of work completed on time, within budget, and to the required standard. They set milestones, coordinate tasks across people and teams, and track progress against a plan. When risks surface, the project manager addresses them. When scope starts to creep, they push back or negotiate trade-offs with stakeholders.
The leadership style is top-down. Project managers make decisions, delegate tasks, and control the schedule. They typically build a detailed plan at the start and manage against it, adjusting as needed but always aiming to keep the project aligned with the original blueprint. Think of them as the person who answers the question: “Will this project ship on time and on budget?”
What a Scrum Master Actually Does
A scrum master is accountable for how well a scrum team delivers value, not for a specific project plan or budget line. Their job is to establish and facilitate scrum as a working method: running sprint ceremonies, helping the team understand scrum theory, and removing obstacles that slow people down. According to the Scrum Guide, the scrum master helps everyone on the team and across the organization understand scrum practices.
The leadership style is the opposite of command-and-control. Scrum masters lead by serving the team. They advise, coach, and protect the team from external disruptions so developers can focus. They do not assign tasks. Instead, they empower the team to self-manage, meaning the team decides how to break down and complete its own work. A scrum master answers a different question than a project manager: “Is this team working effectively, and what’s getting in their way?”
Key Differences Side by Side
- Planning approach: A project manager builds a detailed upfront plan with milestones and predictions. A scrum master works through short iterative cycles (sprints), adapting plans based on what the team learns along the way.
- Authority over people: A project manager delegates tasks and often has some say in staffing decisions. A scrum master influences through coaching and facilitation, not through assigning work.
- Budget and scope: A project manager typically owns the budget and is held accountable for scope management. A scrum master has no direct budget responsibility. Scope decisions in scrum fall to the product owner.
- Risk management: A project manager identifies and mitigates project risks as a core duty. A scrum master addresses impediments to the team’s workflow, which can include risks but is focused on day-to-day blockers.
- Success metric: For a project manager, success means delivering the agreed scope on time and within budget. For a scrum master, success means the team is continuously improving and delivering valuable work each sprint.
Why Companies Combine the Roles
Despite the clear differences in theory, many organizations post jobs with titles like “Project Manager/Scrum Master” or “Agile Project Manager.” This happens for practical reasons. Smaller companies may not have the headcount to staff both roles separately. Larger companies transitioning from traditional project management to agile methods often need someone who can handle stakeholder reporting and budget tracking while also facilitating scrum for a development team.
An agile project manager blends both functions. They handle high-level planning, stakeholder communication, risk management, and progress monitoring, but they do so with a collaborative, facilitative style rather than strict command-and-control. They guide the team without imposing rigid task assignments on the development process, championing agile practices within the organization while still keeping an eye on schedules and deliverables. This hybrid role is common in industries like financial services and technology consulting, where companies need someone comfortable in both worlds.
According to Glassdoor salary data from 2026, professionals holding a combined project manager/scrum master title earn an average of about $127,000 per year in the U.S., with a typical range between $99,000 and $165,000. Top earners in these hybrid roles can reach $207,000 or more. Companies like Capital One and Wells Fargo list total compensation in the $110,000 to $162,000 range for these positions.
Certifications That Signal Each Path
The credentials you pursue tell employers which side of the divide you lean toward. For project management, the PMP (Project Management Professional) from the Project Management Institute is the most widely recognized certification. It validates your ability to manage scope, schedule, cost, and risk across a range of methodologies.
For scrum masters, the two most common certifications are the CSM (Certified ScrumMaster) from Scrum Alliance and the PSM (Professional Scrum Master) from Scrum.org. Both focus on scrum theory, team facilitation, and empirical process control. The CSM requires a two-day training course, while the PSM is assessment-based and can be taken without attending a class.
If you’re targeting hybrid roles, holding both a PMP and a scrum certification makes you especially marketable. Many agile project manager positions list both as preferred qualifications.
Which Role Fits Your Working Style
If you’re energized by building detailed plans, tracking progress against milestones, managing budgets, and being the single point of accountability for a project’s outcome, project management is the more natural fit. You’ll spend your time coordinating across teams, reporting to executives, and making decisions about resource allocation and trade-offs.
If you’d rather coach a team, facilitate collaboration, and focus on continuous improvement without owning the plan or the budget directly, the scrum master path is a better match. Your day-to-day will center on sprint planning, retrospectives, removing blockers, and helping the team get better at delivering work in short cycles.
Many professionals start in one role and move into the other. A project manager who joins an agile organization often finds their skills transfer well, especially around stakeholder management and risk awareness. A scrum master who wants broader organizational influence may grow into program management or agile coaching, which carry some of the same strategic responsibilities as traditional project management but with an agile framework underneath.