Technical debt is any shortcoming in the solution that makes it less than 'good enough' and might create problems in the future. When there's a lot of technical debt, the velocity might decrease in the future because developers have to
deal with the shortcomings. On the other hand, this debt might even remain in the final product and make it harder and more expensive to maintain the product. Refactoring is a common way of reducing technical debt. It's when the code
is improved without changing its external behavior. It's a good idea to Agile teams to spend some of their capacity on continuous refactoring. Improving the definition of 'Done' is the second way of reducing technical debt.