September 28 & 29, 2020 | Virtual
Please login or join to subscribe to this thread
Scrum project management is a methodology for managing software delivery that comes under the broader umbrella of agile project management. It provides a lightweight process framework that embraces iterative and incremental practices, helping organizations deliver working software more frequently.
Why call a role "Scrum Master" if you are not following Scrum? That will create some expectations of ceremonies, artifacts and other roles which won't be applicable.
I'd prefer to go with either XP's "coach" or DAD's "Agile Lead", if you are referring to the role responsible for helping a team become more agile with their delivery practices.
1) Scrum is not a Project management framework. It was defined as a product development framework and although it can be used within a project management methodology like PMBok and PRINCE2, in itself it is not a project management framework. A project is defined by scope, time and busget. Scrum has no process to manage budgets and a very simplistic approach to delivery time-frame.
2) Scrum is no longer software oriented. It can be sued in many other domains.
3) Any framework can be used to deliver working software frequently. Incremental and iterative delivery it is used since 1950s. Scrum doesn't bring anything new in that area.
The topic is probably broader, with a lot of concepts associated with Agile/Scrum that originated somewhere else and are presented as new. Things like kanban, kaizen, user stories, story points, incremental and iterative etc.
The Agile Manifesto stated that "we are uncovering better ways", and my assumption is uncovering means new ways.
I also agree on the terminology, coach seems more appropriate, although I don't mind to use the Change Manager when it comes to enterprise level Agile Transformations.
For me, it is about the function and my philosophy is to use whatever works without worrying about what it is called. So if there are scrum principles that could help in a particular situation and an individual is needed to manage that then yes, the scrum master role can be applied anywhere even if there is no scrum in sight. Or that role can even be performed by an existing one, much like a teacher performs the role of educator but also a facilitator. I believe this is true for any role i.e. the much-asked question about missing BA role in Agile.
I would be very wary about accepting a scrum master position in an organization that wasn't committed to using the scrum framework.
It would be similar to a COBOL programmer taking a job at a company that didn't use COBOL.
I disagree that the Scrum Master role can exist without the Scrum Framework. Of course that you can label a Project Manager (The role that manages scope, budget and time in a project) Scrum Master but I doubt that that's even moral. Have a look at the end of the Scrum Guide and you will see why I believe that "Scrum’s roles, events, artifacts, and rules are immutable and although implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices."
However, from the Agile Manifesto point of view, the BA role is obsolete because the Developers (not coders) should work direct with the end users, How realistic is that, it is another story.
The Scrum Master is a facilitator but not in the sense of Project Coordinator or Business Analyst, otherwise why do you need a new framework? The Scrum Master is defined as a managerial role, the famous "Servant Leader", concept defined in 70's and usually totally misunderstood by Scrum teams.
Please login or join to reply