Thank you all for the discussion here. I feel the topic is closed now.
There seems to be a misunderstanding. This "delivery team" as mentioned above, does program and test and create marketing initiatives and trainings and ... whatever is necessary to produce regularly a potentially shipable product increment according to their DoD. I do understand that you and Jeff mean all this with the term "development".
You introduced new role names like Scrum Master and Product Owner to clearly identify these new roles. The role "developer" is already loaded. And I often see - due to a long time of referring to "programmers" as developers - that this causes some confusion. Thus, people don't feel included when we speak about the Development Team though they also contribute to the successful creation of the product increment. Therefore I wrote this proposal.
I learned by now that the term "delivery team" is also loaded and negatively conotated and thus neither appropriate. An alternative mentioned in the discussion below is "Product Development Team". Others are also mentioned.
My hope with this proposal is that the adoption of Scrum is simplified and accepted equally by all members of the Scrum Team.
I like such group discussions. I overlooked that a "Delivery Team" exists in some organizations (with a "Delivery Manager"), meaning a special team that kicks out the software (thank you, Alasdair for pointing that out to me). In this case this would add to confusion rather than reducing it.
@Anonymous: regarding the downvote, maybe that can be raised with another proposal. I would even vote for that. And could you please elaborate, what I should consider in this case to raise my understanding. I found some aspects of this discussion far more helpful than your (general) comment. I'm happy to learn...
And the number of votes as well as the discussion here indicate to me that there is a problem with the term "Development Team" to some. So how could we adapt this proposal to make it more valuable and to address the bigger picture?
Mike, I see your point that the "Uses of Scrum" section tries to add clarity of what "develop" and "development" means through examples and the last sentence. Though "development = programming" is (to me) a piece of complex work already.
And the Scrum Guide says: "The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of "Done" product at the end of each Sprint." Here I read that "Development" is defined as "delivering" - to me that makes even more the case for "Delivery Team". When reading the comments I see the limits of this term too and there seems to be some desire to change the term. Thus, I wouldn't say this is "completed".
PS: This suggestion seems also related to "Slightly change the Scrum Roles definitions to avoid newcomer confusion" => https://scrumguide.uservoice.com/forums/241958-general/suggestions/31757773-slightly-change-the-scrum-roles-definitions-to-avo
I also like the term "Product Team" and the point by Mikkel that "Delivery" can be part of the DoD.
And I can also see the point by Stefan that in the worst case "you delivery what I (PO) order" could be inferred.
team is ok for me - (squad, unit or force might also apply, a crew I associate with a service group) - any specific term from software development I'd like to avoid, like development or build - even delivery could be too specific yet. Good, question, Andrew, what name could it be? What do they do? They accomplish something, they achieve something, they create something, ... what else?
Btw, to goole for "a group of people achieving something" yields f.e.:
Force sounds nice too - "may The Force be with you" :-)Ralph Miarka shared this idea ·
82 votesRalph Miarka supported this idea ·