
Understanding and Quantifying Technical Debt

#67 - Continuous Architecture (Part 1) - Principles and Essential Activities - Murat Erder
Topic 5 of 9
Published Dec 6, 2021 · Clip 24:55–29:50 (4:56)
Murat defines technical debt as decisions made to get something into production that impact architectural coherence and sustainability, illustrated with legacy data integration interfaces. He discusses paying down debt by maintaining a technical debt log and negotiating with business stakeholders each sprint. On quantification, he admits it's difficult but advocates articulating debt in business terms — e.g., percentage of team effort spent maintaining suboptimal architecture.