In 30 seconds
- "Developers" covers everyone doing the work: coders, testers, designers, analysts.
- Accountable for the Sprint Backlog, quality and adapting the plan.
- Self-managing: they decide how to do the work.
Who counts
The Scrum Guide uses "Developers" for anyone committed to creating a usable Increment each sprint. It isn't limited to programmers; testers, designers and analysts are Developers too.
Accountabilities
- Creating the plan for the sprint: the Sprint Backlog
- Meeting the Definition of Done
- Adapting the plan daily toward the Sprint Goal
- Holding each other accountable as professionals
Working with the other roles
The Product Owner decides what's most valuable; Developers decide how much fits and how to build it. The Scrum Master helps them work effectively.
Myth vs reality
Myth · Developers means programmers only.
Reality · It includes everyone building the Increment.
Myth · Developers take orders from the Product Owner.
Reality · They negotiate scope and own the how.
Myth · Each Developer owns their own tasks only.
Reality · They share accountability for the Sprint Goal.
The AI angle
Developers spend less time typing and more time specifying, reviewing and integrating. Accountability for the Increment's quality stays with them, whoever wrote the code.
FAQ
How many Developers should a team have?
Scrum suggests a team of 10 or fewer in total.
Can the Product Owner be a Developer?
Possible, but it can blur focus.
Do Developers need to be cross-functional individually?
The team needs all skills, not each person.