Have you ever noticed your team making assumptions on what the role of a Scrum Master is that do not align with your vision?
During my Scrum-mastering years, I have seen it many times: teams and organizations have surprising expectations of Scrum Masters that have nothing to do with their actual job.
If you want to know, how to eliminate (or at least reduce) this from the moment you step into a new team, watch this video.
I will share a three step process that will help you set things straight from the get-go. I have learned it the hard way; spare yourself some time and nerve cells by learning from my mistakes.
I am so excited! Big news here today!
New Retrospective Poker cards are finally here. 100 of them, to be exact.
The past couple of months after the end of the Indiegogo campaign, I have been working on improving the design and adding important explanations into the deck.
Now everything you need to run awesome retrospectives with your team is in the box of 44 cards (yes, the number of cards has DOUBLED).
I have prepared a special video where I unbox the cards and show you exactly what's inside. Watch the video to learn more.
Since the number of sets available is limited, I will allow some extra time for my newsletter subscribers to get their copy. So make sure you are subscribed before that.
ScrumMastered.com deserves a vision statement, however small it is right now. I would like to share the first iteration of that vision statement in the image below.
If you have not defined a vision for yourself as a Scrum Master, you should give it a try following the formula above. It was introduced in the book Crossing the Chasm by Geoffrey Moore for product vision.
What is your vision as a Scrum Master?
Share your vision in the comments below.
I get this question sometimes from Scrum Masters who are just starting their journey or want to get into this role. They are worried that they don't have any technical background or don't have a Computer Science degree.
I definitely know where the confusion comes from: quite a lot of companies ask for a Computer Science degree in their job descriptions when hiring Scrum Masters.
In this video I will be talking about my take on this. Do you actually have to be a ex-developer to become a Scrum Master?
The role of a Scrum Master is not about saying what to do, but rather helping agile teams understand it. And, of couse, you need to live up to the ways of work you want the teams to follow. So my question to you is:
How do you live up to your own expectations of agile ways of work?
Leave a comment below and let me know. Being able to lead by example should be a professional skill of a Scrum Master, don't you think?
Collecting some kind of metrics to show the results of your work is important, no doubt in that.
However, in the case of a Scrum Master, that may seem like a daunting task considering the type of work we do.
So how do you go about counting your "coaching points"? (I have just made up that term)
There are actually so many different metrics you can measure as a Scrum Master. You just need to know how to choose them and how to use them!
That is why in today's video I will be sharing some tips on how to make sure your team is on the right track.
The purpose of Sprint Planning is to plan the next sprint by agreeing on the Sprint Goal and creating a plan to achieve that goal. That we know. However, these are not the only topics that should be discussed.
What are the topics that you should cover in a Sprint Planning to help you make it more effective?
Leave your comments below. Let's learn from each other.
Velocity can be a dangerous metric to measure, if the people around you do not understand it's real purpose. It can also quickly get out of hand if you do not stay true to the real purpose of measuring it. I want to hear from you.
What is the real reason for you to measure velocity of your team as a Scrum Master?
Share your thoughts in the comments. Don't be shy, be the first to comment - I am just starting out and need your help to build bigger audience for this website.
There is a lot of talk about what a typical day of a Scrum Master looks like and it is a fair question. Because the role is described in a vague manner in the Scrum Guide, it is important to have a detailed responsibilities list to understand it sometimes.
(thank goodness, I have created such a list in my Action Plan for Scrum Masters that I sure hope you have downloaded already. And if you haven't - what are you doing??? - go sign up for the newsletter and download it!)
However, as we dive deeper into daily tasks of a Scrum Master, we can get distracted and start doing too much. Yes, it actually can be a real problem in this role.
It might sound unusual, but great Scrum Masters have a list of things they should actively avoid doing if they want to be successful in helping their teams become more Agile.
In today's short video I will talk about crucial mistakes that can prevent your team from succeeding with Agile and how to avoid them.
While coaching is an important part of the Scrum Master role, it is not always the answer to all your challenges.
Now I want to know your thoughts. Share your story in the comments below:
Tell about a time when coaching did not work for you. Either when you were coached or you were coaching someone. Why do you think that really happened?
Let's learn from each other by sharing our experiences.