image (1)

Can a developer be a Scrum Master? A few Pros and Cons

Agile teams are the backbone of modern project development. But the question remains: Can a developer also be an effective scrum master? Or the other way around: Can a scrum master also be a developer? Some team leads are concerned with these considerations. In this article, we try to answer the question and highlight three advantages and disadvantages of this dual role.

To give you a brief answer in advance: In the agile world, there are rarely clear "yes" or "no" answers. The dual role of Scrum Master and Scrum Developer can be successful if the person knows the challenges and consciously juggles the roles. The Scrum Guide itself does not give a direct answer to this question, and in this respect the possibility of a developer being a Scrum Master or a Scrum Master being a developer is not denied. At the same time, it should be clear that this does not correspond to the optimal state – more on this below.

Let's start by briefly defining the roles we are talking about here.

Can a developer be a Scrum Master | Scrum Developer

Scrum Developer vs. Scrum Master

Because roles are very important in Scrum. In this respect, the clarification of "Scrum Developer vs. Scrum Master" is important: the Scrum Master focuses on process optimization and removes obstacles for the development team. In contrast, the Scrum Developer focuses on the technical implementation of customer requirements.

Both roles complement each other and it is crucial to respect the boundaries between them in order to maintain balance in the agile team. So can a Scrum Developer also be a Scrum Master, or a Scrum Master Developer? Before we answer that, one more advantage of combining the two roles.

Can a developer be a Scrum Master | Scrum Developer

Advantage: Use Agile synergies

One example of the positive side of this combination lies in a software developer's deep understanding of the processes in an agile environment. A developer scrum master can better optimize development processes because he has internalized both the needs of the team and the agile principles. This understanding enables a seamless integration of Scrum practices and values into the development cycle.

The prerequisite for this is, of course, that this developer is also appropriately trained or has mastered the Scrum Guide and, at best, has already gained external coaching experience. In addition, this role would also need a lot of time to fulfill both roles – that will be difficult.

Can a Scrum Master be a developer, or a developer be a Scrum Master? In short, it would work, but can lead to disorganization.

Can a developer be a Scrum Master | Scrum Developer

Disadvantage: Lack of objectivity

On the flip side, however, is the potential loss of objective perspective. A developer scrum master may not be able to maintain the necessary distance during code reviews to provide unbiased feedback. The dual function harbors the risk of overlooking important aspects that a neutral scrum master could better grasp.

The second disadvantage already mentioned, which may have an even greater impact: objectively speaking, there is not enough time in most agile software projects to effectively fulfill both roles, scrum master and software developer, in parallel. Some responsibilities will suffer in any case. And there are even more disadvantages.

Can a developer be a Scrum Master | Scrum Developer

Disadvantage: leaving your own bubble

One potential risk that a developer scrum master could face is the danger of being trapped in their own technical bubble. Due to the close connection to development, social and interpersonal challenges in the team could be overlooked. 

However, the role of the Scrum Master requires an empathetic and attentive attitude towards the individual needs of the team members. It is important to consciously step out of the technical perspective and also consider the human aspects. After all, the agile manifesto emphasizes collaboration and the individual more than processes and tools – a reminder that looking beyond the code is just as important as the technical aspects.

So, can a Scrum Master be part of the development team or not? To summarize, yes, it is possible, but it is not recommended.

"Many team members are afraid to speak up!"

"We discover too many unexpected issues & bugs at a late stage!"

"Why does it sometimes take me hours to prepare a simple retrospective?"

Woman_pm
You lead an agile team and...
📊... want to impress with clear metrics on your teams agiliity?
⏱️... lack the time to prepare great agile retrospectives?
You should try Echometer.

Can a developer be a Scrum Master | Scrum Developer

One solution: digital coaching support

If you really have no other option than to fill the Scrum Master role with a "part-time" developer, then our tool Echometer will help you a lot – it was developed for this challenge, among others: "part-time" Scrum Masters become a professional team coach in a time-efficient way with our simple tool.

Echometer is a digital tool that helps agile team leads with agile retrospectives and team Health Checks. Whether remote, hybrid or on-site: it makes team coaching measurable and professionalizes your work while saving you a lot of work. Just take a look at our website to find out more: www.echometerapp.com.

"If you really have no other option than to convert a software developer to a part-time Scrum Master, at least try Echometer to maximize the probability of success."

Can a software developer be a Scrum Master | Scrum Developer

Conclusion - Developers as Scrum Masters

Can a Scrum Master be part of the development team? The dual role of "developer scrum master" opens up opportunities for synergies, but requires clear role definitions to avoid potential disadvantages. An agile scrum master with a developer background can bridge the gap between technology and teamwork, provided that they navigate skillfully between the two roles. And this is precisely what is likely to be very difficult in practice, so it tends to be discouraged. If there is no other way, then let tools like Echometer help you.

Finally, another quick hint: If you would like to know how it feels to develop your team with our tool: You can start an agile retrospective below without logging in, in this case the "Keep, Stop, Start" workshop. 

Alternatively, simply forward our website to the responsible colleagues: www.echometerapp.com.

Open Feedback Questions

Continue: What should we keep?

Stop: What should we stop doing?

Start: What should we start doing?

Share this article in your network

Need a team boost? Do this: The Spotify Health Check Retrospective!

First Health question: "😍 We love going to work, and have great fun working together."

Sounds good? Try our retro tool for free below.

Articles you may also be interested in

Echometer Newsletter

Don't miss any updates on Echometer & get inspiration for agile working