When the Scrum Master Role is Set Up to Be an Anti-Pattern
If you’ve never experienced what a good Scrum Master does for a team, it’s easy to misunderstand the role as being administrative: scheduling team meetings, taking notes on impediments, nagging people to update the status of things. When that happens, it’s natural for decision makers to feel that the role of Scrum Master is not a real job, and therefore decide not to invest time or money into it. At that point, one of several anti-patterns typically happens. Here are the ones I see most often:
