When many Development Teams are working on a single product, what best describes the definition of “Done”? (Choose the best answer.)

When multiple teams work on a single product, they must have a shared Definition of "Done" to ensure their work can be integrated into a single, valuable, and potentially releasable Increment at the end of the Sprint. If teams have different standards of quality or completeness, the combined result would be fragmented and likely not releasable, creating "undone" work and integration debt. A common Definition of "Done" creates the necessary transparency and shared understanding of quality. Teams may add their own more stringent criteria, but they must all meet the shared baseline.

A. A "hardening Sprint" is an anti-pattern that delays integration and feedback; work should be integrated within the Sprint.
B. This answer is evasive; Scrum provides a clear guideline for this common scenario to ensure integration is successful.
C. Knowing about differences is not enough; incompatible definitions of "Done" prevent the creation of a single, integrated Increment.

1. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide: The Definitive Guide to Scrum: The Rules of the Game. Scrum.org. p. 11. "If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. If there are multiple Scrum Teams working on the product, they must mutually define and comply with the same Definition of Done."

2. Epping, T. (2019). The Professional Product Owner: Leveraging Scrum as a Competitive Advantage. Addison-Wesley Professional. Chapter 7, "The Definition of Done". (Explains that for scaled environments, a shared DoD is non-negotiable for creating an integrated increment).