Career
Scrum Master
A Scrum Master helps a Scrum Team (and the wider organisation) use Scrum well. You remove impediments, protect focus, improve how work flows, and grow real ownership. You are not the team's secretary, a project controller, or a permanent translator between the Product Owner and Developers.
Open a section
What this job is responsible for
- Coaching Scrum practice, empiricism and a living Definition of Done
- Removing impediments and escalating with impact when the team cannot unblock itself
- Healthy events: Daily Scrum, Sprint Planning, Sprint Review and Sprint Retrospective
- Team working agreements and conditions for psychological safety
- Flow improvements with Lean and Kanban thinking where useful
- Coaching the organisation on roles, boundaries and anti-patterns that kill Scrum
Signs things are going well
- Daily Scrum is a team plan for the Sprint Goal, not a status report to you
- Retrospectives produce one change that sticks into the next Sprint
- Impediments have an age, an owner and a next move with a date
- Product Owner and Developers work together without you mediating every conflict
- Sprint Goals survive mid-Sprint noise and status theatre is named early
- RAG on team health is honest, and red is thanked rather than punished
How this role works with nearby roles
- Product Owner: Owns value and Product Backlog order. You coach how the team inspects and adapts around that backlog.
- Delivery Manager: May join up several teams or a programme. You own how well Scrum works for this team.
- Project Manager: Owns the plan and constraints outside Scrum. Share one RAID so you do not double up on status reporting.
- Agile Coach: Often works across teams or the profession. You stay accountable for this team's Scrum effectiveness day to day.
Who this guide is for
Scrum Masters, agile coaches and delivery practitioners who facilitate Scrum Teams in UK digital environments, including Civil Service and private sector contexts where titles differ but the craft does not.