Scrum Masters expanding from Scrum

"Scrum Master" refers to a set of accountabilities on a Scrum Team. There's no reason why someone who is fulfilling those accountabilities for a team cannot know Kanban or other methods or frameworks and incorporate those into a team using Scrum. However, if the team decides that Scrum is no longer appropriate, then perhaps they should consider a different name for the role. If the person is knowledgeable about a number of different agile frameworks, then perhaps "Agile Coach" is a good name.

There is some talk and a trend in my country about Scrum  Masters taking on more frameworks with their teams such as Kanban. What should be call ourselves if that is the case?

From what you describe a Scrum Master would have work to do. Any such decisions ought to be clearly understood and made by the team.

Thank you for your insights, I will explore these with my teams.

Luke

Depends on the Agile framework:

- if I'm working primarily with the Scrum framework, I'm the Scrum Master,

- if I'm working primarily with the Kanban framework, I'm the (Kanban) Service Delivery Manager,

- if I'm working primarily with the DSDM framework, I'm the DSDM Coach,

- if I'm working primarily with the eXtreme Programming framework, I'm the XP Instructor,

and

- if I'm working with several (minimum 3) frameworks, I'm the Agile Coach.



AND the most important thing to remember is that the title doesn't matter at all,

I've hold the title of Scrum Master in companies where there was only Kanban with XP.

It really doesn't matter so long you know, understand and can teach/coach/mentor under the Agile framework that has been implemented at your client's company.