What is the problem?

** Should A Scrum Master Be Technical?! **

I always get this question in my Scrum.org classes, but still, it seems there is no end to the repetition of this question. So, a few months ago, I decided to investigate this question deeply and even build a solution for it.


First, I searched a lot to understand the why behind this question. In fact, there are various reasons for it. 

Imagine you are a Scrum Master without any technical background and you are in a conversation with Developers. They constantly use technical terms but you don’t understand them. Naturally, you experience these feelings:

Feeling lost and confusedFeeling you don’t understand themFeeling that you don’t know what’s going on in the team’s daily workFeeling that Developers don’t accept you as a serious roleFeeling idiotFeeling ignoredFeeling be redundantFeeling unworthy and doubt

All these feelings are destructive and prevent you from being as effective as possible for your team. 

You are not supposed to have deep technical knowledge, but you should understand the general concept of technical terms.

Imagine one of the Developers is saying: 

The Feature branch has been merged with the Main branch. 

But, what does it mean really?!

To understand this routine sentence, do you need deep technical knowledge? Absolutely Not.

You just need to acquire a general understanding of the source control concept. Why the team needs it? What is it? How it works? etc. 

Ask yourself: If you had a basic understanding of source control terms and could immediately imagine the concept on the screen of your mind, would you feel confused anymore?!

We have the same situation with other technical terms as well.


I also searched the Internet about this question. The result is that I found many blog posts and forums. I brought some of them here:










Let me share some of the answers from these blog posts:

“They have to have enough understanding of the technical work the developers do to be able to ask relevant questions and coach the team.”


“I encourage all the Scrum Masters I work with to be as technical as they can comfortably be.”


“Of course a solid awareness of what I’ll broadly call XP practices is essential so I can guide the team to explore these.”


“They do need to have a sound understanding of the agile process and a general understanding of the technicalities of the industry to become successful servant leaders.”


The common denominator of all answers is:

Scrum Masters do not need to have deep and strong technical knowledge, but they should have a basic general understanding of technical terms.


Now another question arises for Scrum Masters:

How can I learn a basic and general understanding of technical terms while I don’t want to go deep into every single term?


I searched a lot to find various answers to this valid question. Unfortunately, I couldn’t find a vivid concrete solution for it. 

What I found was:

Reading books which is time-consuming and usually too deepSearching the Internet / Watching YouTube which is disorganized and of course time-consumingParticipating in technical classes which are usually too technical and expensive

I even went through Udemy which usually offers cheaper courses, but I couldn’t find any course that exactly matched the expectation.


After a lot of investigation, I realized that there was no solution in the market that targeted this specific need.

So, it was the main trigger for me to roll up my sleeves and start building a video course for it. Fortunately, as I used to be a Developer for around 10 years, it was in my ability radar to build such a course.

The result was the course “10 Day Understand Developers”.


More than that, I searched to create a good outline for the course covering all the popular, regular, and routine technical terms.

We have these main categories in the course. In each category, I elaborate on various technical terms:

Day 1: Overall View of Product DevelopmentDay 2: Web TermsDay 3: DatabaseDay 4: Software ArchitectureDay 5: Source ControlDay 6: Programming TermsDay 7: Delivery PipelineDay 8: TestDay 9: Cloud TechnologiesDay 10: Miscellaneous Terms


Now, it is the time to invest in yourself and improve your understanding of the Developers’ world. It has these outcomes for you:

Understand the basics of Developers’ daily language in just 10 daysBecome more effective in serving DevelopersBe accepted by Developers and prevent from being seen as a redundant role

This is the landing page of the course. You can find all the required information about it there:



Just start and level up yourself to understand your Developers’ daily language.

Leave a Reply