The Scrum Master Role is Evolving
The single-specialty role of Scrum Master is evolving into full-stack Scrum Masters who can serve as scrum masters, coach teams, and deliver projects.
Last month I wrote about the term for Scrum Master and how it should be changed. That sparked a number of other conversations, including one with my colleague and agile expert, Al Bayer. We think that the role of the Scrum Master is evolving, and we wondered if others are seeing this as well.
The accountabilities of the Scrum Master are clearly articulated in the Scrum Guide, which also describes the Scrum Team as:
The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies.
The way I read this, you cannot have a Scrum Team without one Scrum Master. Scrum enthusiasts would insist that the Scrum Master role is a dedicated accountability and that each team should have a dedicated Scrum Master. “You wouldn’t have a professional sports team without a coach” is how that line of thinking goes. However, having someone whose role is limited to Scrum Mastering is expensive.
