Should I have One Definition of Done? With Eric Landes

In this episode, Eric Landes addresses a question he received while training: “Should we have more than one ‘Definition of Done?’”

If you are interested in attending Scrum training, check out our public Scrum training courses. 

Key Takeaways:

This week, let's talk about the Definition of Done. In one of our classes, we had a question about the Definition of Done. Specifically, how many Definitions of Done can a Scrum Team have? So, I went to the Scrum Guide, and here is what that says:

"The moment a Product Backlog item meets the Definition of Done, an Increment is born."

The guide does not say it meets the sprints Definition of Done or the potentially shippable definition of done. Instead, it states, "the Definition of Done," implying, in my mind, that there is one Definition of Done.

In class, we discussed whether there should be a definition of done for releases, for instance. When some organizations release the software, users need to be trained. Marketing materials might need updating, etc. And I understand that these things need to happen.

Having one DoD would reduce friction for releasing. No waiting for another team to complete work. The Scrum team controls when they can release. High-maturity teams and organizations are designed this way.

But not all organizations are in a place where we can have the Scrum team do everything necessary for release. So the team may have to grow into it. That is ok. Remember where you are headed and make improvements every sprint to put everything necessary for done into your definition.

Related to this Episode:

A complete list of the current Scrum Training by AgileThought.

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!