Unlocking Scrum Mastery: Beyond Authority and Power - Discover the essence of effective Scrum leadership without relying on authority. Explore how respect, value, and skill foster team success. Dive in now! 🚀
Enjoy this video? 🔔 Like and subscribe to our channel:
https://www.youtube.com/@nakedAgility
Hello, fellow Scrum enthusiasts! 🌟 I’ve just shared my thoughts on a subject close to my heart: the true role of a Scrum Master. 🔄 In this video, I unravel the philosophy behind Scrum leadership, focusing on influence rather than authority. 🌈 It’s all about creating an effective team environment, driven by respect and skill rather than power. 🛠️ Join me as I delve into this fascinating aspect of Scrum, and let’s explore how we can lead our teams to greater heights! 💪💼
Key Takeaways:
00:00:04 Scrum Master’s Role and Lack of Authority
00:00:24 Accountability in Scrum Roles
00:01:36 Leadership in Scrum
00:02:17 Understanding the Organizational Context
00:03:08 Earning Respect in Scrum Leadership
NKDAgility can help!
These are the kinds of issues that lean-agile practitioners love and most folks hate, and if you find it hard to grasp the subtleties of Scrum leadership without authority, my team at NKDAgility can help you or help you find a consultant, coach, or trainer who can.
If you have issues that are undermining the effectiveness of your value delivery, it’s especially important to find help as soon as you can and not wait!
You can request a free consultation:
https://nkdagility.com/agile-consulting-coaching/
Sign up for one of our upcoming professional Scrum classes:
https://nkdagility.com/training-courses
Because you don’t just need agility, you need Naked Agility.
#ScrumMaster, #ScrumTeam, #Leadership, #TeamEffectiveness, #RespectAndValue
Watch on Youtube
Why isn’t the Scrum Master given any real power or authority in the Scrum Guide? What’s the thinking behind that?
So, but they are. They are given accountability over the effectiveness of the team. In Scrum, the Product Owner isn’t really given any power or authority apart from the accountability for maximising the value of the work done. Right? The developers aren’t given any authority apart from maximising the quality of the product that they’re working with.
So, the Scrum Master has the same type of accountability assigned to them that they need to figure out, without that explicit authority, how to create an environment within which the Scrum team can be as effective as possible.
And that generally is the way that most things happen within organisations. Right? Most things in organisations don’t happen through authority. Authority is used for escalation. Right? Something’s screwed, escalated up, somebody says make this choice. It doesn’t matter if it’s the right one or not, but go this way. Right? That’s that escalation point.
But a Scrum Master is a leader. Right? And leaders, while in some contexts, yes, leaders get authority and they may have authority as well, but people need to choose to follow them. People need to want to do the things that the Scrum Master is suggesting because they’re helping, because people see value in the things that they’re doing.
And that takes real skill. Right? It’s not you as a Scrum Master. You need to understand the processes, practices, and tools. Right? What is it that the teams that you’re working with are actually doing? Right? What’s their context of their technical environment? What’s the context of the business environment? Because you’re going to be helping the Product Owner.
And what’s the context of the organisation as a whole? And figure out how do I increase the effectiveness of the teams going forward.
So, while they don’t necessarily have any real power or authority, they can gain that power and authority through people looking to them for guidance. They’re providing value to people. If you provide value to me, I’m going to listen to the things that you have to say because I’ve listened to you in the past. You provided me with value; I got a success out of it.
Therefore, if I’m unsure or I need more information, I’m going to perhaps come to you because I respect you. I respect your opinion. I respect the information that you have. I respect the value you provide me. And that’s how a Scrum Master makes changes in an organisation.
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.