A shared Definition of Done is one quality standard that every Scrum Team on the same product agrees on and follows. The Scrum Guide 2020 says that when multiple Scrum Teams work on a product, they must mutually define and comply with the same Definition of Done. Without it, no one can trust the combined Increment. The Professional Scrum Master I (PSM I) assessment tests this rule with options that look like team autonomy. Last verified: October 2026.
Why the shared Definition of Done matters on PSM I
The rule checks whether you understand what the Definition of Done is for: transparency. The PSM I has 80 questions in 60 minutes with an 85% passing score, according to the Scrum.org PSM I page.
| PSM I fact | Value |
|---|---|
| Questions | 80 |
| Time | 60 minutes |
| Passing score | 85% |
| Fee | USD 200 per attempt |
How the Scrum Guide 2020 defines a shared Definition of Done
The Scrum Guide 2020 describes the Definition of Done as the commitment for the Increment. It is a formal description of the state of the Increment when it meets the quality measures required for the product. Three rules follow, all in the "Commitment: Definition of Done" part of the Increment section:
- Organizational standard first. If the organization has a Definition of Done for increments, all Scrum Teams must follow it as a minimum.
- Otherwise, the Scrum Team creates it. If there is no organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. The Scrum Team includes the Product Owner, the Scrum Master and the Developers.
- Multiple teams, one standard. In the guide's words, they "must mutually define and comply with the same Definition of Done."
The Developers are required to conform to the Definition of Done. Work that does not meet it is not part of the Increment.
The Nexus Guide (January 2021) adds detail for scaled Scrum. In a Nexus, the Nexus Integration Team is responsible for a Definition of Done that applies to the Integrated Increment. Individual teams may apply a stricter Definition of Done, but they cannot use weaker criteria than the shared one. Nexus is not core PSM I content, but it explains the logic.
Worked example: three teams, one checkout
Three Scrum Teams build one e-commerce app. Team A owns the cart, Team B owns payments, and Team C owns delivery options. Each team wrote its own Definition of Done in its first Sprint.
- Team A requires automated regression tests and a security scan.
- Team B requires code review but no regression tests.
- Team C requires deployment to a staging environment.
At the end of the Sprint, all three teams say their work is done. Then the combined checkout fails: payment changes broke the cart, and no standard asked for end-to-end tests.
The fix is to agree on one Definition of Done for the product. It includes integration and regression tests across all three areas. Team A may keep its extra security scan, because a stricter team standard does not conflict with the shared one.
Why each wrong option fails
The LinkedIn question asked how three Scrum Teams on the same product should handle the Definition of Done.
| Option | Verdict | Why |
|---|---|---|
| A) Each team creates its own Definition of Done independently | Wrong | Independent definitions produce Increments that may not integrate. |
| B) All teams mutually define and comply with the same Definition of Done | Correct | This is the Scrum Guide rule for multiple teams on one product. |
| C) The Product Owner defines it for all teams | Wrong | The Scrum Team creates it, or the organization sets a minimum. It is not a Product Owner decision. |
| D) Teams relax it when integration gets difficult | Wrong | The Definition of Done is a commitment. Lowering it under pressure hides problems. |
Option C is the subtle trap: the Product Owner is accountable for value, so candidates assume the Product Owner also sets quality. The guide gives that to the Scrum Team and the organization.
What practitioners say about a shared Definition of Done
- In a Scrum.org forum thread on Done for multiple Scrum Teams, Ian Mitchell wrote in 2018 that teams on one product "must observe a common Definition of Done which qualifies the releasability" of each integrated Increment.
- In a 2026 forum thread on organizational and product definitions, one reply said all teams on a product must meet the same standard, and none can be less strict than another. Ian Mitchell added that company standards are the first place to look.
- The LeSS framework page on Definition of Done describes one product-level definition agreed between the teams and the Product Owner, which teams that can do more may extend.
Common misconceptions about the Definition of Done
- "Self-managing teams each choose their own Definition of Done." Self-management works inside the shared standard, not instead of it.
- "The Definition of Done is the same as acceptance criteria." Acceptance criteria are specific to one item. The Definition of Done applies to every item. Our article on Definition of Done vs Definition of Ready covers the difference.
- "The Scrum Master writes the Definition of Done." The Scrum Master can coach teams on it, but the Scrum Team creates it.
Practice Questions
Question 1
Three Scrum Teams work on the same product. How should the Definition of Done be handled?
A) Each team creates its own Definition of Done independently B) All teams must mutually define and comply with the same Definition of Done C) The Product Owner defines the Definition of Done for all teams D) Teams may relax the Definition of Done when integration gets difficult
Answer: B. The Scrum Guide requires one mutually defined Definition of Done for teams working on the same product.
Question 2
Your organization has a company-wide Definition of Done. Your Scrum Team wants stronger security checks. What is true?
A) The team must use the company definition exactly as written B) The team must follow the company definition as a minimum and may add to it C) The team can replace the company definition with its own D) Only the Scrum Master can change the company definition
Answer: B. An organizational Definition of Done is a minimum for all Scrum Teams.
Question 3
No organizational standard exists. Who creates the Definition of Done for a single Scrum Team?
A) The Product Owner B) The Scrum Master C) The Scrum Team D) The stakeholders
Answer: C. Without an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.
Related topics
- Definition of Done vs Definition of Ready
- SAFe, LeSS and DAD: scaling Agile
- Technical debt, which grows fast when the Definition of Done is weak
- Scrum Guide 2020 at six: what the PSM exam still tests
- Practise Definition of Done questions in the PSM I exam simulator.
FAQ
Can different Scrum Teams have different Definitions of Done?
Yes, if they work on different products. If they work on the same product, the Scrum Guide 2020 says they must mutually define and comply with the same Definition of Done.
Who owns the Definition of Done in Scrum?
If the organization has a standard, all Scrum Teams follow it as a minimum. Otherwise, the Scrum Team creates a Definition of Done appropriate for the product. The Developers must conform to it.
Can one team add stricter criteria to a shared Definition of Done?
The Nexus Guide allows teams to apply a more stringent Definition of Done within their own team. They cannot apply less rigorous criteria than the shared standard.
Is the Nexus Guide part of the PSM I exam?
PSM I is based on the Scrum Guide 2020. The multi-team Definition of Done rule comes from the Scrum Guide itself, so you can answer those questions without Nexus.