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 as 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 therefore the possibility that a developer is a Scrum Master or a Scrum Master is a developer is not denied. At the same time, it should be clear that this is not the optimal state - more on that below.

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

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 focus of the Scrum Developer is on the technical implementation of the customer’s 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.

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 software developer is also trained accordingly or has mastered the Scrum Guide and, ideally, has already gained external coaching experience. In addition, this role would also need a lot of time to fill both roles - that will be difficult.

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.

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.

If you really have no other option than to fill the Scrum Master role with a “part-time” software developer, then our Echometer tool will be of great help to you - it was developed, among other things, for this challenge: “Part-time” Scrum Masters become professional team coaches in a time-efficient manner thanks to 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 repurpose a software developer into a part-time Scrum Master, at least try Echometer to maximize the probability of success.

Christian Heidemeyer, Psychologist & Scrum Master

Can a Scrum Master be part of the development team? The dual function “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 he navigates skillfully between the two roles. And that is likely to be very difficult in practice, so it is generally discouraged. If there is no other way, then let tools like Echometer help you.

Therefore, again the note: If you would like to try out how it feels to develop your team with our tool: You can start an agile retrospective without logging in, in this case the “Keep, Stop, Start” workshop. 

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