Done, Cancellation and Multiple Teams
This chapter draws together a few points that often trip up candidates: what the Definition of Done really provides, who may cancel a Sprint, and how several Scrum Teams work on one product.
The value of the Definition of Done
The Definition of Done describes the state an Increment must reach to be considered complete and usable. Meeting it creates shared transparency about quality; if a Product Backlog item does not meet it, it is not released or presented as done.
Cancelling a Sprint
Only the Product Owner has the authority to cancel a Sprint, which may occur if the Sprint Goal becomes obsolete. Cancellations are rare; any completed and done work is reviewed and the remaining items are returned to the Product Backlog.
Multiple teams on one product
When several Scrum Teams work on the same product, they share one Product Goal, one Product Backlog and one Product Owner, preserving a single transparent view. They should also share a common Definition of Done so their Increments integrate.