I'd like to share with you a story: an engineer who became a Scrum Master because one was needed, and then became a better Scrum Master because one was needed. I am very curious what my fellow Scrummers think of my perspectives.
Two years ago I was hired as a developer in an “ops-y” pipeline team. Although the team was convinced it was Scrumming, it had apparently bought into a common myth: “Scrum is a set of best practices and you cherry-pick from it what is relevant to your work environment.” The team had (most notably):
- Not seen its Scrum Master in months.