5. www.co-learning.be
Let’s share an observation!
Phase 2
Not taking care of
Technical Debt
Exponential Growth of
Implementation Cost
For New Feature
Phase 1
New Product Started
Low Implementation Cost
For New Feature
Phase 3
Long time not taking care of
Technical Debt
Exploding
Implementation Cost
For New Feature
9. www.co-learning.be
Change some part of the system…
# of known defects
for the entire product
% time spend
developing Clean Code
% time spend
developing Quick
Bug Fixes
% Clean Code in
the entire product
but we have
1999!!!
O
O
10. www.co-learning.be
A system change
# of known defects
for the entire product
% time spend
developing Clean Code
% time spend
developing Quick
Bug Fixes
% Clean Code in
the entire product
O
O
23. www.co-learning.be
Improvement Kata
Step 1
Step 4
Step 3
Step 2
Grasp the
Current Condition
Get The Direction or
Challenge
Establish your
Next Target Condition
Conduct
Experiments
to get there
25. www.co-learning.be
Fast decision making using a decentralised model
Deliberately paying back your debt by refactoring
That’s it!
2 aspects on dealing with technical debt from a business perspective
Step 1
Step 4
Step 3
Step 2
Grasp the
Current Condition
Get The Direction or
Challenge
Establish your
Next Target Condition
Conduct
Experiments
to get there
28. My Purpose
Clean it up
or run away!
www.co-learning.be
Help organizations to build
Great Products with Great Teams
in/jurgendesmet
PS: What title would be more suited now?
Technical Debt from a Business Perspective or Technical Debt with a Business Perspective