There's usually room for improving the definition of "Done". A good definition will let less
technical debt pass on to the next Sprints.Technical debt is minor shortcomings in the code that
makes it less than "good enough" and therefore creates risks in the future. It usually decreases
velocity in the future (because the team has to fix the shortcomings) and as some of the debt might
remain in the final product, the maintenance cost will increase as well.Another Agile way of
reducing technical debt is continuous refactoring.