What actually belongs solely to the Development Team in Scrum?
I came across a Scrum question that said the only thing that belongs solely to the Development Team is the Sprint Backlog.
That made me pause.
The Developers create the Increment. They’re accountable for meeting the Definition of Done. Yet apparently the only artifact that strictly “belongs” to them is the Sprint Backlog.
I get the wording nuance, but it raises a bigger question for me.
If Developers own the Increment, does that automatically mean they fully own testing and quality? Or do many teams still treat testing as something adjacent rather than part of Development accountability?
Is this just certification wording, or does it expose how we think about ownership of delivery and quality in practice?
If Developers own the Increment, does that automatically mean they fully own testing and quality?
Yes, the Developers are fully accountable for quality. They are the ones doing the work building the Increment, and if quality was to be cut, they are the ones who would know about it.
Anyone whose labor or industry is needed to have a Done Increment of immediately usable quality is a Developer. That includes whoever is doing the necessary testing.
In Scrum, the Sprint Backlog belongs to the Developers because it represents their plan for the Sprint. They decide how the work will be done. This is an important part of empowerment and motivation in Scrum: the people doing the work make the decisions about that work.
The Increment, however, is an artifact delivered by the Scrum Team and, as I see it, handed over to stakeholders. The team does not retain ownership indefinitely after delivery.
Testing and quality are not separate activities in Scrum. Developers are accountable for producing a Done Increment, which means testing and quality are part of the work. Teams that treat testing as a separate function are often carrying over habits from traditional development models.