Unlocking the Scrum Master’s Potential: Embracing Broader Responsibilities for Agile Success

Published on
3 minute read

In my experience teaching the Professional Scrum Master II (PSM2) course, I’ve encountered a recurring theme that resonates deeply with participants: the epiphanies that emerge during our discussions. While there are several insights that attendees gain, the most common epiphany often revolves around the role of the Scrum Master and the broader implications of their responsibilities.

The Scrum Master’s Broader Role

One of the most significant realisations for many is that the Scrum Master is not solely focused on the team. This is a crucial point that, despite being clearly outlined in the Scrum Guide, often gets overlooked. The Scrum Master has accountabilities not just to the team but also to the Product Owner and the organisation as a whole.

  • Understanding Accountability:
    • The Scrum Master must ensure that the team is functioning effectively, but they also need to engage with the organisation to remove impediments and foster an environment conducive to agility.
    • This dual focus can be a game-changer. When Scrum Masters begin to understand their role in the larger organisational context, it opens up new avenues for influence and impact.

Asking the Right Questions

As we delve deeper into these responsibilities, I encourage Scrum Masters to ask difficult questions. This is where the real growth happens.

  • The Power of “Why?”:
    • Often, there are long-standing rules and processes within organisations that may no longer serve their purpose. For instance, I recently explored the historical context of certain practices at the Royal Bank of Scotland, where some rules date back over 200 years.
    • It’s essential to question whether these rules are still relevant today. By challenging the status quo, Scrum Masters can help teams navigate through outdated practices that hinder their progress.

The Meta Epiphany

For those who are also facilitators, there’s an additional layer of insight to be gained. This meta epiphany involves learning how to engage more effectively with people and encourage participation in discussions.

  • Becoming a Two-Dimensional Scrum Master:
    • It’s about expanding beyond the traditional view of Scrum and incorporating additional tools and practices that can enhance team dynamics.
    • By modelling the behaviours they wish to see, Scrum Masters can facilitate meaningful change and foster a culture of collaboration and engagement.

Conclusion

These epiphanies are not just theoretical; they have real-world implications for how we approach our roles as Scrum Masters. By embracing the broader scope of our responsibilities and fostering a culture of inquiry, we can drive significant change within our organisations.

If you found this discussion insightful, I encourage you to engage with me further. Whether you have questions about Scrum, Agile practices, or just want to chat over a virtual coffee, feel free to reach out through Naked Agility. Your journey towards becoming a more effective Scrum Master starts with these conversations, and I’m here to support you every step of the way.

So what is the most common Epiphany in the PSM2 course? I think there’s more than one, and I think it depends on what level you’re playing at when you come into the class, which Epiphany you get.

So probably the biggest Epiphany is the realisation that the Scrum Master is not just focused on the team. That’s the big Epiphany for most folks because I think, even though it’s very explicit in the Scrum Guide, it absolutely states here’s the Scrum Master’s accountability to the team, and here’s the accountability of the Product Owner, and here’s the accountability to the organisation. Most people seem to forget or kind of gloss over that bit for the accountability for the organisation.

When we start kind of double-clicking on that and expanding it and figuring out what the implications are of those accountabilities for how the Scrum Master purports themselves within the organisation, I think it changes that dynamic. It expands those ideas, and they really have that realisation that they perhaps need to be doing more, that they need to be poking at some of those, asking difficult questions. Right? That’s something that I find is very important as a Scrum Master.

Even if all that difficult question is, is why? Right? Something happens a particular way in the organisation that is getting in the way of the team. Why? Right? Because you do find, depending on the organisation, that there can be rules in place that are ancient rules.

I have been doing a little bit of digging recently on the Royal Bank of Scotland, and they have these rules in place for how their teams work. But there are 200-plus-year-old bank rules, right? There are rules in place because they were a great rule 100 years ago for whatever context they were created in. But are they still relevant today? That’s kind of like your organisational package and your organisational craft, and who’s going to take care of that? Who looks at that craft?

So I think that that’s one of the big epiphanies at that level. Then there’s the meta Epiphany in the PSM2 that I think is really important for those people in the room that are also facilitators. So they kind of get a double Epiphany, and that’s how to engage with people and have more people participate in the discussions.

Like, how to become a two-dimensional Scrum Master rather than that one-dimensional of just looking at Scrum. How do I start bringing in additional tools and practices in the way that they do things and demonstrate their own behaviour in order to facilitate change of the people and participation in the events?

Thanks for watching the video. If you enjoyed it, please like, follow, and subscribe. I always reply to comments, and if you want to have a chat about this or anything else Agile, Scrum, or DevOps, then please book a coffee with me through Naked Agility.

Scrum Master People and Process Professional Scrum Agile Frameworks Agile Project Management Scrum Team Agile Transformation Software Development Sociotechnical Systems Agile Leadership

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Slaughter and May Logo
Alignment Healthcare Logo
Emerson Process Management Logo
Milliman Logo
Schlumberger Logo
Bistech Logo
Deliotte Logo
Ericson Logo
YearUp.org Logo
MacDonald Humfrey (Automation) Ltd. Logo
Illumina Logo
Kongsberg Maritime Logo
Freadom Logo
Hubtel Ghana Logo
Capita Secure Information Solutions Ltd Logo
Akaditi Logo
Cognizant Microsoft Business Group (MBG) Logo
Jack Links Logo
Department of Work and Pensions (UK) Logo
Washington Department of Enterprise Services Logo
Ghana Police Service Logo
Washington Department of Transport Logo
Nottingham County Council Logo
Royal Air Force Logo
ALS Life Sciences Logo
Healthgrades Logo
Trayport Logo
Hubtel Ghana Logo
Sage Logo
Microsoft Logo