Scrum Master

A Scrum Master is a specific role within the Scrum framework of Agile software development. The role is designed as a "servant-leader" responsible for promoting and supporting Scrum by helping everyone understand its theory, practices, rules, and values. Unlike a traditional project manager, a Scrum Master does not manage the people but rather coaches the team and removes impediments to progress. The term was coined in the 1990s by Ken Schwaber and Jeff Sutherland, drawing the word "Scrum" from a rugby formation and appending "Master" to denote someone who has achieved mastery over the process, similar to the usage in guild terminology (e.g., a master craftsman).

Usage of the term has become a subject of debate within the technology sector as part of a broader movement to adopt more inclusive language. Critics argue that the word "master" carries heavy historical trauma associated with slavery and systemic racism, and that removing it helps create a more welcoming environment, regardless of the term's etymological intent in this specific context. Proponents of the term argue that it describes a level of proficiency and authority over a framework rather than authority over human beings, distinct from the "master/slave" technical metaphor which has been more universally rejected. While the official Scrum Guide retains the title, some organizations have proactively shifted to alternative titles to avoid potential alienation.

Example:
"Our Scrum Master facilitated the retrospective to help the team identify bottlenecks in the last sprint."

Example:
"To improve team cohesion, the company decided to rename the Scrum Master role to 'Team Coach.'"