Who is responsible for creation of DoD?

What are your current thoughts about the best answer, bearing in mind what you may have read in the Scrum Guide?

The Development Team is responsible for creation of DoD.

I believe its the collaborate effort of the Scrum team. However, in the Scrum guide, it mentions - "If the Definition of done for an increment is part of the convention or guidelinenes , all Scrum teams must follow it. If done for an increment is not a convention of the development organization, the Development team must define a definition of done"

Trying to really understand what that sentence exactly means.
And the answer to the questions: -

1) Who creates the DoD?
2) Who is responsible for Dod?

Are 1 & 2 the same?

Scrum Teams can be part of large organizations which have a stake in the quality of the products being developed. An agile team isn't necessarily garage startups, and they can have a duty to parent organuzations in terms of quality, risk control and observing strategic direction.

Hence the first place to go for a Definition of Done ought to be the organization itself. It may have standards that need to be observed with regard to branding, legislation, contractual conditions or any number of other factors. A team may augment that standard with their own criteria.

Scrum team is responsible for creating of DoD

Posted By Upendra Srivastava on 19 Jan 2017 07:36 PM
Scrum team is responsible for creating of DoD

Sorry, but I don't agree:
' If "done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of “done” appropriate for the product.'

Unless this question on Open Assessment point it has correct for Dev Team, the Scrum Guide refers:

"If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product."

For me make sense to be a Scrum Team responsibility instead Dev Team, since the PO have the responsibility for the final product.

Le Guide Scrum 2020 est clair à ce sujet en page 13 version Française:

• Soit la Definition on Done pour un incrément fait partie des standards de l'organisation, dans ce cas toutes les Scrum team doivent la suivre,
• Soit s'il ne s'agit pas d'une norme de l'organisation, la Scrum Team (Product Owner, Scrum Master et développeurs) doit créer une Definition of Done approprié pour le produi.

Answer is Development Team.

Scrum Guide says as follow,

"The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint"

I believe this has changed with the 2020 Scrum Guide. It now clearly states that the DoD is the responsibility of the whole Scrum Team: 

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. 

Defining Done ought to be collaborative. There is a duty of care to others, and the requisite level of quality must be understood along with the ability of the Developers to meet it:

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.

The Developers are required to conform to the Definition of Done.

Making sure that Done is achieved is the specific accountability of the Developers. They are the ones doing the development work and hence only they are in a position to assure it:

the Developers are always accountable for:

---

• Instilling quality by adhering to a Definition of Done;

Organization who is sponsoring Scrum does it. If they don't do it, then Scrum team. Read the "Definition of Done" section of the Scrum guide.

Instead of asking who is responsible for DoD, it is worth asking who needs it and for what?

I believe the Scrum Team needs it to be able to communicate what it means for the Increment to be Done. So, that they can transparently inspect it with the stakeholders. Thus if there is no Definition of Done provided they need to establish it. 

Jacek Markiewicz, that is all fine but the devil is in the details. And it's good to know that between the latest version of the Scrum guide and the previous one, the DoD responsibility has changed. This is important to know when passing the test as it good make a pass or fail difference. 

This is important to know when passing the test as it good make a pass or fail difference. 

While this is true, is passing the test the only reason you would want to know this?  What others are saying is that if you will be working in an organization that is using Scrum, it is better to know the importance of the Definition of Done.  

On that note, I will point out that the Scrum Guide does not say the Scrum Team can not further refine the organizational Definition of Done.  It states (emphasis by me)

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.

I have been in organizations that have defined a minimal set of conditions that all teams would follow (all code reviewed, passes all tests, etc) but then each team would add additional conditions to enhance the definition for their individual products or team agreements.