What is the job of a Scrum Master?
The job of a Scrum Master consists of helping a team organize itself with Scrum, an agile work framework widely used in software development and also in other areas. In Scrum, work is split into short cycles, called sprints, at the end of which the team shows something finished and reviews how it worked. The Scrum Master is not the team's boss: the role is to make sure the method is understood and used well, and that nothing blocks the progress of everyone else.
A typical day includes a short meeting with the team to see what was done and what comes next, and a series of informal conversations to clear up problems: a person waiting for an answer, a tool that is failing, a doubt about what was requested. The Scrum Master also prepares and leads meetings such as the planning of the cycle and the final review, and keeps other parts of the organization informed. More time goes into talking, listening and organizing than into programming or designing.
Typical tasks
- Leading Scrum meetings so that they are orderly, short and useful.
- Identifying the team's obstacles and working with other departments to solve them.
- Explaining the rules and goals of Scrum to people who join the team.
- Helping to keep pending work visible, for example on a physical or digital board.
- Supporting the Product Owner in keeping the list of pending work ordered and clear.
- Facilitating the review of how the team worked and suggesting small improvements.
- Mediating when people on the team disagree.
Subjects and content usually covered
- Principles of the agile manifesto and the values of Scrum.
- Scrum roles, events and elements: sprint, backlog of pending work, review and retrospective.
- Other agile approaches, such as Kanban and methods for scaling work across several teams.
- Techniques for facilitating meetings and workshops.
- Communication, listening and conflict handling in teams.
- Basics of how software is developed: testing, releases and working with code.
- Task tracking tools and ways of measuring the flow of work.
Usual duration and type of training
There is no single degree for this job. Many people arrive with a university degree of 4 to 5 years in engineering, computer science, business administration or similar fields, and add Scrum-specific courses that usually last from a few days to a few weeks. Others combine several years of experience in a team with short training. The length and type of training vary by country and by company, and options exist both in person and online.
How you get there and what is usually required to practice
There are several ways in. It is common to come from another position within a team, such as development, testing, analysis or project management, and move into facilitating the work of others. Some people also arrive from studies in business administration, organizational psychology or engineering and start in team support roles.
There is no mandatory official license to practice. In many countries companies value certificates from Scrum courses and, above all, previous experience working in agile teams. It is worth knowing that the first position is usually hard to get without some experience in working teams.
Skills that help
- Listening closely and asking questions that help the team clarify its ideas.
- Leading meetings by giving everyone a turn to speak and watching the time.
- Mediating in disagreements without imposing a position.
- Explaining concepts in a simple way to people with different levels of knowledge.
- Organizing information and tasks so that they are visible and clear.
- Talking with people in different positions, including those who make decisions.
Career paths and job opportunities
- Software development companies and technology consultancies.
- Banks, insurers and other financial companies with technology departments.
- Telecommunications and e-commerce companies.
- Public bodies with digital projects.
- Companies in other sectors, such as health or industry, that use Scrum in non-technical areas.
- Freelance work, or consultancies that support several teams.
What you are not always told
- The role has little formal authority: influence comes from trust and conversation, not from giving orders.
- It is easy for an organization to use Scrum only halfway and to ask the Scrum Master for control or secretarial tasks that are not part of the role.
- The results of the work are hard to see: if the team runs well, it looks as if the Scrum Master did almost nothing.
- Often the same person supports more than one team, which multiplies meetings and changes of topic.
- The first position can be hard to get, because many job offers ask for previous experience in teams.
How the field is changing
Many teams work in a mixed or distributed way, so meetings and boards rely on digital collaboration tools. Some tools already summarize meetings or suggest improvements, which reduces administrative tasks and puts more weight on supporting people. The way the role is understood is also changing: in several organizations it is combined with other functions or comes closer to the work of a team coach, and there is debate about how much pure Scrum is appropriate compared with mixes of methods.
Want to know if this is the right career for you?
Take the free vocational test with 5 scientific methods — CHASIDE, Holland, Big Five, MMMG and VAK — to get your personalized profile. You can also explore all university careers or learn about the scientific methodology.