Do You Use “Domain Leadership” as a Scrum Master?

What do you do as a Scrum Master when servant leadership no longer gets you anywhere?

There’s a deeply underestimated aspect of the Scrum Master’s role — that of the Domain Leader. Alongside the Servant Leader, it’s one of Scrum’s essential leadership modes — only this one plays offense.

When Servant Leadership Reaches Its Limits

The Domain Leader ensures that the ethical fabric of discussion within — and around — the Scrum Team stays intact.

If, for example, there are recurring problems with disruptive personalities — or even outright saboteurs — this leadership stance steps in. It may mean temporarily excluding people from events or setting clear behavioral conditions that are defined and agreed upon within the team’s domain.

At times, it can even mean removing someone from the team altogether.

As a practical tool, I often use Team Agreements — documents that define shared expectations and, importantly, include the possibility of consequences when those agreements are violated.

Leadership, after all, isn’t just about serving others. Sometimes it’s about protecting the field so the team can grow.

#Scrum #ScrumMaster #Leadership


Find me on:

LinkedIn: https://www.linkedin.com/in/ehauth/ Mastodon: norden.social/@ring2

Me: As a Senior Scrum Master, I lead agile teams to deliver innovative and user-centric digital products and services for the media industry. With over 25 years of work experience in various roles and sectors, I have developed a diverse and versatile skill set that includes Scrumban, Scrum, Facilitation, Product Management, and Project Leadership.

I hold a Certified Scrum Master (CSM) credential from Scrum Alliance and a Facilitator badge. I also write as a columnist for ZEIT ONLINE, sharing my insights and perspectives on topics such as digital transformation, innovation, and culture.