Evolution of the Scrum Master Role: From Facilitator to COO
“Capital One Financial Corp. cut the “agile” group within its technology department this week [...] affecting 1,100 employees…” - WSJ
“We struggled to see the value of the Scrum Master role. The type of people in the role didn’t understand the business. They were prescriptive about Scrum rather than practical about the business.” - Scrum Inc. Health Industry Client
“Scrum Masters are being treated like team admins.” - Scrum Inc. Tech Industry Client
“Leadership is asking: what are we paying these people for?” - Scrum Inc. Manufacturing Industry Client
These industry patterns along with general industry sentiments expressed across social media platforms challenging the function of the Scrum Master role highlight how misunderstood the Scrum Master role really is. A role that can significantly improve operational effectiveness has somehow been boxed into an outside facilitator role, and thought of as someone who does not/should not have the power to influence the strategic direction of a team let alone an organization. This raises a crucial question - how did a role designed to be so instrumental in team and organizational success become so misunderstood and limited in its impact??
Before we look at the why, it is important to understand that the Scrum Master role has always been designed to be a leadership role - a true leader who serves and a change agent accountable for enabling a highly effective delivery engine both at the team and organization level that delivers value to the customer at a rapid pace. A Scrum Master has a holistic system view, with the scale of the role indicating the increasing perimeter of the view, ensuring:
When we combine this understanding with the need for this role in a complex adaptive system, we know that it requires an inherent investment in the organization's success and future, which does not come from a purely facilitative positioning. So what then is the problem, and how did we end up in a place where companies are laying off Agile roles, especially Scrum Masters, in droves?
Earlier this year, Scrum Inc. hosted our semi-annual Agile Transformation Community of Practice (CoP) and we invited the global transformation leaders in attendance to discuss their thoughts on this challenge. There was widespread concern among these leaders that the Scrum Master role’s potential is not being maximized. Here is a summary of the major issues they shared as the reasons:
领英推荐
The answers these leaders shared match closely with the patterns we have observed as part of our consulting work at Scrum Inc. , patterns that we are actively working to change so that organizations can harness the true power of this role. Increasingly we understand that the evolution of the role’s positioning from a facilitator to COO, someone responsible for operational effectiveness, is in fact a matter of understanding the design of the role, enabling the competency, and changing the mindset as well as the environment. More tactically, to enable the potential of the Scrum Master role, this is what we recommend organizations and Scrum Masters start doing? today to address the concerns highlighted above:
As Organizations:
As Scrum Masters:
Ultimately, as with any Agile role, it is not about doing agile; it is about being agile. By understanding and embodying the above capabilities, Scrum Masters can play a significant role in driving value and contributing to the long-term success of their organizations, fulfilling the intended purpose and true potential of the role.
So now the question becomes how do we create the competencies needed to drive the potential of the role, integrating the agile and non-agile skills, to enable the empowerment needed for the role to succeed? Join me, Preetinder (Preeti) Pugatch , in an upcoming LinkedIn Live conversation with Enterprise Agile Consultants James Edmondson and Shaun Thompson as we explore this topic further. Here is a teaser:?
“We might equate the Scrum Master’s development to Maslow's hierarchy of needs. At the bottom, shelter, food and warmth we can equate this to the very basic accountabilities of what we expect a Scrum Master to be able to support a team with. But for a team to be truly effective they require a Scrum Master who can operate at the top of Maslow's hierarchy: self-actualization (Shu-ha-ri). But to get there, they need to develop along two pillars 1. Competence (agile and non agile) and 2. Clarity of purpose (self, team, and org) (see David Marquet’s pillars for intent based leadership). So the question for organizations is how do you enable Scrum Masters to rise to the top of the pyramid and be truly empowered to release the full effectiveness of a team?”
In the meantime, check out our Scrum Master and Scrum Master@Scale courses where we bring in real life scenarios and case studies from our consulting experience to complement the theory and show practical application of both agile and non-agile skills to drive organizational success. Our courses are taught by industry experts and are specifically designed to enable students to start implementing improved ways of working immediately. Join us and let’s change the way the world works, together.
UX Design Leader
2 个月Thanks for the deep reflection. It's giving me a lot of empathy because all of this discussion can apply to UX Design as well, if you substitute "user centered product development" for "agile", especially on these points: - the argument about whether Agile/Scrum (Design/Design Thinking) is the right name vs. is it the right process - the resulting devaluation in the eyes of business leaders due to lack of clarity and alignment on exactly what the value is and how it is achieved - the need for well-rounded, highly competent leaders to identify the need for a process, start from a shared baseline, and customize it for the context is more important than whether they start from an agile perspective or a waterfall one (or from a design-driven process vs an eng- or product-driven one).
?????? Tomek ?????? & Agile Coach @ Bosch Digital_ ??
2 个月As an organizational agile coach or SM you should be part of the leadership team by default. But earning the acceptance to be seen, trusted and valued as a leader needs time. With time you develop hard (domain) and soft skills. These will be the basis for your potential success in that role. Certificates, 1-5 day trainings on all the agile methodologies, toolings etc. are fine. But not mandatory for success. Experience, domain- , business- and orga-knowledge are crucial. Let’s say it metaphorically: - you need to understand the smell of the place BEFORE you can create / change the smell to be even better ?? Another aspect is definitely the right choice of people for that role. I would not recommend to leave a fresher in that role alongside with veteran dev, ops or business teams or even managers… Junior SMs need guidance, mentoring and experienced senior SMs around to be able to grow and develop in good way.
Agile Coaching | Scrum Master | Software Development Management | Agile Training | Team Coaching | People Management |
4 个月It is typical for organizations that don’t understand Agile, to not understand the value a good scrummaster brings. That may never get it. I sound like an old timer but this is true. The paradigm shift from command and control to self organizing teams needs to continue to be promoted and desired. This brings the high performing teams and the best job and environment ever worked in!
Scrum Master en John Deere
4 个月the new era for SM is here!
Agile Coach & Business Analyst
4 个月I will add my voice to those highlighting the 2-day Scrum Master certification as a core of the problem. Imagine how a team would view a developer who attended a 2-day course to become a developer, and then was added to the team. I'm exaggerating a little to make a point. I've wondered if it wouldn't be better if the prerequisites for the Scrum Master role were something like process engineering degree plus organizational management and deep people skills. Thinking out loud here, but the rigor of a discipline like engineering might increase the respect for the role. One other thing I have also wondered about is the name of the role. For those outside of software development teams, it sounds odd. "Scrum Master? Is that like a Dungeons and Dragons thing?" :) Good topic... !!