Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint.
Developer is the generic term for a team member who is ‘developing’ the solution that achieves the Sprint Goal. It applies regardless of whether the Scrum Team is a marketing team, software team, HR team, or even data management and reporting team.
The specific skills needed by the Developers are often broad and will vary with the domain of work.
However, the Developers are always accountable for:
Each Developer is expected to work collaboratively with other Developers to deliver the Sprint Goal, rather than work only in their capability silos and only do work that directly reflects their capability area.
Rather than say “I’m a part of the test team”, a Developer with test capability would say “I’m part of the Scrum Team”.
Developers are expected to help get work to Done before they take on new work into the Sprint.
The temptation is when, for example, software development tasks are done, to then start on new work before other work has reached Done. Developers are expected to work to the mantra “start finishing and stop starting”.
Developers aren’t expected to:
Developers are expected to:
1. Sutherland, J. and Schwaber, K. (2020) The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.