Scrum roles in theory and practice
Scrum.org has advertised for a developer: http://t.co/wCGdhBtTkZ
The advertisement says:
"The role of the full stack web developer and technical team lead is pivotal to the execution of Scrum.org’s vision of improving the profession of Software Development"
Now, while the Scrum Guide acknowledges that "Individual Development Team members may have specialized skills and areas of focus" it does make the following point quite clear:
"Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule"
It might be unfortunately construed that, by advertising for the "role" of "full stack web developer" and "technical team lead", scrum.org is making an exception in its own case. Could someone from the organization please comment on the thinking here?
I don’t think this would be a problem.
This is an advertisement of Scrum.org, an organization, rather than one of a Scrum team.
At first:
“This role is responsible for building out a long term technical strategy for scrum.org, managing a team of people delivering on that vision and working with 3rd parties to both deliver Scrum.org’s properties and also connect to other 3rd parties.”
The "Role" is a job role, seems like a technical management role, not a Scrum role.
Secondly:
Image that, if a Job Description just said that we need several developers as follows:
One Developer with coding skill
One Developer with media design skill
One Developer with …
I think this is uncommon for people to recognize.
It usually be described as:
One Web Developer
One UI Designer
Per my experiencs, event hough there are no titles for Development Team members other than Developer, they always have special titles in their organization and have functional title printed on their name cards.
Who says the site scrum.org is developed using Scrum? ;)
It seems natural, but maybe they use a different framework.
Yes!
Who know?
:)