Definition of Done for many Scrum teams

> What do you propose we should do to harmonize the DoDs?

A Definition of Done properly applies to the increment. Are the teams collaborating to jointly provide a fully integrated, tested, and usable increment to the Product Owner each and every Sprint?

All the Teams Product Increments at the end of each of their Sprints go in the same code base for one product release. There is often some collaboration required between the Teams to achieve this. Until now, each Team has its own DoD. The question is: who works with the Product Owner to create a unified DoD? Some of the Team members (Developers) or the Scrum Masters?

The Nexus Guide says:

"The Nexus Integration Team is responsible for a definition of “Done” that can be applied to the Integrated Increment developed each Sprint."

What does the Nexus Guide say about how a Nexus Integration Team is formed?

That is a great tip to check up the Nexus guide. It's possibly what we need: a Nexus Integration Team. Other than a PO and a SM, the Team members are skilled individuals that can coach and guide the other Scrum Teams to properly integrate all the work to a Definition of Done.

Once the Nexus Team DoD is defined, other Scrum Team "may choose to apply a more stringent definition of “Done” within their own teams, but cannot apply less rigorous criteria than agreed for the Increment."

I'll share that with my colleagues. The challenge is that basic Scrum is not yet fully in place, so we need to achieve a solid base before we move to a Nexus...

Thanks!

I like the second and then each team can add but not subtract from the overall product DoD. I also like the idea if possible to get all the teams together in space if possible to review the DoD and review/make any tweaks so everyone can hear the discussion and feel ownership in the product DoD. May have to be creative in facilitation so the discussion is focused.

While it is logical for each scrum team to have their own DoD which is in conformance to the type/nature of work being done by the team and forecast of PBI.

Multiple scrum teams working on the same product/project and using product backlog - DoD across all teams must be aligned to ensure that final outcome/deliverable is a working increment and potentially ship-able.

In Nexus the DOD is or can be, reviewed ( SCRUM style ), along with other improvement opportunities, in the individual SCRUM teams' Sprint Retrospectives.

The Nexus Integration Team's Sprint Retrospective is almost mandated to ask some specific questions, addressing Technical Debt, work un-finished, integration, and frequent deployments to minimise dependencies. "Work left undone" would be a good forum to review the DOD perhaps.

So there are two "layers" in Nexus Sprint Retrospective, where the DOD can be harmonized/aligned.

Pat