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.