The Scrum Master Should NOT BE A DEVELOPER

But…we’ve always done it this way!

Photo by Specna Arms on Unsplash

Some might say that Agile has revolutionised software development, and with that change in thinking across the industry (it is reported that 95% of respondents to the State of Agile Report practice Agile development methods) it makes sense that there are many Scrum Masters around.

In Scrum teams where we have the following roles

• Scrum Master
• Product Owner
• Development Team

we notice that the Scrum Master isn’t automatically a member of the development team. What is going on?

First let us explore the elephant in the room:

What is the role of the Scrum Master?

A Scrum Master needs to deal with the changing priorities of a dynamic software project. This can come about because of poorly drafted and recorded requirements, and the business asking for changes in priority from the team.