In software development, technical debt can come in many forms. For instance, a new product was created using a prototype that was never architected after the proof of concept was created. Another example is bugs that had workarounds, but a fix has not been implemented yet. Another issue is that a series of software upgrades need to be implemented, but the team is understaffed. These are only a few examples of technical debt, but all of them create a problem that can haunt a project in the form of risk. How does a project manager dig their way out of technical debt?