PMP vs Scrum Master vs Agile Coach: Which Test to Use
Hiring? Send candidates a scored, cheat-resistant assessment.Start free
Three roles, three different signals
A PM leads across organizations. A Scrum Master coaches a single team. An Agile Coach helps organizations scale frameworks. They share vocabulary but require completely different skills. Yet most teams assess them the same way — or worse, confuse the role.
The result: you hire a Scrum Master who can't navigate politics, or a PM who can't build team coherence, or a coach who's never shipped anything. This post breaks down the three roles, what to test for each, and the assessments that work.
The three roles defined
Project Manager
Owns the outcome of a specific project or initiative. Has authority (or can build it) to allocate resources, make trade-off calls, and coordinate across teams. Accountable for timeline, scope, and often budget.
Key judgment: "We can ship on time with fewer features, or late with all features, or expensive with contractors. I choose: fewer features because the customer's decision deadline is August, not revenue impact of the feature set."
Scrum Master
Coaches one agile team. Removes impediments, facilitates ceremonies, and helps the team improve its process. Has no authority over the product or hiring; that's the product owner and the team lead.
Key judgment: "The team is drifting in refinement meetings. I'll run a separate session to define what 'done' means, then use that in future refinements to move faster."
Agile Coach
Helps organizations implement or scale agile frameworks. Works across multiple teams, advises leadership on structural changes, and resolves conflicts between teams or frameworks.
Key judgment: "The organization has three teams using different estimation practices. I'll propose a common taxonomy, pilot it with one team, and if it works, roll it across the three."
Why traditional PMP doesn't work for Scrum Masters
The Project Management Professional (PMP) certification tests predictive scheduling, risk management, cost control, and stakeholder integration across a whole project lifecycle. It assumes the PM has authority and a defined scope.
A Scrum Master's job is different: remove blockers for one team, improve iteration velocity, and hold ceremonies. They have no authority to reassign resources or descope the product. PMP teaches the wrong mental model.
If you hire a PMP for a Scrum Master role: They'll want to control the scope, fight with the product owner, and try to predict things that can't be predicted in agile work.
If you hire a Scrum Master for a PM role: They'll facilitate discussions but not make calls. They'll ask the team "how should we handle this?" when they should be deciding.
Assessment by role
For Project Managers: Decision-making + stakeholder navigation
Test what matters:
- Scenario problem (30 min): Can they make clear trade-off decisions under constraints?
- Prioritization problem (20 min): Can they distinguish important from urgent and defend the ranking?
- Risk assessment (15 min): Can they identify cross-team dependencies and mitigate proactively?
- Behavioral interview (30 min): Have they navigated politics, reset expectations, delivered bad news?
Hiring bar: Score 4+ on decision-making and risk judgment. Score 3.5+ on stakeholder influence. Lower on ceremony or process knowledge.
For Scrum Masters: Team coaching + process design
Test what matters:
-
Impediment problem (20 min, live): "Your team is slow in standups, refinement is chaotic, and two engineers are in conflict about the sprint goal. What do you do?"
- High signal: Ask clarifying questions first ("What does 'slow' mean — we talk 45 minutes when we should talk 15?"). Propose specific interventions tied to the problem. Don't assume you can fire someone or remove a team member.
- Low signal: "I'd improve communication" or "I'd run better ceremonies."
-
Retrospective response (15 min, live): "Your team did a retro and surfaced that they're blocked by another team's API. They're frustrated. How do you help them move forward?"
- High signal: "I'd help them articulate the specific blocker, then I'd set up a working session with the other team lead to unblock it." (Ownership through influence, not authority.)
- Low signal: "I'd escalate it" or "I'd tell them to just work around it."
-
Behavioral interview (30 min): Have they coached individuals, resolved team conflicts, or driven process improvements?
- Good examples: "I noticed the team wasn't estimating story size correctly, so I ran a session on story pointing and observed us get much faster."
- Bad examples: "I told the team to follow the Scrum framework" or "I escalated the problem to the PM."
Hiring bar: Score 4+ on coaching and empathy. Score 3.5+ on process design. Lower on strategic thinking or cross-org influence.
For Agile Coaches: Organizational design + facilitation
Test what matters:
-
Scaling problem (30 min, live): "An organization has four teams. Two use Scrum, one uses Kanban, one uses custom waterfall-agile. They're shipping on different cycles, and it's hard for leadership to track progress across teams. How do you help them align?"
- High signal: "I'd first understand why each team made their choice (different product types? different leadership? different maturity?). Then I'd propose a common cadence — not a common framework — so all teams review progress every two weeks. That lets leadership track across teams while respecting team-level autonomy."
- Low signal: "I'd tell them all to use Scrum" or "It's complicated."
-
Conflict resolution (15 min, live): "A PM wants a team to commit to a date. The Scrum Master says you can't commit in agile, you only forecast. How do you bridge that?"
- High signal: "I'd separate concerns: we can do a capacity plan (forecast), and separately, we can identify business risks and build buffer into the plan (commitment). The PM gets a date they can use with customers; the team gets realistic expectations."
- Low signal: "Agile doesn't do commitments" or "The PM needs to learn agile."
-
Behavioral interview (30 min): Have they driven org change, scaled frameworks, or resolved multi-team conflicts?
- Good examples: "Two teams had incompatible definitions of done, which blocked handoffs. I led a working group to define a shared standard, piloted it with one team, then rolled it across."
- Bad examples: "I trained people on agile" or "I created a process document."
Hiring bar: Score 4+ on organizational thinking and change management. Score 3.5+ on facilitation. Lower on hands-on team coaching.
Common hiring mistakes
Mistake 1: Posting for a "Project Manager/Scrum Master" role. These are different jobs. If you're building a small team, you need a Scrum Master, not a PM. If you're shipping a big initiative, you need a PM.
Mistake 2: Using the same assessment for all three roles. A PM should be tested on decision-making. A Scrum Master should be tested on coaching. An Agile Coach should be tested on systems thinking. Reusing the same test is like assessing engineers and designers the same way.
Mistake 3: Overweighting certifications. PMP, CSM, and CAL credentials show someone has studied frameworks. They don't show judgment. If someone says "I have a PMP, so I can manage anything," be skeptical. Test them on the role you actually have.
The comparison matrix
| Dimension | Project Manager | Scrum Master | Agile Coach |
|---|---|---|---|
| Authority | Has it; makes trade-off decisions | Doesn't have it; influences through coaching | Doesn't have it; influences through frameworks |
| Scope of focus | Whole project, multi-team | One team | Multiple teams, organizational systems |
| Key skill | Decision-making under constraint | Team coaching and process design | Organizational change and alignment |
| Red flag | Can't decide; hedges | Can't coach; escalates; | Can't think systems; prescribes one framework |
| Assessment priority | Risk judgment + stakeholder skill | Coaching examples + process thinking | Change management + facilitation |
How to choose which role you need
You need a Project Manager if: You're launching a new product, integrating two teams, or shipping an initiative that spans multiple teams and has a hard deadline.
You need a Scrum Master if: You have a single team that's struggling with sprint execution, refinement, or conflicts within the team.
You need an Agile Coach if: Your organization is scaling agile practices, teams are using different frameworks, or you're trying to improve across teams.
Many orgs hire a PM and a Scrum Master. They're both useful, but they're different. Assess them differently, hire for different strengths, and set different success metrics.