The Technical Debt Management Cycle:Evaluating the Costs andRisks of IT AssetsDr. Bill CurtisDirector, Consortium for IT S...
Technical Debt Damages Business Value            2
The Technical Debt MetaphorTechnical Debt           the future cost of defects remaining in code at                      ...
How to Use Technical Debt                 Calculating Cost                  Of Ownership       Assessing                  ...
CAST’s Application Intelligence Platform Language                Application                    Detected                  ...
Technical Debt Management Cycle                     Application                                       Build/Release/IT Exe...
Step 1  Set Policy and Quality Priorities Quality         Corporate purpose     Training Policy          Expected behavio...
Step 2  Set Thresholds for App Quality                                    Reliability       3.8                          ...
Step 3  Measure Technical Debt
Step 4  Plan Quality Goals & Actions        3.9                             Quality Score Target        3.7              ...
Step 5  Remediate Violations          11
Step 6  Track Results                            App Management              3.6              3.5                        ...
Step 7  Report to the Business               Quality           Operational             Output              Category      ...
Reducing Technical Debt Is Imperative              14
Upcoming SlideShare
Loading in …5
×

The Technical Debt Management Cycle

1,470 views

Published on

The Technical Debt Management Cycle: Evaluating the Costs and Risks of IT Assets by Dr. Bill Curtis, Director, Consortium for IT Software Quality.

Published in: Technology
1 Comment
0 Likes
Statistics
Notes
  • Whoa! Information overload, but I do appreciate all the efforts put into this work.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

No Downloads
Views
Total views
1,470
On SlideShare
0
From Embeds
0
Number of Embeds
242
Actions
Shares
0
Downloads
20
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

The Technical Debt Management Cycle

  1. 1. The Technical Debt Management Cycle:Evaluating the Costs andRisks of IT AssetsDr. Bill CurtisDirector, Consortium for IT Software Quality
  2. 2. Technical Debt Damages Business Value 2
  3. 3. The Technical Debt MetaphorTechnical Debt  the future cost of defects remaining in code at release, a component of the cost of ownership Business Risk Opportunity cost—benefits that could have been achieved had resources been put on new Opportunity cost capability rather than retiring technical debt Liability from debt Liability—business costs related to outages, breaches, corrupted data, etc. Technical Debt Interest—continuing IT costs attributable to the violations causing technical debt, i.e, higher Interest on the debt maintenance costs, greater resource usage, etc. Principal borrowed Principalcost of fixing problems remaining in the code after release that must be remediatedStructural quality problems in production code 3
  4. 4. How to Use Technical Debt Calculating Cost Of Ownership Assessing Business Risk Estimate ofTechnical Debt Explaining IT Managing Cost of Quality Portfolio Quality 4
  5. 5. CAST’s Application Intelligence Platform Language Application Detected Quality Parsers Analysis Violations MeasurementsOracle PL/SQL Expensive operation in loopSybase T-SQL Static vs. pooled connectionsSQL Server T-SQL Complex query on big table PerformanceIBM SQL/PSMC, C++, C# Large indices on big tablePro CCobol Empty CATCH block Evaluation of Uncontrolled data accessCICSVisual Basic 1200+ coding & Poor memory management RobustnessVB.Net architectural rules Opened resource not closedASP.NetJava, J2EE SQL injectionJSP Application Cross-site scriptingXML Buffer overflow SecurityHTML meta-dataJavascript Uncontrolled format stringVBScriptPHP Unstructured code Misuse of inheritancePowerBuilderOracle Forms Lack of comments TransferabilityPeopleSoft Violated naming conventionSAP ABAP,Netweaver Highly coupled componentTibco Duplicated codeBusiness Objects Index modified in loop ChangeabilityUniversal Analyzerfor other languages High cyclomatic complexity 5
  6. 6. Technical Debt Management Cycle Application Build/Release/IT Executives Managers Developers QA/AI Center Step 1 Step 2 Step 3 Set policy and Set thresholds Measurequality priorities for app quality Technical Debt Step 4 Plan reduction goals & actions Step 7 Step 6 Step 5 Report to the Remediate Track results business violations 6
  7. 7. Step 1  Set Policy and Quality Priorities Quality Corporate purpose Training Policy Expected behavior Reporting Audit Reliability Performance Security Quality Customer-facing MaintainabilityPriorities Internal business Reliability Performance Security Maintainability 7
  8. 8. Step 2  Set Thresholds for App Quality Reliability 3.8 Performance 3.9 Product information Security 2.5 Maintainability 3.0 Retail Reliability Performance 3.5 3.5 Online purchaseWebsite Security Maintainability 3.9 2.5 Reliability 3.5 Performance 3.0 Delivery scheduling Security 3.9 Maintainability 2.5 8
  9. 9. Step 3  Measure Technical Debt
  10. 10. Step 4  Plan Quality Goals & Actions 3.9 Quality Score Target 3.7 by Release 3.5 3.3 ReliabilityScore 3.1 Performance 2.9 Security 2.7 Maintainability 2.5 10
  11. 11. Step 5  Remediate Violations 11
  12. 12. Step 6  Track Results App Management 3.6 3.5 AppDev PlannedPerformance 3.4 Exec Efficiency 3.3 Actual 3.2 3.1 3 2.9 Portfolio 2.8 QA Data 2.7 Repository 12
  13. 13. Step 7  Report to the Business Quality Operational Output Category problems Measure Outages, slow Resilience Availability recovery Degraded Efficiency Work efficiency responseTechnical Security Breaches, Theft Data protection debt Lengthy Transferability IT productivity comprehension Changeability Excessive effort Delivery speed 13
  14. 14. Reducing Technical Debt Is Imperative 14

×