When is it most appropriate for a Development Team to change the definition of “Done”?
My question is because some people says that the Definition of Done must change during the Sprint Planning, but the scrum guide says:
"During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of "Done", if appropriate and not in conflict with product or organizational standards."
So I'm agree with the fact that the Definition of Done is defined by The Development Team if the organization don't have one defined, And also believed this must occur in the first Sprint Planning.
I would like to hear what you think about it.
“if the organization don't have one defined, ” ——Definition of Done by Development Team
Thanks Gongyuan Chen, but my question is When is it most appropriate?, In Which Event:
Who says that the Definition of Done must change during the Sprint Planning? Not only have I never heard this anywhere before, but the section of the Scrum Guide that you quoted makes it clear that the Sprint Retrospective is the opportunity to adapt the Definition of Done used by the team.
The only thing that isn't defined is when the Definition of Done is created with respect to the very first Sprint. Having a Definition of Done is used to estimate Product Backlog Items and help the team ensure that what they plan for a Sprint is achievable and realistic. I would suggest that the Definition of Done would need to be established during or at the first Sprint Planning. If the team is refining a backlog before the Sprint Planning, then I would suggest that it would need to be done before any Product Backlog Items are refined.
I agree with Thomas here - to define 'completion' status, the periphery must be appropriated as well. Having shifting goal-posts serves no one, not even the devils advocate who does so. Having a clean and succinct path forward is the way to go - if a team is unclear on the end-goal, the conclusion shall remain elusive and stupefying.