 Hi, I'm Geoff Watts, and this Lightbulb talk is about the definition of done. Agile approaches focus on iterative and incremental delivery of value, and the definition of done is critical in enabling this. There are two important aspects to the definition of done. In order for an increment of work to be deliverable within an iteration, all aspects of the product development life cycle need to be contained within the definition of done. In a software delivery, this means that design, development, testing, integration, documentation, user experience, and probably many others are all part of done. If my product with a publication of a book, then content, illustrations, spell check, grammar, pagination, etc. would be part of my definition of done. This is important in order for our customer to be able to potentially deploy something of real value at the end of the iteration. It's also important because by trying to get something done, we'll find whatever issues there are with the various aspects of our development life cycle. For example, if we have problems with testing, but we don't test until six months from now, then we're delaying our ability to fix the problems in testing. Whereas if we test for each feature now, then we can identify and rectify issues now. Our definition of done will also define our quality benchmark. This could be the depth of testing, the levels of performance or speed, and even the number of browsers we're compatible with. If my product was a landscape garden, my level of quality might be the number of weeds visible, or the evenness of the law, or the definition of the edging. These lightbulb talks have a definition of done as well, including title, the script being reviewed and edited, a consistent introduction, the audio with low ambient noise, noise equalization, and volume of plus six decibels, a time limit of three minutes plus or minus 10 seconds, the animation and the alignment of the audio to the video, the text in the animation being spellchained, a thumbnail image being published to YouTube and added to the playlist. Regardless of your product, bring together the cross-functional team and collaboratively identify all of the tasks required to bring one valuable feature from idea to completion. Then as we mature as a team or our product focus changes, we may need to inspect and adapt our definition of done over time. I hope this lightbulb talk has been useful in helping you understand what we mean when we say done.