Technical debt is about doing the system right, not about doing the right system. It is essentially a quantifiable measure of how good the quality of your code is. It does not address functional completeness, nor can it predict success in the market. However, functional completeness might not amount to much if your technical debt is high. Likewise, market success is likely to elude you if you do not pay back your technical debt in a timely manner.
About The Author
Dr. Israel Gat is an expert in Agile and Lean methods, devops, software governance, technical debt and technical due diligence. He served as Cutter Fellow and the Director of the Agile Product Management & Software Engineering Excellence practice from 2008 until 2015, and now splits his time between consulting and writing. Dr. Gat has received many accolades from clients, such as “His approach is the only one I’ve found that actually works… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.