Technical Debt Prioritization Framework Template
Minimizes future risks and avoids slowing down the development of your software.
Code Knowledge. How are you familiar with the code?
Severity. How it affects the software's functionality or performance?
Dependency and Scale. How many components depend on that part of the code? The scale of impacted software architecture.
Cost of Fixing. How many story points would it cost to fix the technical debt issue?
Total Score = (Knowledge + Severity + Dependency) – 3 * Cost