Is the Scrum Master a disruptive role?

While talking to one of my team during our regular chats, the number of changes Ive challenged the team with came up. I was glad when he said he could see the value in them, but was surprised when he said he initially saw them as a disruption.

The scrum master role is seen as someone protecting the team, i.e. prevent disruptive outside influences from causing internal disruption. So I was initially worried, as thats the opposite of what Im supposed to do!

Before I did anything, I was wise enough to check with the other members to get their take on it. My favourite answer was (emphasis mine):

your job is to push the team and challenge them to do better

I can see that could be taken as disruptive, so I did some digging. I couldnt see much reference to the Scrum Master being a disruption, until I came across this Its quite hard to get the meaning of the presentation from just the slides, but Im taking comfort in the title.

Personal Conclusion

After a fair bit of thinking, Ive come to the conclusion that disruption is as another tool in my belt. As long as I limit its use to when I think the team are stagnating, treading water or could simply do something better, it could be a very useful way to ultimately increase velocity. Importantly, I think as long as I dont expect all of my suggestions to be acted upon and Im more than willing to be told Im wrong, I see no problem with it.

Thats my conclusion, but Id be really interested to hear other opinions in the comments below or catch me on twitter if you prefer.

Comments Section