Free Scrum Master Practice Assessment (2026)

Cohesyve · Practice for candidates

Going for a Scrum Master role? Find out how you'd actually score.

Run a Scrum Master simulation built the same way employers build theirs, and get a full report showing exactly where you lost marks — before it counts.

free assessments a month

no card required

Full

scored report every run

Every

question type included

5 free assessments a month · No card required · Pro from $16/mo

Overview

Scrum Master assessments are scenario work, not certification questions. You are given a team in trouble — a sprint that keeps slipping, a retrospective nobody speaks in, a product owner who changes scope mid-sprint — and asked what you would do first. Some include a facilitation exercise or a written team-health note. This page covers what these assessments contain and what separates process knowledge from actual facilitation judgement.

Why employers assess this role

Certification proves attendance, not capability, and the ceremonies are easy to describe and hard to run well. Employers assess with scenarios because the difference between a Scrum Master who improves a team and one who administers a board only becomes visible when something is going wrong.

What gets tested

Facilitation of ceremonies that are not workingImpediment identification and removalCoaching individuals and teamsHandling conflict within a teamWorking with a difficult product ownerReading delivery metrics honestlyProtecting the team without becoming a barrierAdapting the process to the team rather than the reverse

The format

Duration

45–75 minutes

Question types

Team scenario with written response
Facilitation role-play or planned agenda
Delivery metrics interpretation
Situational judgement on conflict and stakeholder pressure

Levels

Entry · Mid · Senior

What you'll be asked to do

Fix a ceremony that has stopped working

Stand-ups that have become status reports to a manager, retrospectives with no honesty in them, planning sessions that overrun. You are asked what you would change and how you would run the next one.

•Design the agenda for a retrospective in a team where nobody raises problems
•Fix a stand-up that has turned into a fifteen-person status meeting
•Restructure a planning session that consistently overruns without producing a plan

Remove an impediment

Something outside the team is blocking it — a dependency, an approval, an absent decision. Assessors look at whether you escalate with specifics and whether you address the cause or the instance.

•The team is blocked waiting on another team for the third sprint running
•A key approval sits with someone who never responds; set out your approach
•Two developers are pulled into unplanned support work every sprint

Handle conflict and behaviour

Interpersonal scenarios: a dominant voice, a disengaged member, a disagreement that has become personal. Marked on whether you act early and whether you address it privately or publicly as appropriate.

•One engineer dominates every discussion and others have stopped contributing
•Two team members disagree publicly and it has become uncomfortable
•A team member consistently commits to work they do not complete

Manage pressure from outside the team

A stakeholder or product owner pushing scope, dates or people. Assessors want a position, not deference in either direction.

•The product owner adds work mid-sprint every sprint; respond
•A senior stakeholder asks for a firm date the team cannot honestly give
•Management asks you to report individual velocity for performance reviews

Cohesyve for candidates

Practise a Scrum Master assessment before the real one

Run the same AI job simulations companies use to evaluate applicants. You get a scored report showing where you're strong and where you're not, plus what to work on.

Sample tasks — and what strong looks like

A team has missed its sprint goal four sprints in a row. Set out what you would do first.

Mid

What strong looks like: Investigates before intervening — looks at whether the goal was ever realistic, at how much unplanned work arrived, and at whether the team feels able to say no — then addresses one cause rather than adding process. Weak answers immediately propose more granular estimation or a longer planning meeting.

Design a retrospective for a team where the same issues are raised every time and nothing changes.

Mid

What strong looks like: Breaks the pattern deliberately, focuses the session on one issue with a named owner and a date rather than a long list of observations, and revisits previous actions openly. Weak answers pick a new retrospective format and change nothing about follow-through.

Management asks you to report individual velocity so it can feed performance reviews. Respond.

Senior

What strong looks like: Declines clearly and explains the predictable consequence — inflated estimates and hoarded work — then offers what management actually needs: visibility of delivery and predictability at team level. Weak answers either comply or refuse without offering an alternative.

A new team has just formed and wants to skip retrospectives because they feel like a waste of time.

Entry

What strong looks like: Takes the objection seriously rather than defending the ceremony, agrees a short trial with a specific improvement in mind, and lets evidence make the case. Weak answers assert that the framework requires it.

How to prepare

#1
Practise writing what you would do in the first week with a struggling team, and make sure the answer starts with observation rather than a new process.
#2
Prepare a real agenda for a retrospective where trust is low, including how you would handle silence in the room.
#3
Rehearse declining a request from a senior stakeholder while offering a workable alternative, since these scenarios appear in almost every assessment.
#4
Practise reading delivery data honestly — a burndown that always looks fine near the end usually indicates work being reshaped rather than finished.
#5
Get comfortable coaching one person about behaviour, privately and specifically, and write out how that conversation would open.
#6
Do a full timed mock combining a team scenario and a facilitation plan, because assessments reward concrete next steps over framework vocabulary.

Common mistakes

Quoting the framework as the reason for a decision instead of the outcome it produces.
Adding process in response to a problem that more process will not fix.
Escalating an impediment without specifics, an owner or a date.
Treating a persistent team conflict as something the team will resolve on its own.
Shielding the team so completely that stakeholders lose all visibility.
Describing ceremonies you would run without saying what would change as a result.

How it's scored

Criterion	What strong looks like
Facilitation judgement	Designs a session with a purpose and an outcome, manages the quiet and the dominant voices, and adapts when the room does not respond.
Diagnosis before action	Investigates the cause of a delivery problem before changing the process, and names what evidence would confirm the hypothesis.
Impediment handling	Escalates with a specific ask, an owner and a date, and works on the recurring cause rather than the individual blocker.
Coaching and conflict	Addresses behaviour early, privately and specifically, and coaches toward the team resolving it rather than depending on the Scrum Master.
Stakeholder handling	Holds a defensible position under pressure, gives honest forecasts with uncertainty attached, and offers alternatives rather than refusals.

Frequently Asked Questions

Do I need a certification to pass the assessment?

A certification may get you the interview, but these assessments are scenario-based and mark judgement. Candidates who quote the guide without saying what they would actually do on Monday morning tend to score poorly.

Will I have to facilitate something live?

Sometimes, particularly at mid and senior level. More often you are asked to write the agenda and explain how you would handle specific moments — silence, dominance, or a disagreement that surfaces mid-session.

How much do delivery metrics come up?

Regularly, but the test is interpretation rather than calculation. Assessors want to see whether you can read a chart honestly, including when it is flattering the team, and whether you resist using velocity as a performance measure.

Is Kanban or SAFe knowledge expected?

Only if the employer uses it, and it is normally stated in advance. What travels across every context is the ability to diagnose why a team is not delivering and to change one thing at a time.

How should I practise for a scenario-based assessment?

Work through scored scenarios and read the feedback on your reasoning. Cohesyve includes five free assessments each month, so you can find out whether your answers read as facilitation judgement or as framework recitation.

Practise another role

Cohesyve · Practice for candidates

Practise a Scrum Master assessment now — free.

Five scored assessments a month, a full report on every run, and a learning pathway built from what you got wrong. No card required.