Scrum Master

Scrum Masters are servant leaders who help teams use Scrum effectively. They facilitate ceremonies, remove impediments, shield the team from distractions, and coach team members toward self-organization and continuous improvement.

Unlike traditional managers, Scrum Masters have no authority over team members. They lead by influence, not command. Their success is measured by the team's success—high-performing, engaged teams that deliver value consistently.

A great Scrum Master makes themselves increasingly unnecessary. Their goal is to build team capabilities so the team can eventually manage itself. This doesn't mean the role disappears—it evolves toward coaching and organizational improvement.

1986: Hirotaka Takeuchi and Ikujiro Nonaka published "The New New Product Development Game" in Harvard Business Review, describing a rugby-like approach to development. The term "scrum" came from this.

1995: Jeff Sutherland and Ken Schwaber formalized Scrum, presenting it at OOPSLA. The Scrum Master role was defined as part of the framework.

2001: The Agile Manifesto was signed. Scrum became the most popular Agile framework, and Scrum Master became a recognized profession.

2010s: Certifications proliferated (CSM, PSM). Scaled frameworks like SAFe expanded the role. Debate emerged about "full-time" Scrum Masters vs. shared roles.

2020s: The 2020 Scrum Guide update emphasized servant leadership and anti-patterns. The role continues evolving as Agile matures.