Why is the DOD a "transparency artifact"

Last post 08:44 pm October 14, 2016
by Ian Mitchell
1 reply
Author
Messages
06:52 am October 14, 2016

hi

I' m wondering why the DOD is not listed as a regular scrum artifact, but listed separately as a "transparency artifact" in the scrum guide.

Transparency (together with inspection and adaption) is rooted into the ceremonies and artifacts, since empiricism is the foundation for Scrum. I.e. the sprint backlog provides transparency, the backlog contributes to transparency, etc. I have trouble in understanding the need for a separate "transparency artifact".

I have experienced that every word in the scrum guide has been carefully chosen, so placing the DOD outside of the regular list of artifacts will have a good reason. I need some help in understanding why.

Any idea on this is much appreciated.

thanks
roland flemm

08:44 pm October 14, 2016

> I' m wondering why the DOD is not listed as a regular scrum artifact,
> but listed separately as a "transparency artifact" in the scrum guide.

It isn't listed as a "transparency artifact". It's described in a section about artifact transparency. That isn't the same thing. A Definition of Done can be said to *facilitate* artifact transparency, but is not an artifact itself.

For example, with a DoD:
- The work remaining in Product and Sprint Backlogs is better understood and can be better estimated
- The Increment can be released with an assurance of a certain level of quality.

> ...every word in the scrum guide has been carefully chosen...

Correct.