Scrum master screening questions: certifications, ceremonies and metrics
On this page
- Which scrum master seat: single team, multi-team or coach-hybrid
- Certifications: what CSM and PSM actually prove
- Ceremonies: the practice test
- Removing impediments: the story question
- Metrics: what they track and how they're misused
- Team and stakeholder conflict
- How scrum master resumes overstate the work
- Knockout checklist and scorecard
- Questions people ask
A scrum master screen should separate two very different things: knowing the Scrum Guide, and actually running a team through a stuck sprint, a stakeholder who keeps interrupting the team, or a velocity number leadership is misusing. Ask which certifications they hold, then set the certification aside and ask for a specific impediment they removed, a ceremony they changed because it wasn't working, and what they do when a product owner and the team disagree. Candidates with real practice answer in specifics: team size, sprint length, the actual problem, what they tried.
This overlaps with project manager phone screen questions and product manager phone screen questions in some companies, since titles blur across the three. Ask what the candidate actually owned — team facilitation and impediment removal is a scrum master's job; scope and budget belong to a project manager; what gets built belongs to a product manager.
Which scrum master seat: single team, multi-team or coach-hybrid
| Seat | What the work usually is | Facts to ask for | Common overstatement |
|---|---|---|---|
| Single-team scrum master | Runs ceremonies, removes impediments and shields one team's focus | Team size, sprint length, tenure with that team | Impediments that were actually resolved by the manager, not the scrum master |
| Multi-team scrum master | Supports two or more teams, often with more coordination and dependency work | Number of teams, how dependencies were managed across them | "Supported five teams" meaning attended their standups without real involvement |
| Scrum master / agile coach hybrid | Coaches beyond one team: org-level agile practices, coaching other scrum masters | Which teams or scrum masters they coached, and one specific practice they changed | "Agile coach" title for someone who has only ever run one team's ceremonies |
| Scrum master / project manager hybrid | Blends facilitation with schedule and stakeholder reporting duties | Which parts were scrum master work versus project management work | Command-and-control project management relabeled as scrum mastery |
Certifications: what CSM and PSM actually prove
Neither certification is legally required, and neither tests real-world team facilitation. Know what each involves (as of September 2026):
| Credential | Issuer and requirement | What it does not test |
|---|---|---|
| CSM (Certified ScrumMaster) | Scrum Alliance. A 16-hour course from a Certified Scrum Trainer, then a 50-question exam (37 correct to pass); no prior scrum experience required, per Scrum Alliance's CSM page | Whether the candidate has ever actually run a sprint or handled a real team conflict. |
| PSM I (Professional Scrum Master I) | Scrum.org. A standalone assessment, no required course, with a stated 85 percent passing score, per Scrum.org's certification pages | Same gap as CSM; it is knowledge of the framework, not applied practice. |
| A-CSM / PSM II or III | Advanced tiers from each body, generally expecting practical experience beyond the entry level | Still self-assessed knowledge rather than a verified employment record. |
- "Which certification do you hold, and what's one thing from the course you've actually changed in how you work?" Strong: a specific practice change. Red flag: recites Scrum Guide definitions with no applied example.
- "How long have you been practicing versus when did you certify?" A candidate certified last month with years of informal scrum master-adjacent experience is a different story than one who certified and has never run a team.
Ceremonies: the practice test
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| Walk me through how you run sprint planning. | Describes capacity discussion, backlog refinement done beforehand, and how the team, not the scrum master, commits to the sprint. | Describes assigning work to people themselves. |
| How do you keep daily standup from becoming a status report to you? | Team talks to each other, not to the scrum master; specific technique for redirecting a status-report habit. | Standup is people reporting to the scrum master one at a time. |
| What do you do in a retrospective that isn't just "what went well / what didn't"? | Names a specific format change and why, and an action item that actually got implemented afterward. | Every retro is the same three questions with no follow-through on actions. |
| Tell me about a ceremony you changed because it wasn't working. | A specific problem (retros with no action, standups running long) and a specific fix they tried. | Every ceremony has run exactly the same way at every job. |
Removing impediments: the story question
Ask: "Tell me about an impediment you removed that the team could not have removed on their own." This is the single best question for separating people who facilitate meetings from people who actually protect a team.
- Strong: "A dependency on another team was blocking two stories for a week. I went to their scrum master directly, we agreed to reprioritize one story ahead of the sprint boundary, and I updated both teams' boards so it was visible."
- Weak but honest: "Mostly I escalate things to the engineering manager." Fine for a junior scrum master, but ask what they escalate and what they try first.
- Red flag: cannot name a specific impediment at all, or describes only administrative tasks (updating the board, sending reminders) as their main function.
Metrics: what they track and how they're misused
Worked example: velocity used as a target (invented numbers)
A team's velocity was 32, 35, 30, 33 points per sprint. A new director asks the scrum master to "get velocity to 40."
- A scrum master who understands velocity explains it is a planning input specific to that team's own estimating scale, not a productivity target comparable across teams or improvable on command.
- Ask: "What would you say to that director?" A strong answer pushes back with the reasoning above. A weak answer either complies silently or has no framework for the conversation at all.
- "What metrics do you track for a team, and what does each one actually tell you?" Strong: velocity as a planning tool, sprint predictability (committed versus completed), cycle time, and the limits of each.
- "Have you ever seen a metric gamed? What did you do?" Strong: a specific example, such as stories being split to inflate point counts, and how they addressed the root cause.
Team and stakeholder conflict
- "What do you do when the product owner and the team disagree on what 'done' means?" Strong: facilitates a conversation back to the definition of done the team agreed on, rather than picking a side.
- "Tell me about a stakeholder who kept interrupting the team mid-sprint." Strong: a specific boundary they set and how they protected the sprint commitment without becoming the team's only point of contact.
- "How do you handle a team member who consistently doesn't deliver what they committed to?" Strong: coaching conversation first, involves the team's own norms, escalates to the manager only if it continues. Red flag: "that's a management problem, not mine" with no attempt to address it at the team level first.
How scrum master resumes overstate the work
| Claim | Question to test it |
|---|---|
| "Certified Scrum Master" | "What have you actually run — how many sprints, how many teams, for how long?" |
| "Improved team velocity by 25 percent" | "Over what baseline, and did the story point scale change at the same time?" (A rescale can fake a velocity increase.) |
| "Led agile transformation" | "What was your actual role versus the coach's or the leadership team's?" |
| "Removed blockers daily" | "Give me one specific blocker, not a general description of the job." |
Knockout checklist and scorecard
Must-ask on every scrum master screen
- Seat: single-team, multi-team, coach-hybrid or project-manager-hybrid.
- Certification held, and one practice they've actually applied from it.
- One ceremony they changed because it wasn't working.
- One impediment they personally removed.
- Metrics they track and whether they understand their limits.
- One real conflict handled between the team and a stakeholder or product owner.
Knock out, or flag before submitting, if the candidate can recite the Scrum Guide but cannot describe a specific impediment they removed; if every ceremony and metric story is generic with no team size or timeframe attached; if the role needs multi-team coordination and the candidate has only run a single team; or if they describe velocity or points as a performance target rather than a planning tool.
| Area | 1 | 2 | 3 | 4 |
|---|---|---|---|---|
| Certification vs. practice | Certified, no applied practice | Some practice, limited depth | Certified and clearly practicing it | Coaches others in the practice |
| Impediment removal | No specific example | Administrative examples only | One real cross-team impediment | Pattern of proactive impediment removal |
| Ceremonies | Textbook description only | Runs them, no adaptation | Adapted a ceremony with a reason | Consistently improves ceremonies with team input |
| Metrics literacy | Treats metrics as targets | Tracks basics | Understands metric limits | Teaches the team to read metrics correctly |
| Logistics fit | Deal-breaker | Two open questions | One open question | All aligned |
Write the evidence next to each score in the candidate's own words: "Pushed back on a director who wanted velocity at 40, explained points aren't comparable across teams, kept the team's own scale." Interview Signal attaches quotes like that to each score from the call, which is useful here specifically because certification claims are easy to state and hard to verify without the candidate's own words on record.
Questions people ask
Does a CSM or PSM certification mean someone can actually run a scrum team?
No. A Certified ScrumMaster requires a course and a 50-question exam with no prior scrum experience needed, and Scrum.org's PSM I is a standalone assessment that does not require a course at all. Both prove someone learned the framework; neither proves they have run a real team through a real impediment. Test the practice on the call.
What is the difference between Scrum Alliance's CSM and Scrum.org's PSM?
CSM requires attending a 16-hour course from a Certified Scrum Trainer, then passing a 50-question exam (37 correct required). PSM I is a standalone assessment anyone can register for, with no required course, and a stated 85 percent passing score. Both are widely recognized; neither is a legal requirement to work as a scrum master.
How many teams should a mid-level scrum master be able to support?
There is no fixed number; it depends on team maturity and how much coaching the role includes. Ask how many teams they currently support and whether that number changed over time, and judge whether it fits what this role actually needs.
Is velocity a good metric to ask a scrum master about?
Ask about it to see if they understand its limits. A scrum master who treats velocity as a target to hit, rather than a planning input that varies by team and sprint, is a red flag, since that is one of the most common ways teams get pushed into bad estimating habits.