Why Scrum Master is a misleading role?

Sounds awful, the title right? But let me explain.

The other day, together with my fellow Scrum Masters, we were having this discussion. I have two teams that use Kanban as their Framework instead of Scrum, does this mean they don’t need a Scrum Master?

There is a misconception that Kanban is the next level of maturity of a team. After they do Scrum, they become so mature, they evolve to Kanban. That is incorrect.

Kanban is just another framework. Another way for the team to control and visualize how they work and what they are working on. A different way, not a better way.

So this is where the misleading part of the role comes in.

Just because a team does Kanban does it mean they don’t need a Scrum Master?

In my opinion, NO. It doesn’t mean that.

The Scrum Master role goes beyond Scrum. Its main purpose is to be a servant leader. A Coach. Someone that can help the team in their agile journey, being that Scrum, Kanban, XP, etc.

I believe a good Scrum Master should be agnostic of the framework. What do you think?

Cheers,

signature

1 thought on “Why Scrum Master is a misleading role?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

search previous next tag category expand menu location phone mail time cart zoom edit close