October 24, 2013
Posted in ScrumMaster and tagged agile, agile adoption, coaching, dysfunctions, scrum, scrummaster.
Pingback: I Killed The ScrumMaster (And Why He Had It Coming) | Tiny Giant Books
Great video, thank you both!
It seems like what you are discussing can be split into two categories:
The skills, behaviors and “mechanical tasks” of a good SM; and the responsibility for leading and influencing organizational change and adoption.
Considering then that the issue raised by Daniel may be more related to terminology and comprehension more than anything else, I would humbly suggest the following improvements to the way Scrum is taught and implemented:
Scrum Mastery, or an ensemble of skills, behaviors and “mechanical tasks” (previously performed by a SM) that are trained and cultivated and for which each team member assumes responsibility, on a rotating basis for the mechanical tasks.
ScrumChampion, or new role with responsibility for leading and influencing organizational change and adoption of Scrum.
These improvements would go in the direction of creating 1/ a receptive culture for implementation of Scrum via the ScrumChampion and 2/ truly self-organizing, continuously-improving teams via the adoption and practice by all team members of the skills, behaviors and mechanical tasks of Scrum Mastery.
Thanks again for sharing your exchange and moving the conversation forward.
Your email address will not be published. Required fields are marked *
Save my name, email, and website in this browser for the next time I comment.
* Copy this password:
* Type or paste password here: