A short YouTube talk by Mike Lyons explaining the concept of a "definition of done" (DoD) for software stories. He lists concrete checklist examples (peer review, acceptance/regression/UAT tests, documentation, no increase in technical debt) and emphasizes teams must explicitly agree whether "done" means production release or merely releasable in a lower-level environment.
Definition of done gives us a visible list of all the things that stories need to meet before we'll call them done. So what are some examples of definition of done? Let's take a look at a few here. The story we're working on has been peer reviewed. All of our acceptance tests have passed. Our regression tests have passed. We passed our user acceptance test pass. Documentation is completed. We have not increased our technical debt. Look, it's important for you and your team to know do we mean done is in production? This is a big one. I meet with teams all the time and done is, you know, it's in a lower level environment. Done is, it's being tested. So does done mean software in production or software potentially releasable software in a lower level staging environment? You decide. My point is understand what definition of done is. As a team.
