Skills you need to be a scrum master
8 skills a hiring manager would actually test for, each with the level this role expects and what it is used for. Not a syllabus — the shape of the job.
Build my path to this roleUpskili checks what you can already do, then sequences only what is missing. No account needed.
What the role requires
Ordered by how much the job depends on it. The bar is the proficiency expected of a competent scrum master — not mastery, and not a passing acquaintance.
-
Agile frameworks (Scrum, Kanban)
Essential
Facilitates all team ceremonies and enforces agile principles.
Deep -
Jira
Essential
Manages backlog, sprints, and tracks team velocity.
Strong -
Stakeholder management
Essential
Aligns product owners, devs, and business on priorities.
Strong -
Conflict resolution
Important
Mediates team disagreements to maintain healthy dynamics.
Strong -
Confluence
Important
Documents sprint goals, retrospectives, and team agreements.
Strong -
Coaching
Important
Guides team toward self-organization and continuous improvement.
Strong -
Risk management
Useful
Identifies and escalates blockers before they impact delivery.
Working -
Slack
Useful
Facilitates async communication and daily standup updates.
Working
An order worth learning it in
A list of ten skills is the same unhelpful answer a catalogue gives, just sorted. This is where to actually start.
Start here
Essential to the role, and reachable from a standing start. Everything below rests on these.
- Conflict resolution
- Confluence
- Coaching
Then this
The rest of what the role is assessed on. Harder, and it builds on the foundation above.
- Agile frameworks (Scrum, Kanban)
- Jira
- Stakeholder management
What sets you apart
Not what gets you hired, but what separates doing the job from being trusted with it.
- Risk management
- Slack
You almost certainly have some of this already.
That is the point of starting from the role rather than a course. Upskili checks what you can do, then builds a path across only the gap.
See my path to scrum master