Development team now called Developers
The 2020 version of the Scrum Guide changed the name of the Development team role to Developers. I understand the logic of the change that we want to avoid having a team within a team. But I still struggle with the word 'Developers' since, for me, it too closely aligns with IT and people programming. Every time I give a scrum training, I have to spend time explaining the meaning of this term, which tells me there is a problem.
I'm going to try using the term 'Product developers' and see how this goes. What are other viewpoints on this role naming?
But I still struggle with the word 'Developers' since, for me, it too closely aligns with IT and people programming. Every time I give a scrum training, I have to spend time explaining the meaning of this term, which tells me there is a problem.
If it provokes students into reconsidering Done, and the comprehensive skills a team needs to genuinely achieve it, I'd be inclined to think of it as a solution.
Ian, from a non-IT perspective the term "developer" is usually either understood as a name for a software programmer or for a company building real estate. I do not see the connection between "developer" and "done" just by the name only. A more descriptive term with which non-IT folks could probably identify more easily would be "doer": A doer is doing something until it is done. And who doesn't want to be a doer? ;)
A more descriptive term with which non-IT folks could probably identify more easily would be "doer": A doer is doing something until it is done. And who doesn't want to be a doer? ;)
One of the most dysfunctional "Daily Scrums" I have witnessed had 20 in attendance. There were half a dozen Developers. The balance was made up of various mid-tier managers and assorted hangers-on, all of whom quite clearly saw themselves as "doers". They were convinced of it.
The collaboration of these "doers" would indeed have been helpful in achieving Done, had they spared it at any time other than in those 15 minutes, which were for the Developers to refocus on the Sprint Goal. None of those other "doers" shared in that commitment.
This is from the opening section of the Scrum Guide circa 2020
As Scrum’s use spreads, developers, researchers, analysts, scientists, and other specialists do the work. We use the word “developers” in Scrum not to exclude, but to simplify. If you get value from Scrum, consider yourself included.
If you are teaching Scrum to a group of individuals that are not related to software I suggest that you are free to use a more relevant term but make it clear that when they read the Scrum Guide or any literature associated to Scrum, that they will see many references to the word Developer as the individual(s) that are involved in doing the technical work associated to producing the product. I honestly think that replacing "developers" with "doers" would cause more confusion as @Ian Mitchell's example shows. Having experienced similar situations, "doers" definitely doesn't seem right.
Don't get too caught in the symantics. Focus on the message and purpose. I think that taking the time to explain is good. It shows that the participants are paying attention, want to learn and are willing to ask questions. Sounds like a great opportunity to instill some of the Scrum Values.