are you a connector or a hand-holder?


21-12-2024

Hey Reader,

I sat down with Ryan from Australia for an episode of the Agile Audit podcast last year. Yes, this is how long it takes me to get a video out these days...

Anyway, we had an awesome discussion, and as I was rewatching it to get the episode ready, I got some new insights and inspirations.

One of the topics we delved into was the role of a Scrum Master as a connector or a glue of sorts.

Since our jobs bring results that can only really be seen long-term and are difficult to connect to our jobs directly, it sometimes feels like we have to validate our existence. And that often results in trying to show tangible results.

This often results in us taking over decision-making, being a bit too forceful and facilitating every discussion, providing reports. Or in simple terms - hand-holding.

What I also enjoyed during this discussion with Ryan was our thoughts on how to show value to the stakeholders and also the team. In the end, they are our biggest promoters - when they see the positive improvements we bring, we don't need to prove anything anymore.

Ryan shared his stories of what that value looks like and how to recognize it.

We also touched on an interesting question: should a Scrum Master have any formal authority in the organization? A tricky question, isn't it?

I think it's a leadership role, but not one that needs official power. It's about guiding the team rather than being in charge. Transitioning to this self-organization approach can be a challenge for some teams, as people may have a tendency to rely on the Scrum Master for too long.

In my experience, making team agreements explicit can help. By involving the team in creating these agreements, everyone understands what's expected. This prevents misunderstandings and helps the team stay within the Agile framework.

Overall, the Scrum Master should focus on guiding and empowering the team, rather than having formal authority. It's about creating an environment where the team can thrive and take ownership of their work.

We discussed even more topics with Ryan during the episode, so check it out for more insights and ideas.

Keep learning with our wiki!

I had a lot of material just kind of sitting there without purpose. Some of it I originally created for the teams I worked with to help them understand Scrum. I made it into a set of wiki pages that I would usually copy-paste into the team's documentation space.

And I was a bit sad to have all of this material just sitting there and only being useful to a handful of people.

So I decided to transform it into my own Wiki space on ScrumMastered website. I started filling in some additional articles and I plan on adding more as I discover new interesting topics.

Let's connect!

Thank you for reading. I hope you learned something new! Cheers,

Update your preferences or Unsubscribe here

Looking for more guidance?

  1. Book a coaching call and join my mentorship - work with me one-on-one
  2. Sign up for the online course Fundamentals of Agile to become an Agile expert (and an Agile Coach)
  3. Find a guide to your next workshop or a new practice to implement in your team
  4. Watch my YouTube videos for free for even more insights and advice

Btw, if you want to sponsor this newsletter, you can get more information here.

You received this email because you have subscribed to the newsletter at ScrumMastered.com, made a purchase in ScrumMastered store, or joined the Mastering Scrum community.

11720350 Canada Inc. o/a ScrumMastered, 10 Wellesley Place, M4Y 1B1, Toronto

Daria Bagina

I help professionals and organizations build awesome teams with the help of Agile and Scrum practices. I provide highly actionable tools and systems that bring you results. Professional Scrum Trainer | Experienced Agile Coach

Read more from Daria Bagina

21-12-2024 Hey Reader, I've got a new video for you. Yes, I sent you an email last week about this topic already since I posted it in a blog post. BUT... I updated the text and included so much more information in it to give you even more actionable steps to take to improve your meetings. And I also have filmed a video for you 🎥. Writing an attendee story One of the things that I added a ton about is the attendee story, or really, how to write a better more useless agenda for your meetings. I...

21-12-2024 Hey Reader, "The are too many meetings is Scrum". Or so many people say. But in reality, whether you use Scrum or not, you probably have too many meetings. There are a few things that you can implement to immediately free up your calendar and focus on what's really important. To help you with that, I wrote up a blog post. In summary, I bring you 5 rules to follow to avoid useless meetings: A meeting can only happen if it has a clear purpose. No preparation means no meeting. The...

21-12-2024 Hey Reader, Today I wanted to talk to you about a topic that has been on my radar for the last several months. And the more I look into it, the more I want to discuss it. Luckily, I got a chance to deep-dive into this topic with Mark Metze during the recording of a podcast episode for Agile Within. The topic is "how much technical knowledge do you need to be a successful Scrum Master (or Agile Leader in general)". I'm sharing a part of that podcast with my answers to Mark's...