Wouldn't it be fair to say that in a healthy Scrum practice, if you have experienced Scrum teams that are truly self-empowered and self-managed, they will learn early on in their careers the things that the team needs (from Scrum Masters, no doubt), and will come to do those things on their own - with less need for a Scrum Master on a regular basis - over the long haul? In other words, wouldn't it perhaps be worthwhile for Scrum teams to work towards reduced need for dedicated Scrum Mastering as they mature?
There are a lot of "ifs" in there. In my experience it is a rare team that meets all those criteria. Teams may be able to grow into it, but that takes time. At that point a ScrumMaster would not be as focused inwardly on the team, but externally toward the organization trying to create change that would enable even better results from the team. I still don't see it as a job that ever ends when ScrumMaster is a properly empowered and respected role.
Wouldn't it be fair to say that in a healthy Scrum practice, if you have experienced Scrum teams that are truly self-empowered and self-managed, they will learn early on in their careers the things that the team needs (from Scrum Masters, no doubt), and will come to do those things on their own - with less need for a Scrum Master on a regular basis - over the long haul? In other words, wouldn't it perhaps be worthwhile for Scrum teams to work towards reduced need for dedicated Scrum Mastering as they mature?
There are a lot of "ifs" in there. In my experience it is a rare team that meets all those criteria. Teams may be able to grow into it, but that takes time. At that point a ScrumMaster would not be as focused inwardly on the team, but externally toward the organization trying to create change that would enable even better results from the team. I still don't see it as a job that ever ends when ScrumMaster is a properly empowered and respected role.
@@AgileForAll Well-said. I like that.