Multiple Scrum Teams mutually define "the definition of done"
The Scrum Guide says -
" If there are multiple Scrum Teams working on the system or product release, the development team on all of the Scrum Teams must mutually define the definition of "Done".
My questions are:
1) Does it mean that there should only be one definition of "Done" for a project / product using Scrum framework and all the teams working for that project/product should adhere to that. If this is the case, wouldn't it be difficult for some of the teams to satisfy all of the criteria of definition of "Done" and for some the portion of increment developed by them would fall short of some required criteria.
2) Is it true to say that definition of "Done" would "specifically" be defined only by the Development team and this would be used by the "entire" Scrum team to assess whether the work on the increment is completed or not.
Thanks.
> wouldn't it be difficult for some of the teams
> to satisfy all of the criteria of definition of
> "Done" and for some the portion of increment
> developed by them would fall short of some required criteria.
What do you think the consequences would be for the release of a product increment, if one or more of the contributing teams did not meet the agreed "Definition of Done"?
2) Is it true to say that definition of "Done" would "specifically" be defined only by the Development team and this would be used by the "entire" Scrum team to assess whether the work on the increment is completed or not.
In my opinion, the DoD should not only be developed by the development team(s) that serve the product, but there should be agreement from the Product Owner as well on what constitutes a "complete" story.
There should also be continuous improvement efforts toward an organizational definition of DoD that all teams are capable of achieving.
Thanks Ian & Timothy !!!
@Ian,
What do you think the consequences would be for the release of a product increment, if one or more of the contributing teams did not meet the agreed "Definition of Done"?
In my understanding the consequences would be not realizing/ obtaining the full potential/benefits of Scrum and increased Technical Debt.
Can we have it this way. Suppose we have a project that has Technical writers team and a team of developers. Now "Spell Check" can be an item in the Definition of Done for the technical writing team but it may not make much of a sense to the Development Team.
My answer to this is they can include "Spell Check" as an item in the common Definition of Done for both the teams and Development team can (as this can not be a item for assessing their work) ignore this in assessment of their PBI..