Technical Debt comes from multiple sources, not just from code written too quickly, but also from natural causes such as a UX paradigm that becomes dated, or an architecture that can no longer support traffic that has grown 10x since its design.

This whitepaper examines the various origins of technical debt, presents how to analyze the burden and risks brought by the various the kinds of debt, and concludes by offering a framework where business and engineering leaders collaborate to prioritize technical debt projects within the product roadmap.