Technical Debt

C afé Identifying, Measuring, Reducing & Avoiding Technical Debt Rob Myers for ADP East 10 Nov 201109 November 2011 © Agile Institute 2011 1

time (schedule) effort (cost) size (scope) Five Core Metrics: The Intelligence Behind Successful Software Management, Lawrence H. Putnam & Ware Myers, Dorset House Publishing, 200309 November 2011 © Agile Institute 2011 2

time (schedule) productivity effort (cost) size (scope) Five Core Metrics: The Intelligence Behind Successful Software Management, Lawrence H. Putnam & Ware Myers, Dorset House Publishing, 200309 November 2011 © Agile Institute 2011 2

reliability time (schedule) (quality) productivity effort (cost) size (scope) Five Core Metrics: The Intelligence Behind Successful Software Management, Lawrence H. Putnam & Ware Myers, Dorset House Publishing, 200309 November 2011 © Agile Institute 2011 2

09 November 2011 © Rob Myers 2011 3

“...having high amounts of Technical Debt isprobably the number one impediment to Teamsbeing agile.” Dr. Dan Rawsthorne, Exploring Scrum:The Fundamentals

• Design Debt

• Design Debt• Quality Debt

• Design Debt• Quality Debt• Testing Debt

• Design Debt• Quality Debt• Testing Debt• ...ad nauseam

• Design Debt

• Design Debt • Cyclomatic complexity

• Design Debt • Cyclomatic complexity • Cycle time

• Design Debt • Cyclomatic complexity • Cycle time• Quality Debt

• Design Debt • Cyclomatic complexity • Cycle time• Quality Debt • Mean Time Between Failures

• Design Debt • Cyclomatic complexity • Cycle time• Quality Debt • Mean Time Between Failures • Severe-defect count

• Design Debt • Cyclomatic complexity • Cycle time• Quality Debt • Mean Time Between Failures • Severe-defect count• Testing Debt

• Design Debt • Cyclomatic complexity • Cycle time• Quality Debt • Mean Time Between Failures • Severe-defect count• Testing Debt • % Covered

• Design Debt • Cyclomatic complexity • Cycle time• Quality Debt • Mean Time Between Failures • Severe-defect count• Testing Debt • % Covered • Time to regression test

09 November 2011 © Rob Myers 2011 7

(c) SoftwareHumor.com http://theleek.net/software-humor-blog/posters/technical-debt-the-poster/09 November 2011 © Rob Myers 2011 8

Minimal Iteration Debt Payment

Test Drive!09 November 2011 © Rob Myers 2011 10

“The results of the case studies indicate that the pre-release defect density of the four products decreased between 40% and 90% relative to similar projects that did not use the TDD practice. Subjectively, the teams experienced a 15–35% increase in initial development time after adopting TDD.”http://research.microsoft.com/en-us/projects/esm/nagappan_tdd.pdf, Nagappan et al, © Springer Science + Business Media, LLC 2008 09 November 2011 © Rob Myers 2011 11

Developer’s “Oath of Athens” I vow to leave the code asgood as I found it, or better!

• Design Debt

• Design Debt • Merciless Refactoring

• Design Debt • Merciless Refactoring• Quality Debt

• Design Debt • Merciless Refactoring• Quality Debt • Find bugs before check-in

• Design Debt • Merciless Refactoring• Quality Debt • Find bugs before check-in• Testing Debt

• Design Debt • Merciless Refactoring• Quality Debt • Find bugs before check-in• Testing Debt • Fast automation

• The Wobbly Iron Rhomboid

• The Wobbly Iron Rhomboid• At ﬁrst, Quality v. Productivity trade-offs

• The Wobbly Iron Rhomboid• At ﬁrst, Quality v. Productivity trade-offs• Sharpen the Chef’s Knives

• The Wobbly Iron Rhomboid• At ﬁrst, Quality v. Productivity trade-offs• Sharpen the Chef’s Knives• Quality quickly improves throughput of value (Productivity)

Rob.Myers@agileInstitute.com http://PowersOfTwo.agileInstitute.com/ @agilecoach09 November 2011 © Agile Institute 2011 15

http://www.ontechnicaldebt.com	20
http://paper.li	15
http://www.linkedin.com	1

Technical Debt

by Agile Institute

Accessibility

Categories

Upload Details

Usage Rights

3 Embeds 36

Statistics

Technical Debt Presentation Transcript