What Is The Definition of Done 📜 In Scrum | How Is It Different To Acceptance Criteria
ฝัง
- เผยแพร่เมื่อ 15 ก.ย. 2024
- As more and more companies are implementing Scrum, there are more failed Scrum implementations. And every time I come into these kind of organisations, one of the common issue is lacking of technical excellence in the Definition of Done.
This video explains how the Definition of Done is the most important aspect of Scrum that should not be neglected by organisations implementing Scrum.
If you would like to explore more about Scrum, join one of my Live Virtual official Scrum.org classes: www.scrum.org/j...
If you found this video or any other videos on my channel valuable, buy me a cup of coffee from here: www.buymeacoff...
Thank you for your continuous support.
#Scrum #TechnicalExcellence #DevOps
The Definition of "Done" is a critical aspect of Scrum. However, many people who are new to Scrum thought that the Definition of "Done" is the same as Acceptance Criteria.
Finally, someone mentioned documentation is also important. Doing Scrum doesn't mean we don't need documentation.
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.
04:22 to bookmark for my knowledge:
What a simple and effective way to demonstrate the Sprint Backlog -> Product Backlog OR Completed Increment process via the DoD checklist.
As always, I appreciate how you simplified things when explaining them in your videos.
Thanks!
Thanks for watching it @Maria 🙏
As always, great video. Thanks for it! 😁 Suggestion for the next video: The importance of Sprint Goal
Thank you Ilham Cahya Suherman. Will put it in my Vlog backlog.
Congrats for the 1k subs. And thank you for another great video!
Thank you for your support Rafael Issao Miyagawa 🙏
Nice video Joshua! For me Definition of done is a set of minimum standards defined by a team for the work being done for an specific product. While the acceptance criteria is a special checklist created for each story, so the team knows when the expectations will be covered. Stay safe!
Scrum Express thanks for stopping by 🙏😊
Short. Clear. Excellent!
Thank you. :)
Hey Joshua, thanks for sharing!
Nice video! Like the emphasis on governance and documentation. I've subscribed.
Thank you Michael. Much appreciated 🙏
Great video coach!! Especially for my refreshment 😂
Glad you liked it!!
just found ur channel.. and this is the first video i watch. great content..
Thank you @Ridwan. Glad you enjoy it!
Joshua Partogi anytime
Nice concise video - this made me re-examine the way we incorporate both AC and DoD.
P.S. I'm a fan of the music - any chance you could point out what it is?
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!
At 2:04, more than attribute they call the DoD the commitment for the Increment.
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. :)
Keep making such amazing Scrum videos,can you also make a video on Definition of Ready
Thanks for the vedio
You are most welcome.
Where can I find ideas about 'definition of done' for projects outside of software development?
Hi George. What product are your Scrum team developing? We can go from there. Scrum is all about product not project.
The DoD is the responsibility of the entire Scrum Team, not only the Developers. It would be quite strange not to include the PO's perspective on what he/she considers done.
*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 :)