Scrum Master · Playbook
Scrum Master Playbook
A practical guide for serving the Developers, the Product Owner and the organisation. Standards describe what good looks like for public services. Methods describe how a team inspects and adapts. Keep those ideas separate so you do not bury the team in process, or run empty ceremony with no empiricism.
MAP-01 Scrum map
Scrum Guide fidelity & adjacent maps
Scrum is a framework for empiricism, not a ceremony catalogue.
Know the Scrum Guide accountabilities: Product Owner, Scrum Master, Developers. Events and artefacts exist to create transparency, inspection and adaptation. Add Lean and Kanban ideas when flow is the constraint. Reach for SAFe, MSP or programme ceremony only when the organisation truly needs that scale.
Maps you will actually use
| Map | Answers | Shape |
|---|---|---|
| Scrum Guide | How does this team create a usable Increment each Sprint? | 3 accountabilities · 5 events · 3 artefacts · DoD |
| Kanban | Where does flow stall, and what WIP limit would help? | Visualise · limit WIP · manage flow · policies |
| Lean | Which queues and hand-offs are waste? | Small batches · fast feedback · remove queues |
| DORA | Is release mechanics the real bottleneck? | Lead time · deploy frequency · change fail · restore |
| ADKAR | Why is Scrum adoption stalling for individuals? | Awareness to Desire to Knowledge to Ability to Reinforcement |
| GDS Service Standard | Is iterative working evidenced for a public service? | 14 points · user needs and continuous improvement |
Choose in practice
- Stable team, clear Product Owner, need for a Sprint Goal: stay with Scrum and coach fidelity.
- Board shows chronic multitasking or interrupt demand: add Kanban policies inside the Sprint.
- Release pain dominates retros: bring DORA trends before asking for more ceremony.
- Organisation is "doing Scrum" but accountabilities are blurred: teach the Guide before importing SAFe.
- UK public service assessment looming: map Reviews and DoD evidence to the Service Standard, not a paperwork scramble.
In DDaT terms, agile delivery roles often sit across Delivery Manager and related paths. Titles vary by department: Scrum Master, Agile Delivery Manager, Agile Coach. The accountability does not: someone must grow the team's ability to inspect and adapt. If that person is only a meeting booker, you do not have a Scrum Master.
Accountability ladder (typical agile delivery path)
- Associate / Junior SM: learning facilitation and impediment craft on a contained team with coaching.
- Scrum Master: accountable for one Scrum Team's effectiveness and working agreements.
- Senior SM / Agile Coach: complex teams or several teams, coaches other SMs, surfaces organisational impediments.
- Head of Agile Delivery / Lead Coach: owns the profession bar, hiring standard and organisational coaching agenda.
What you stop and start doing as you grow
You stop doing
- Running every event as the default facilitator forever
- Taking notes and updating the board as your primary value
- Measuring your week by how many meetings you attended
You start doing
- Coaching the team to run Daily Scrum and Retro without you
- Escalating organisational impediments with evidence and dates
- Measuring your week by ownership growing behind you
Three questions to run every day
If any answer is "no" for more than a week, that becomes the priority over calendar admin.
Facilitation is neutral process leadership, not directing the work. Protect the purpose of each Scrum event and call out theatre early. Timeboxes exist so conversation converges on a decision or a plan, not a monologue.
Ceremony purpose and red flags
| Event | Real purpose | Red flag it is broken |
|---|---|---|
| Daily Scrum | Developers re-plan the next 24 hours toward the Sprint Goal | Status report to the SM, DM or PO |
| Sprint Planning | Forecast a realistic Sprint Goal and plan | Capacity never checked; wish list accepted |
| Sprint Review | Inspect the Increment with stakeholders and adapt the backlog | Internal-only audience; demo of clicks with no feedback |
| Sprint Retrospective | One concrete improvement carried into the next Sprint | Same three complaints every fortnight, nothing changes |
| Refinement | Shared understanding of Ready work before Planning | Estimates without edge cases; PO monologue |
Facilitation moves that keep purpose alive
- Open each event by restating the purpose in one sentence, then park off-topic items.
- Prefer questions that return ownership to the team over answers that make you the bottleneck.
- Close with a decision, a plan adjustment or a named experiment. Never "good chat" alone.
- Rotate facilitation when the team is ready. Your silence is a coaching win, not neglect.
Event: …
Purpose (one line): …
Decision or output we need: …
Red flag we will interrupt: …
Impediments are not vibes. Log them. Distinguish delay from true blockage. Timebox your own moves. Escalate with impact when the team cannot unblock itself. Polite nudges without dates are not impediment management.
Impediment record minimum
| Field | Why it matters | Weak version |
|---|---|---|
| Name | Shared language, not a rant | "Things are slow" |
| Age | Shows organisational neglect | No date opened |
| Owner | Someone moves it | "The team" or "IT" |
| Next action + date | Creates a clock | "Following up" |
| Impact on Sprint Goal | Unlocks escalation | No link to value |
Escalation hygiene
- Each impediment has an owner and a next action date before the day ends.
- External blockers get escalation with impact and a ask, not endless polite nudges.
- You remove at least one named blocker visibly each week, and say out loud that you did it.
- RAID absorbs impediments that are risks or dependencies so DM and PM share one story.
Impediment: …
Age: … · Owner so far: …
Impact on Sprint Goal: …
Ask: decision or action needed by [date]
Use Kanban thinking inside Scrum when the board shows chronic multitasking. Watch cycle time and blocked age. Pair with DORA when release mechanics are the bottleneck. Hustle does not fix overload; policies do.
Flow signals to watch
| Signal | What it tells you | First coaching move |
|---|---|---|
| High WIP | Context switching is eating capacity | Agree a WIP limit and finish before starting |
| Blocked age rising | Impediments are unmanaged | Age the blockers; assign owners today |
| Long cycle time | Batches or queues are too large | Cut slice size; remove one approval queue |
| Weak DORA | Release path is the constraint | Smaller batches; automate the painful step |
- WIP limits exist and are respected in refinement and Daily Scrum conversations.
- Blocked columns have owners, not decorative sticky notes.
- Sprint burndown or flow charts drive conversation, not blame.
- Expedite policies are explicit so urgent BAU does not silently erase the Sprint Goal.
Flow metrics are for learning. If people hide work to game WIP limits, you have a safety problem, not a metrics problem. Fix the response to honesty first.
Match your intervention to readiness. Over-facilitating a capable team creates dependency. Under-teaching a new team creates zombie Scrum. The ladder is a daily judgement, not a permanent personality.
Modes and moves
| Mode | When | Move |
|---|---|---|
| Teach | New to Scrum or a broken practice | Explain the why, model the event, show the Guide |
| Facilitate | Team can run but drifts from purpose | Hold purpose, neutral process, interrupt theatre |
| Coach | Competence growing | Questions before answers; let them own the plan |
| Mentor / defer | Team owns practice | Observe, intervene rarely, work organisational impediments |
Signs you should step up or step back
Step up (teach / facilitate)
- Daily Scrum collapses into silence or status to you
- No Definition of Done, or it is ignored
- Retro produces venting with no experiment
Step back (coach / defer)
- Team can run Daily Scrum if you are absent
- PO owns prioritisation conflicts without you as translator
- Working agreements are enforced by the team, not by you
Publish a light RACI with Delivery Manager, Product Owner and Project Manager where roles overlap. Organisational coaching means naming the system that produces zombie Scrum: mid-Sprint injections rewarded, red RAG punished, and accountabilities blurred. In Civil Service contexts, help the team meet Service Standard ways of working without turning Scrum into a compliance script.
Boundary checks
- You do not rewrite the Product Backlog or set priority.
- You do not assign tasks as a default habit.
- You do surface organisational impediments upstairs with evidence and dates.
- You do protect the Sprint Goal with the Product Owner when noise arrives mid-Sprint.
What to coach upward
| Organisational pattern | Cost | Coaching ask |
|---|---|---|
| Stakeholders inject work mid-Sprint | Sprint Goal dies; trust dies | Park asks; show capacity trade-off |
| Status packs replace transparency | Watermelon RAG | Ask what decision the update changes |
| SM used as project controller | Team stops owning the plan | Clarify RACI; return planning to Developers |
| "Committee Product Owner" | No ordered backlog | Name one accountable PO |
Organisational coaching without a relationship upstairs is venting. Build enough trust with the SRO, DM or Head of Delivery that early amber is welcome.
Psychological safety is the belief that you can raise problems, admit ignorance and challenge ideas without punishment. Scrum depends on it. If people cannot say "this Sprint Goal is at risk", your metrics lie.
Weak versus strong signals
| Signal | Weak version | Strong version |
|---|---|---|
| Daily Scrum | Everyone fine, blockers never mentioned | Blockers named early without shame |
| Retro | Silence, or blame of absentees | Specific behaviours, one owned experiment |
| RAG | Always green until crisis | Early amber thanked publicly |
| Estimates | Padded or heroic to please | Honest capacity; negotiation with PO |
Working agreement craft
- Write three to seven agreements the team can actually keep. Revisit them in Retro.
- Include how you handle conflict, mid-Sprint asks and Definition of Done disputes.
- Model the standard: be first to admit a facilitation miss or an outdated assumption.
- Separate person from process. Critique the system that produced the miss.
The information does not change between Daily Scrum and a steering update. The altitude, the framing and the ask do. Clear asks beat journey narratives. Named owners beat anonymous "the business" pressure.
Audience calibration
| Audience | Detail level | What they want |
|---|---|---|
| Developers | High, plan and blockers | Cover from noise; help removing impediments |
| Product Owner | Medium, Sprint Goal and Ready risk | Partnership on injections and DoD |
| DM / peers | Medium, dependency and health | Early warning, shared RAID language |
| SRO / board | Low, outcome risk and decision | Recommendation and a clear ask |
Status: [RAG] because [single biggest team or flow driver]
What changed: …
What we are doing: action, owner, date
What we need from you: specific ask, or "visibility only"
Words to drop
| Drop | Use |
|---|---|
| "The team is busy" | "WIP is at [n]. Finishing A before starting B protects the Sprint Goal." |
| "Stakeholders keep interrupting" | "[Named person] asked for X mid-Sprint. Cost to Goal: Y. Recommendation: park until Planning." |
| "We need more process" | "The purpose of [event] is dead. Here is the redesign or cancel proposal." |
In UK public services, Scrum sits beside DDaT capability expectations, the GDS Service Standard and often programme governance (GovS 002, MSP). Your job is to keep empiricism alive inside that landscape, not to invent a second reporting religion.
- Map Sprint Reviews and user feedback to Service Standard points on user needs and iteration.
- Treat WCAG 2.2 AA as part of Definition of Done for public interfaces, with the PO and testers.
- Share one RAID and RAG story with the Delivery Manager and Project Manager.
- Prefer GOV.UK Design System patterns in Ready conversations when UI work is in scope.
- Coach assessment readiness as continuous evidence, not a cliff-edge slide pack.
Where Scrum meets government governance
- Sprint Goals stay team-owned even when programme milestones exist above.
- Status theatre for boards is challenged: ask what decision the update changes.
- Benefits and SRO asks route through the Product Owner for backlog order.
- Working agreements cover accessibility and operational handover, not only coding tasks.
Under pressure, the instinct is to add more meetings or more process. Diagnose first. A fix for the wrong cause costs a Sprint. Zombie Scrum, status theatre, missing DoD and mid-Sprint injections are the usual suspects.
| Symptom | Likely cause | First move |
|---|---|---|
| Zombie Scrum (ceremony without empiricism) | Purpose of events forgotten; DoD weak | Restate each event's purpose. Rewrite DoD with the team this week |
| Daily Scrum is status theatre | Reporting upward replaced team planning | Facilitator leaves the circle; Developers re-plan to the Sprint Goal only |
| No Definition of Done, or it is ignored | Quality never made explicit | Write a minimal DoD today; refuse "done" without it |
| Mid-Sprint injections | Sprint Goal not defended with the PO | Park asks in the backlog. Show capacity cost. Escalate the pattern if needed |
| Retro changes nothing | No owned experiment, or unsafe to name real issues | One change, one owner, check in next Retro; thank honesty |
| Watermelon team health (green slides, red reality) | Reporting punishes honesty | Thank the next person who reports red early |
| Everything blocked, nothing escalated | Impediments have no age or owner | Open an impediment log with age, owner, next date today |
| SM assigning tasks | Role blur into project control | Return planning to Developers; publish RACI with DM/PM |
| PO absent or "committee PO" | No single backlog owner | Escalate for one named Product Owner; coach interim ordering hygiene |
| High WIP, no finishes | Starting feels safer than finishing | Set a WIP limit; swarm oldest items first |
The one-minute checklist
- Name the Sprint Goal in one sentence. If you cannot, that is the fire.
- Biggest impediment: age, owner, next move?
- Is this a Product Owner, team, or organisation problem?
- Is the pain zombie Scrum, status theatre, missing DoD, flow, or safety?
- What one experiment will we run after the next Retro, and who owns it?
Glossary anchors
- Scrum: accountabilities, events, artefacts, DoD
- Sprint Goal: the single commitment for the Sprint
- DoD: Definition of Done
- WIP: Work in Progress
- DORA: delivery performance metrics
- ADKAR: individual change journey
- RAID: Risks, Assumptions, Issues, Dependencies
- RAG: Red, Amber, Green status
- RACI: Responsible, Accountable, Consulted, Informed
- GDS: Government Digital Service
- Service Standard: 14 points for public services
- SRO: Senior Responsible Owner
Companion: the cheatsheet distils every section into a one-screen field reference.