Please enable JavaScript.
Coggle requires JavaScript to display documents.
Technical Debt - Coggle Diagram
Technical Debt
Design Debt
Parallel development
Delayed refactoring
Poor technology leadership
Lack of ownership
Lack of Knowledge
Last minute changes
principles
KISS - Keep it simple stupid
YAGNI - You aren't gonna need it
DRY - don't repeat yourself
SSOT - Single source of truth
Refs:
Tech Debt Calculation
Three Ways to Reduce Tech Debt
Atlassian Tech Debt Definition
Tech Debt Top Tools
How to Measure Tech Debt
/ TDR
How to reduce Tech Dept
How to Avoid?
Reduce velocity of the Sprints
Limited Knowledge /
Use documentation
High-level design and
architecture documentation
Requirements, user stories
Document decisions / debts
Better tools
SonarQube
SQUORE
Kiuwan
Measure & Visualize
Dashboard
How to measure?
code metrics
code duplication
code complexity
cyclomatic complexity
test coverage
dependency cycles
lack of documentation
programming rules violations
dependency coupling
age of code
when it was created
how many times modified
Technical Debt Ratio =
(Remediation Cost / Development Cost) x 100%
Over-engineering
code that solves problems you don't have
wrappers/factories everywhere
Defect Debt
known defects that
are not yet fixed
low priority
low severity
known work-around
Accidental/outdated design
copy-paste and cargo-cult programming