Definition of "Done" - Multiple teams
I found two sentences that seem a bit contradictory. (pg 18)
Any help on what I might be missing?
- When a Product Backlog item or an Increment is described as “Done”, everyone must understand what “Done” means. Although this may vary significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency.
- If there are multiple Scrum Teams working on the system or product release, the Development Teams on all the Scrum Teams must mutually define the definition of “Done.”
Using your first quote I point out this part.
- When a Product Backlog item or an Increment is described as “Done”, everyone must understand what “Done” means. Although this may vary significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency.
I emphasized two parts. I'm also adding in a part of the paragraph from which you pulled your second quote
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.
So the DoD is applied at the increment level. Everyone working on that increment must understand when it is "Done". So if you have more than one team working on the same increment, they must share a DoD. If all teams are working on separate increments, different DoDs are necessary.
A common practice that I have used and seen when having a joint DoD is to allow each team to add more stringent requirements to their own DoD should they choose but they are not to remove any item in the joint DoD. This sort of follows this statement where the guide is talking about an organizational DoD.
If the definition of "Done" for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum.
That is my interpretation and I'm sure that others will have somewhat different ones or other ways to explain it. I look forward to theirs as much as you do.
Unlike the first statement, the second says nothing about multiple Scrum Teams working on the system or product release. If they have no consequent need to integrate their work, then the Definition of Done may indeed vary significantly per Scrum Team.
Apologies, I should have said it's the first statement that says nothing about multiple Scrum Teams working on the system or product release
Thanks guys. I think I was focusing too much on the wrong part of the sentences. This clears it up for me.
Which Scrum Guide says seems me oppositely in DOD section:
"Although this may vary significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency".
and
"If there are multiple Scrum Teams working on the system or product release, the Development Teams on all the Scrum Teams must mutually define the definition of “Done."