AgileIndy 2015

This presentation explains how the proper use of a definition of done can help a team to deliver software that really matches the customer needs in the fastest way possible. 
The essence of this is to make use of feedback given by the customer, tests and systems. 

Feedback will help you to improve, learn and reach your goal more effectively. 
Important is to receive feedback quick and many times, iterative development can facilitate this.  Where and what you actually get feedback on is defined in the Definition of Done. 
The Definition of Done defines all steps necessary to deliver an increment of done with the best quality possible at the end of a sprint.  The more you do in your sprint, you more you get feedback on, the more you can improve and learn. 

When demonstrating the software for example every week and implementation is done based on the product owners priority, there is a big change the product owner approves the application even before all requested features are implemented. 

This presentation explains the exact reasons why to use a definition of done and how to implement it in a software development team. It shows how the planning process will improve and how it will keep the product owner posted on what exactly is going on in the team (and not keeping it fuzzy).