SEI Figures for Managing Technical Debt
Special permission to reproduce portions of the following texts and images was granted by the Software Engineering Institute:
Chapter |
Page Number |
Figure Number |
Description |
|
1 |
Page 14 |
P1-1 |
Principle 1: Technical debt reifies an abstract concept |
|
Page 15 |
F1-1 |
Major concepts of technical debt |
||
2 |
Page 20 |
F2-1 |
Technical Debt Landscape |
|
Page 24 |
C2-A |
Solution U is cheaper than V |
||
Page 25 |
C2-B |
W over V is cheaper than W over U |
||
Page 26 |
C2-C |
Pay interest, or repay the principal |
||
Page 27 |
C2-D |
Pay more interest, or repay the higher principal |
||
Page 32 |
P2-2 |
Principle 2: If you do not incur any form of interest, then you probably do not have actual technical debt |
||
Page 33 |
2-2 |
Technical Debt Timeline |
||
3 |
Page 37 |
F3-1 |
“It depends”: The many factors of context |
|
Page 45 |
P3-3 |
Principle 3: All Systems Have Technical Debt |
||
4 |
Page 53 |
F4-1 |
Timeline: Reaching the awareness point |
|
Page 55 |
P4-4 |
Technical debt must trace to the system |
||
Page 60 |
F4-2 |
Identifying technical debt items |
||
Page 63 |
F4-3 |
The four things to do in development product backlog |
||
5 |
Page 66 |
F5-1 |
Results of the code analysis for Phoebe |
|
Page 67 |
P5-5 |
Technical debt is not synonymous with bad quality |
||
6 |
Page 86 |
P6-6 |
Architecture technical debt has the highest cost of ownership |
|
Page 98 |
F6-1 |
Exploring the cause-and-effect relationships underlying the problem of unexpected crashes |
||
7 |
Page 104 |
F7-1 |
Code release pipeline |
|
Page 107 |
P7-7 |
Principle 7: All code matters! |
||
8 |
Page 118 |
F8-1 |
Timeline: Reaching the tipping point |
|
Page 124 |
P8-8 |
Technical debt has no absolute measure—neither for principal nor interest |
||
Page 128 |
F8-2 |
Grooming the product backlog |
||
9 |
Page 132 |
F9-1 |
Timeline: Reaching the remediation point |
|
Page 134 |
C9-Sidebar |
Risk exposure and opportunity cost |
||
Page 139 |
P9-9 |
Principle 9: Technical debt depends on the future evolution of the system |
||
Page 142 |
F9-2 |
Release planning |
||
Page 144 |
F9-3 |
NPV of alphaPlus |
||
Page 145 |
F9-4 |
NPV of alphaPlus with technical debt |
||
Page 145 |
F9-5 |
NPV of alphaPlus with technical debt repayment |
||
Page 146 |
F9-6 |
Real options: The decision to add features or refactor |
||
10 |
Page 153 |
F10-1 |
The occurrence of technical debt on our timeline |
|
Page 154 |
F10-2 |
Main causes of technical debt |
||
11 |
Page 173 |
F11-1 |
Scorecard for causes of technical debt in the Phoebe project |
|
Page 175 |
F11-2 |
Scorecard for causes of technical debt in the Tethys project |
||
Page 177 |
F11-3 |
Tethys and the technical debt timeline |
||
12 |
|
No figures |
|
|
13 |
Page 196 |
F13-1 |
Timeline for an organization incurring unintentional technical debt |
|
Page 205 |
F13-2 |
Timeline for a technical debt-aware organization |
(SEI trademarks used in this book are registered trademarks of Carnegie Mellon University.)