In Scrum, each iteration  - or Sprint - should yield a valuable product increment of release quality, so called Done increment. Understanding what makes an increment truly releasable - and therefore genuinely “Done” - provides transparency over the work a Development Team needs to do to achieve that level of quality.
Why is "Done" so important? Without it, incomplete work would mount up, and without visibility of how much effort truly remains, the debt could quickly get out of hand. Quality will suffer. The magnitude of work which is nearly done, but not really done, can easily overwhelm the team and block the entire development process.
But how do we know when we are done? That is exactly what the "Definition of Done" is all about. "Definition of Done" starts as a simple list of criteria but ideally it should be automated. Readily available tools integrated in the release pipeline can seamlessly measure whether we are done. They can easily execute automated tests, measure code coverage or code complexity, do static analysis, deliver software in test environments and do acceptance testing there and much more.
Based on Azure DevOps pipelines we will show how easy it is to automate the implementation of the Definition of Done. Come to this session to get practical recipes how to effectively fight the technical debt and ensure quality with automated Definition of Done.