ScrumMaster, Get off Your High Horse
30 September 2013
Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.
Contrary to popular belief, ScrumMasters don't have it easy. Facilitation is not as simple as it is made out to be, especially when members of the team are either novices and/or haughty. Additionally, there are many proverbial "headless chickens" running around making noise. ScrumMasters face an uphill task in mentoring and guiding prospective Agilists to follow Scrum rules and best practices.
More often than not, the snide remarks come from people who are the least knowledgeable about Agile principles, discipline, methods, practices, roles, and responsibilities. Unfortunately, there is no shortage of such people or groups in the corporate world. When ScrumMasters attempt to explain the concept of Agile and self-organized teams (and in the process also explain the role of management in an Agile environment), they are faced with comments such as, "ScrumMaster, get off your high horse." It is in this context that I write this article.
I had the interesting experience of joining a project as ScrumMaster. On the very first day I discovered, to my dismay, that I was the only member of the team at the time. I was tasked with forming a team of Agile experts when there were none available. The organization I worked for had very little Agile history. Needless to say, it took me more than a month to get people with some exposure to Agile principles and practices. Coaching the team was not the difficult part; the team was enthusiastic and eager to start practicing Agile. The challenge was more from middle management -- line managers, project managers, and program managers. No one had any clue about what Agile truly was, and even less knowledge about roles and responsibilities. The team was expected to deliver from Day One, without giving the members a chance to go through the team-forming life cycle.
The ScrumMaster's role is extremely challenging until such time as the team becomes self-organized and all the stakeholders reach the same level of understanding of Agile best practices, roles, and responsibilities. The situational leadership role ScrumMasters find themselves in demands that they remain steadfast and help eliminate any noise that could potentially distract the team from performing at its best toward the sprint goal. While this may seem like an easy effort, the truth is quite to the contrary. To become a barrier between the Scrum team and any distracting influence from the management, marketing, and other nonessential stakeholders is a full-time responsibility for the ScrumMaster. It is, most of the time, difficult and laden with organizational politics. Ensuring that the Scrum process is used as intended is one challenge. Other challenges include educating/coaching and mentoring stakeholders on the concepts of Agile/Scrum; enforcing the rules of Scrum; timeboxing daily stand-up meetings into 10 to 15 minutes; steering discussions toward increased productivity; mediating through conflicts; facilitating meetings such as sprint planning, retrospectives, and reviews; keeping the team motivated; and helping team and the stakeholders maintain transparency. These are just a few of the challenges faced by all ScrumMasters.
A major impediment to the ScrumMaster role that I have seen and experienced is the expectation that ScrumMaster also perform as a project manager. This is a perfect recipe for disaster. In my opinion, the mind-sets of these two roles are totally different and so will result in project failure. Another expectation that is common in global consulting organizations is that ScrumMasters also perform marketing duties and explore business opportunities for growth. This leads to severe problems and often ends up with disbanded teams. Additionally, it could cost organizations future business with their clients.
ScrumMasters are required to be resistant to all such ridiculous expectations, remain persistent in ensuring that the rules of Scrum are followed, and be dedicated in their efforts to remove impediments to the ability of the team to deliver the sprint goal. ScrumMasters must make sure that all stakeholders have an awareness of the rules. Only then can there be improvement. Bringing awareness of Agile and Scrum to management, marketing, and other stakeholders is a tough task for any ScrumMaster.
So, does the ScrumMaster need to get off his or her high horse?
Not if organizations wish to be successful in their pursuit of Agile excellence.
Current rating: 4.7 (7 ratings)
The community welcomes feedback that is constructive and supportive, in the spirit of better understanding and implementation of Scrum.