Ever since Scrum became widely adopted in the early 2000’s, discussions have arisen whether the Scrum Team consists of programmers, designers, or other titles specific to the needed skills. Should they be called out by title, or is this a cross-functional team?
With the arrival of Dev/Ops, a surge of opinion pushed that Developer team should be replaced with Delivery team, especially for non-software development (like marketing). Yet, from a Scrum user’s (Product Owner?) point of view they are everyone and anyone necessary to research, develop, deliver, and sustain the increment.
This has unearthed strong opinions. Unfortunately, they don’e converge on a single word or phrase.
A Developer is on the Scrum Team … we have listened to discussions about where this leaves the architect, tester, infrastructure setup, and other non-programmers required to “create” a “Done” increment.
We decided this is one of the changes that Scrum requires. All team members work to convert product backlog into a Done increment. Not just programmers, everyone who”s skills, temperaments, and background helps.
1. Does a Developer also deliver software, particularly if “Done” calls for it to be live when delivered. Or can a Developer only Develop?
2. As Scrum has moved to areas such as AI, autonomous intelligence, robotics, material science such as carbonate, advanced hardware development in the quantum space … the skills of the people that are needed to convert PBI’s to increments changes radically. We have to build on software development knowledge to do this.
3. If a Delivery team also develops what it is delivering, is it still a delivery team?
Should we employ Develop/Delivery to include all possibilities that we are aware of, or what suggestions do you have? The name should be all inclusive.
Regardless of the final choice (if change occurs), I’m sure that a sizable minority will not be satisfied. They need to study the Scrum values more to reach an appropriate conclusions.