Technical Debt: How to Communicate to Teams, Beyond the Tech
summary
Examines six common misconceptions about technical debt—its impact, severity levels, causes, scope, management strategies (not only full rewrites), and shared responsibility—and provides tech leaders and developers concrete arguments to communicate the need to reduce debt to non‑technical teams. Uses examples from software engineering and leadership experience in SaaS for pharma labs, and can be delivered in French or English.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:06CTPO role in communication
- 3:32Origins of unintentional debt
- 5:40Misconceptions on refactoring
- 7:50Debt management via backlog
- 8:32Tech evangelism basics
- 11:16Assessing debt severity
- 12:41Tools for debt control
- 13:44Debt impact on business
- 14:45Debt and business value
- 15:27Collective debt responsibility
- 15:48Code as perishable debt
- 16:30Debt treatment strategies
related talks
28mTechnical Debt: Why it'll ruin your software
57mPutting an end to "technical debt"
25mDemystifying Technical Debt
35mTechnical Debt. A guide for developers and IT managers
45mTechnical Debt: Taking back control when it's already messed up
34mThe Technical Debt Trap
01h 01mThe Technical Debt Prevention Clinic
49mDług techniczny - skryty oprawca organizacji nie tylko technologicznych
