There are two sides to mastery: the good and the ugly.
The good side of mastery is something to strive for: be a perfectionist, dedicate yourself to a task, do something to be proud of.
But mastery is a whole different thing for those who think they know (or are) better. This sort of “mastery” begets narrow-mindedness and petty rigidity.
Knowing enough to think you are right, but not knowing enough to know you are wrong.”
—Neil deGrasse Tyson
And so in the spirit of Agile, a movement that promotes diversity and inclusion, there is a small step you can take: if you use the “Scrum Master” title, retire it. You can always go for “agility lead” (together with “product lead” and “engineering lead”) or come up with something creative that reinforces your own culture and organizational structure. You won’t be the first to do it and you may find it wasn’t such a small step after all.
Retire your Scrum Master title.
Scrum Master or not, no one should impose methods on teams, because there is no one best way to do anything. Process is of secondary importance.
The central thing is to create an environment where teams are free to pursue and perfect what makes sense to them—be it Scrum (a good place to start) or better.
