How should 'done' be defined when multiple teams are working on a single product?

Question

Options

• AAll teams must have the same definition of 'done'.
• BEach team must define and use their own definition of 'done'.
• CThe Scrum Master defines when the item is 'done'.

• A
  83% (45)
• B
  11% (6)
• C
  6% (3)

Explanation

When multiple teams contribute to a single product, they must share one unified Definition of Done to ensure consistent quality and a truly integrated, potentially releasable increment - if each team had different standards, the combined product increment could be inconsistent or incomplete. Option B is wrong because separate definitions would create quality gaps and make it impossible to reliably integrate work across teams; the whole point of a shared definition is alignment. Option C is wrong because the Scrum Master does not define "done" - that responsibility belongs to the Developers (with input from the Product Owner and organization), and no single person dictates it unilaterally.

Memory tip: Think of "done" like a shared exit criteria on a group project - everyone on the team must agree on what "finished" looks like, or the final product falls apart. One product = one Definition of Done.

No community discussion yet for this question.