Filipus Tian please share it so we can bust this myth.

You have to avoid excessive focus on documentation. The backlog itself replaces most of it. Most forms of documentation that exist on traditional projects create a lot of overhead and provide little value in the end.

Kevin M Packard agree. There should be discussion on what documentation that should be in the Definition of Done. Highly regulated industry might need more documentations.

@@keinlanz It is good to distinguish specification from documentation. Specification is written prior to development, the functional designs, technical designs, etc. of old. This is mostly replaced by the product backlog. As soon as something is finished, it is removed from the product backlog along with any specifications written for it. Documentation is written during or after the fact. It describes the product, what its features are and how to maintain it. This is not replaced by the product backlog. There may have been many PBIs relating to one and the same feature, as time progresses and further feedback is received. One cannot expect a customer or even a developer to dig through archived PBIs to see what was done when.

Tell that to scrum masters, not developers.

Thanks for watching it @Maria 🙏

Thank you for your support Rafael Issao Miyagawa 🙏

Thank you. :)

Thank you Ilham Cahya Suherman. Will put it in my Vlog backlog.

Thank you Michael. Much appreciated 🙏

Scrum Express thanks for stopping by 🙏😊

Glad you liked it!!

Thank you @Ridwan. Glad you enjoy it!

Joshua Partogi anytime

You are most welcome.

Thanks for the appreciation Mike. I am glad you found it helpful. There are several musics in this video. Which one are you referring? :)

@@scrummasterinblack I liked them all really! Just a fan of electronica in general!

Hi Lorenzo. Thanks for the feedback. As you can see I made this video before the Scrum Guide 2020 was published. I agree with you there. :)

Hi George. What product are your Scrum team developing? We can go from there. Scrum is all about product not project.

*Scrum Guide 2020* : _The Developers are required to conform to the Definition of Done._ So yes, ensuring the increment meets the Definition of Done is the developers _responsibility_

@@scrummasterinblack I agree with that, but I wouldn't agree with what you state in the video: "The Development Team owns the Definition of Done". I think it's the entire Scrum Team's responsibility.

@@Lorenzo-ek9is good point. I made this video before Scrum Guide 2020 was released. In Scrum Guide 2020 it's now the whole Scrum team responsibility. It looks I need to make a new video on DoD :)