As well as all the Responsibilities listed before that in the same document, the Authority “springs mainly from a deep knowledge of Scrum principles and practices”.
I tend to agree that knowledge and experience can help some form of Authority “spring” out. But I will argue that you cannot get this deep knowledge of Scrum principles and practices after 2 days spent in a classroom + a certificate… therefore leaving a lot of newly certified Scrum Master without “authority”.
Isn’t there a need to possess another type of Authority, one that doesn’t depend on some deep knowledge that you may not yet have but wish to gather?
As it happens, I think there is one way to provide new Scrum Masters with the Authority to go and apply what little or more they have learned without fear: this can happen when the belief that failure is part of the natural process of learning exists.
So here is a little mantra you can repeat yourself whenever you are unsure you have that “deep knowledge” but you desperately need a way forward.
- it is ok to fail
- failing fast is the best way to fail
- failures need to be shared and remembered
- it is ok to succeed
- successes need to be shared
- successes need to be celebrated and remembered
- it is ok to ask for help
- it is ok to offer help
- it is not ok to become complacent
- continuous improvement means continuous experimentation
- it is ok to fail
I have shared this with some “new” Scrum Masters over the last few months, some of them have provided some positive feedback and have shared this with other members of their teams. I am now trying to see how this mantra can influence the behaviour of some already well established Scrum Masters that may have become complacent in the area of continuous improvement and experimentation with their teams.
This is of course not only applicable to Scrum Masters. Happy to discuss!