A project manager owns the plan: scope, dates, budget and risks. A Scrum Master owns how the team works: the Scrum events, the obstacles and the habits that make delivery predictable. Neither one decides what the product should do. That job belongs to the Product Owner, who in a startup is usually the founder.
So the question “project manager or Scrum Master?” is really about your project. If the scope and the deadline are fixed from outside, you need someone who owns the plan. If the scope will change as you learn from users, you need someone who keeps a short feedback loop working. Some projects need both, and very small ones need neither as a full-time role.
The Project Management Institute published the PMBOK Guide, Eighth Edition in November 2025. It is the current reference for the role, and it is meant for “a range of approaches”, from traditional plans to agile teams. It rests on six principles: a holistic view, value, quality, accountable leadership, sustainability and empowered teams. And it groups the work into seven performance domains: governance, scope, schedule, finance, stakeholders, resources and risk. The edition also adds guidance on AI, project management offices and procurement.
Those seven domains are a good description of the job. A project manager:
The project manager has authority over the plan and often over people’s time. That makes the role strong when the plan is the thing that must not move.
The Scrum Guide never mentions a project manager. It defines three accountabilities: the Product Owner, the Scrum Master and the Developers. The Scrum Master “is accountable for establishing Scrum as defined in the Scrum Guide” and serves three groups:
The Guide calls Scrum Masters “true leaders who serve the Scrum Team and the larger organization.” They don’t assign tasks. The Developers create the Sprint plan, and “within a Scrum Team, there are no sub-teams or hierarchies.”
| Project manager | Scrum Master | |
|---|---|---|
| Main question | Will we deliver this scope by this date for this money? | Is the team working in a way that shows problems early? |
| Owns | Plan, schedule, budget, risks, vendors, reporting | Scrum events, team habits, removing impediments |
| Authority | Over the plan, often over who works on what | None over people; leads by coaching |
| Success looks like | Delivered on time and on budget | Working software every Sprint, fewer surprises |
| Reference | PMBOK Guide, Eighth Edition (2025) | Scrum Guide (2020) |
| Typical contract | Fixed price, fixed scope | Time and materials or a dedicated team |
| Fails when | The plan matters more than user feedback | Nobody owns priorities, or the role becomes a meeting scheduler |
Match the role to the situation, not to a methodology you read about.
| Your situation | Who you need |
|---|---|
| Fixed scope and an outside deadline (a regulator, a contract, an event) | A project manager |
| Several vendors, hardware or a long chain of integrations | A project manager |
| A product whose backlog will change for months | A Scrum Master and a strong Product Owner |
| A first version in 2-4 weeks with a small team | Neither full-time; the team lead runs the process and you own priorities |
| Several Scrum teams on one product, plus a budget board | Both: Scrum Masters for the teams, a project or programme manager for the plan |
| A team that “does Scrum” but keeps missing Sprint Goals | A Scrum Master first, then look at the backlog |
Yes, small companies do combine them. The combination carries a built-in conflict: the project manager pushes for the date, while the Scrum Master protects the team’s way of working, sometimes from that same push. When one person holds both, watch for the date winning every argument and the Retrospective being the first event to go. If you combine the roles, write down which events can never be skipped. Combining the Scrum Master and the Product Owner is riskier still, because nobody is left to challenge the priorities; it is on our list of common ScrumButs.
Both roles exist to remove friction that developers can’t remove themselves. In the Stack Overflow Developer Survey 2026, 18,214 developers named the factor that did the most to make their job harder in the past six months. Unclear priorities or requirements came first at 16.6%, inefficient processes, workflows or coordination second at 14.6%, and not enough time, staffing or resources third at 14.1%. Leadership activity or organizational changes followed at 11.9%.
Roughly, the first answer is the Product Owner’s to fix, the second the Scrum Master’s and the third the project manager’s. Atlassian’s 2025 developer experience report adds a warning for whoever owns the process: 63% of the 3,500 developers and managers surveyed said their leaders don’t understand their pain points, up from 44% a year earlier. A Scrum Master or project manager who doesn’t surface those problems is adding a layer, not removing one.
In our dedicated teams the usual set of roles is a Product Owner on your side, a business analyst, the developers and a Scrum Master. A developer costs $6,000-9,000 a month. If you need a designer, a QA engineer or a project manager, we add them to the estimate. The team starts in 3-5 days, or within 2 weeks if we hire someone new.
On Guestroom the team included a business analyst and a Scrum Master, and at one point we added Lead Backend and Lead Frontend roles to reduce delivery risk. When a frontend developer had to be replaced mid-project, the change took 1.5 weeks and didn’t hurt the schedule. That is the kind of event a process owner exists for. For how the Scrum Master runs communication with the client, see our guide to project team communication in Scrum. For the role neither of them replaces, see the Product Owner’s responsibilities.
A project manager needs a budget and a timeline before the first day. A Scrum team plans one Sprint at a time. You can have both if the first numbers come from the scope itself.
Our project estimate turns your brief into user stories. You confirm what is in scope, and every hour in the budget traces back to a story you kept. We check the hours the model suggests against what our team actually books on finished projects, then multiply by our published rate of $39-55 an hour. The result is an hours range, a budget range and a number of weeks. It’s a planning range, not a fixed quote, and it gives whoever owns the plan a baseline to track against. You can estimate your project’s cost and timeline in about four minutes.
No. A project manager owns the plan, budget, schedule and risks. A Scrum Master owns how the team works and has no authority over people or priorities. The 2020 Scrum Guide doesn’t include a project manager role at all.
Yes, but the habits differ. A Scrum Master coaches the team to plan its own work instead of assigning tasks, and measures success by working software each Sprint rather than by tracking a fixed plan.
The Scrum Guide doesn’t name a budget owner. In a startup the Product Owner, often the founder, usually holds it, because they decide what is worth building next. On larger programmes a project manager or finance owner tracks spending across teams.
Only when you have both a fixed outside plan and a team working in Scrum, for example several Scrum teams on one product with a budget board above them. For a small product team, a Scrum Master and a strong Product Owner are usually enough.
The Eighth Edition, published in November 2025, has six principles and seven performance domains (governance, scope, schedule, finance, stakeholders, resources and risk), brings back process guidance in a non-prescriptive form, and adds coverage of AI, project management offices and procurement.
Carefully curated content for resourceful Devs, CTOs, and PMs. No spam.