Technical Debt should be reserved for cases when people have made a considered decision to adopt a design strategy that isn’t sustainable in the longer term but yields a short-term benefit, such as making a release. The point is that the debt yields value sooner, but needs to be paid off as soon as possible. Martin Fowler

How to fill the table?

• Date: When the debt was added
• Title: A quick description of the debt
• Why debt was added: Link to a document detailing why the debt was added
• Estimated Cost: The estimate of time it will take the team to pay the debt
• Severity: How severe the debt is: Low, Minor, Major, Critical
• Priority: The priority to pay the debt: Low, Medium, High or Immediate
• Status: Where in the workflow the debt is: Unpaid, In Progress, Debt Paid
• Tasks Associated: Links to the tasks to resolve the debt