DoD

It would be more correct to say that the work actioned by a Development Team must conform with the team's Definition of Done in order for the associated increment to be considered release-ready.

DoD is created by a collaborative effort of the Scrum Team including the Development Team. Scrum Team owns the DoD

The quote from the Scrum Guide:

"Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the definition of “Done” for the Scrum Team and is used to assess when work is complete on the product Increment"

> Scrum Team owns the DoD

I agree, but we need to be careful here. When forming a Definition of Done, the Scrum Guide says a team must consider the "conventions, standards, or guidelines of the development organization". Also, "If there are multiple Scrum Teams working on the system or product release, the developer teams on all of the Scrum Teams must mutually define the definition of 'Done'."

I interpret this as follows. A Scrum Team will wholly own its Definition of Done, but that does not obviate its duty of care towards the organizational attainment of consistent release quality.

The Definition of Done evolves as the team evolves in its Scrum journey. In other words as a team matures it can introduce more stringent criteria into its Definition of Done.

For eg. A Build verification test might become mandatory once a team has a well defined environment to execute the tests. Then the DoD can be extended to include this test as well.

In humorous terms if a team completes a feature which meets the team's DoD it can go on a vacation provided the PO comes along

Thanks All,

From the discussion above , I interpret Scrum team conforms the Definition of Done