Technical debt is a necessary evil. Too much of it can kill your velocity, but none at all is an indication that you’re over-engineering your system, especially in the early stages. The trick is to use technical debt smartly to move faster and get user feedback. Then you will have the information that you need to decide whether to close the debt or dump the functionality.
What You Can Expect To Learn In This Whitepaper
- What technical debt really means
- The pros and cons of technical debt
- Breakdown technical debt metrics
- How to divide technical debt into the right categories to increase efficiency