Is the Scrum Master Role Right for Me? 7 Questions to Consider
Scrum Master is a lucrative role. It has good earning potential. Obtaining a Scrum Master certification, PSM or CSM, is achievable within a short period of time.
However, while anyone could take the role, not everyone will be happy or successful performing it.
Give honest answers to the following questions to see if the Scrum Master role is a good fit for you.
1. Do you have an Agile mindset?
It seems obvious that anyone who wants to work with the Scrum framework should be in an Agile headspace.
But sometimes, it’s the obvious, implied things that get overlooked. Let’s make sure we’re on the same page.
An Agile mindset is characterized by:
- Being open to feedback, including negative feedback
- Creating an open, respectful work environment
- Desire to deliver value
- Embracing complexity and challenges
In a related article, we discuss how an Agile mindset could be developed, its similarities and differences from Growth and Lean mindsets, and how to apply the Agile principles beyond the workplace.
2. Do you enjoy helping others?
Do you find it rewarding to give others guidance to achieve their better self?
Do you feel inspired that you could make a difference and help others change their situation?
Do you find joy in clearing obstacles to unlock their potential – even if they won’t attribute their success to you?
3. Do you seek recognition?
A Scrum Master derives pleasure from the success of others.
The ultimate goal of a Scrum Master is to make the process run so smoothly that their assistance is no longer needed.
Does it mean the Scrum Master can be fired once the team achieves high performance and learns to resolve most of its internal issues?
There will be “wear and tear” – new uncertainties, new conflicts, new actors, new challenges. The Scrum Master will help the team navigate them and maintain the system the Scrum way.
But maintenance doesn’t bring praise.
If you had to pick one, what would you prefer: giving praise or receiving it?
Like with the heart, we don’t give it a second thought while it beats steadily.
Are you fine with quietly knowing the vital role you’re playing, without getting much external acclaim?
4. Can you exert influence without authority?
The term “Servant Leadership” was used to describe the leadership style of a Scrum Master.
It was removed in the 2020 edition of the Scrum Guide to avoid a potential misinterpretation of a Scrum Master as a “servant”. But the concept remains relevant and valuable.
An authoritative leadership style isn’t an option for a Scrum Master, not only because the controlling, demanding manner isn’t in the spirit of Agile. A Scrum Master isn’t in a position to assign consequences.
While they can remove a team member – even the Product Owner – from the team if there’s a prolonged conflict and all other methods are exhausted, this is done as a very last resort.
Emotional intelligence, expertise, and the ability to build trust are some of the factors that allow Scrum Masters to influence without authority.
Can you be convincing without pushing?
Can you appeal to people’s logical and emotional side, so they come to a conclusion themselves, without feeling like it was imposed on them?
What is Servant Leadership?
The term was coined by Robert K. Greenleaf in his 1970 essay, The Servant as Leader.
A servant-first leader thrives to help others grow rather than accumulating power and control for themselves. Empowering others, making them wiser and more autonomous is more beneficial to everyone in the long run.
Empathy, awareness, persuasion, and foresight are among the characteristics of effective servant leaders.
5. Does being “out of control” make you nervous?
When you’re presented with a problem or a challenge, does your brain kick into high gear, producing a strategic plan that you’re eager to bring to life?
If you like actively implementing solutions, the Scrum Master role isn't a great fit.
You cannot impose the “best practices”. Anything that is related to the way of working is fully in the hands of the self-managing team of Developers.
If you think a certain workflow or tool would be great to improve efficiency, you could try pitching it, but you can’t directly tell the Developers what they should be using.
You’ll have to fully trust them. You need to be comfortable living with uncertainty.
How does it make you feel?
- Frustrated that you could only give some gentle hints and nudges instead of optimizing the process directly.
- Relieved that the responsibility of this nature doesn’t rest on your shoulders.
- Excited to see what the team will come up with.
Guess which perspective would leave you in a better place as a Scrum Master.
6. How well do you handle conflict?
When you work with people, there might be personality clashes, unrealistic demands, and various kinds of issues and misunderstandings.
How do you feel when you interact with people who are frustrated, aggressive, or defensive?
- Can you understand someone’s perspective without being judgemental, even if it’s the opposite of yours?
- Are you familiar with de-escalation techniques?
- Can you avoid taking sides, even if you like one party more than the other?
Most of the time, it’s less about handling an active conflict and more about spotting misunderstandings and brewing issues and diffusing them before they cause trouble.
However, you should be mentally ready. If something happens, it’s your responsibility to guide your teammates through the situation.
Can you help the parties fix their issues in a respectful, constructive debate?
7. Are you an eager learner?
If you cannot give decisive answers to some of the questions above, does it mean that the Scrum Master role isn’t for you?
If the following is true:
- Agile and Scrum values and approaches resonate with you
- You find joy in selflessly helping others
- Stances of a Scrum Master describe the place where you want to be
Then you could definitely pursue the Scrum Master role.
Scrum is all about inspection and adaptation. Act, try, observe, get feedback, and improve your skills.
Are you ready to learn from your team and learn with your team?
Are you willing to deepen your understanding of Scrum and Agile and enhance your mastery, no matter what level you are on?
More questions related to the Scrum Master role
Scrum Master vs. Project Manager: what is the difference?
Modern project management has a lot of Agile elements. Both roles heavily rely on communication skills and deal a lot with problem resolution.
But a project manager is more of an active organizer. Scrum Master is a facilitator who is supposed to coach people and steward them without directly telling them what they need to be doing.
A project manager is responsible for the setup and maintenance of the process and is accountable for the outcomes it produces.
Scrum Master is responsible for promoting the Scrum values, facilitating Scrum on the team level, and promoting the Agile culture within the organization.
Related: Should I become a project manager?
Do you need to be certified to become a Scrum Master?
Certification isn’t necessary to take up the Scrum Master role, especially if you change positions internally within the organization. What’s important is having soft skills and an understanding of the Scrum principles.
But if you look at the job postings, nearly all of them mention that certification is preferred.
Related: CSM vs. PSM: Which Scrum Certification is Right for You?
Most importantly, though, is that getting ready for and successfully passing the exam will enhance your understanding of Scrum and help you be a more successful Agile practitioner.
In particular, the second level of the Professional Scrum Master certification (PSM II) by Scrum.org is a good challenge – with active learning, you could take it even if you’re relatively new to Scrum, and get a great head start.
Here’s my guide to preparing for the PSM II exam.
Does a Scrum Master need to be technical?
Having technical background will help you better understand the challenges that the Developers are facing. Understanding the context will help with asking questions that bring you to the core of the issue.
But the specific technical context isn’t critical – it could be picked along the way as you interact with the team.
For a Scrum Master, soft skills are the most important – the ability to communicate, listen, explain, coach, lead, facilitate, and so on.
Can a Scrum Master also be a Developer?
“Developer” is used in a broad sense in Scrum. It could be a designer, a programmer, or any other team member whose work directly adds value to the product.
Those people used to be called “the Development Team”. Since the 2020 version of the Scrum Guide, they’re just called Developers.
So, the question is: could you balance the Scrum Master responsibilities with the responsibilities of your regular job?
It is possible. The Scrum Guide doesn’t explicitly forbid the Scrum Master from having the Developer responsibilities. Not to mention that, on smaller teams and tighter budgets, it seems excessive to have a dedicated person just to facilitate Scrum.
Facilitating Scrum isn’t just about ensuring the Daily Scrum and other events happen on time.
It’s about promoting the Scrum values, resolving conflict, coaching the team members and potentially the other members of the organization to reinforce the Agile culture. This takes both time and energy.
It would get exhausting to do all of the above well while giving your best performance as a Developer.
So, whenever possible, it’s better to have a separate person in the Scrum Master role.
What does a day of a Scrum Master look like?
Here’s a Scrum Master in IT sharing her daily routine.
It’s perfectly fine for a Scrum Master to have their agenda mostly empty.
A Scrum Master observes and listens to pick the cues that something is steering the wrong way. They have the time to quickly respond to emerging situations and to be there for the team members who need them.
Being a good Scrum Master is a challenge, but it’s one well worth taking if your heart is in for it.
It’s a great opportunity to bring positive changes to people and organizations, to take an active part in creative processes that produce value and innovation.