

Philippe Kruchten is a professor of software engineering at the University of British Columbia in Vancouver, Canada.
Meer over de auteursManaging Technical Debt
Reducing Friction in Software Development
Paperback Engels 2019 1e druk 9780135645932Samenvatting
Master Best Practices for Managing Technical Debt to Promote Software Quality and Productivity
As software systems mature, earlier design or code decisions made in the context of budget or schedule constraints increasingly impede evolution and innovation. This phenomenon is called technical debt, and practical solutions exist. In Managing Technical Debt, three leading experts introduce integrated, empirically developed principles and practices that any software professional can use to gain control of technical debt in any software system.
Using real-life examples, the authors explain the forms of technical debt that afflict software-intensive systems, their root causes, and their impacts. They introduce proven approaches for identifying and assessing specific sources of technical debt, limiting new debt, and “paying off” debt over time. They describe how to establish managing technical debt as a core software engineering practice in your organization.
- Discover how technical debt damages manageability, quality, productivity, and morale–and what you can do about it
- Clarify root causes of debt, including the linked roles of business goals, source code, architecture, testing, and infrastructure
- Identify technical debt items, and analyze their costs so you can prioritize action
- Choose the right solution for each technical debt item: eliminate, reduce, or mitigate
- Integrate software engineering practices that minimize new debt
Managing Technical Debt will be a valuable resource for every software professional who wants to accelerate innovation in existing systems, or build new systems that will be easier to maintain and evolve.
"This is an incredibly wise and useful book. The authors have considerable real-world experience in delivering quality systems that matter, and their expertise shines through in these pages. Here you will learn what technical debt is, what is it not, how to manage it, and how to pay it down in responsible ways. This is a book I wish I had when I was just beginning my career. The authors present a myriad of case studies, born from years of experience, and offer a multitude of actionable insights for how to apply it to your project." – Grady Booch, IBM Fellow
Specificaties
Lezersrecensies
Over Robert Nord
Over Ipek Ozkaya
Inhoudsopgave
Preface xv
Part I: Exploring the Technical Debt Landscape 1
Chapter 1: Friction in Software Development 3
Chapter 2: What Is Technical Debt? 19
Chapter 3: Moons of Saturn–The Crucial Role of Context 37
Part II: Analyzing Technical Debt 49
Chapter 4: Recognizing Technical Debt 51
Chapter 5: Technical Debt and the Source Code 65
Chapter 6: Technical Debt and Architecture 83
Chapter 7: Technical Debt and Production 103
Part III: Deciding What Technical Debt to Fix 115
Chapter 8: Costing the Technical Debt 117
Chapter 9: Servicing the Technical Debt 131
Part IV: Managing Technical Debt Tactically and Strategically 149
Chapter 10: What Causes Technical Debt? 151
Chapter 11: Technical Debt Credit Check 167
Chapter 12: Avoiding Unintentional Debt 179
Chapter 13: Living with Your Technical Debt 195
Glossary 207
References 209
Index 217
Rubrieken
- advisering
- algemeen management
- coaching en trainen
- communicatie en media
- economie
- financieel management
- inkoop en logistiek
- internet en social media
- it-management / ict
- juridisch
- leiderschap
- marketing
- mens en maatschappij
- non-profit
- ondernemen
- organisatiekunde
- personal finance
- personeelsmanagement
- persoonlijke effectiviteit
- projectmanagement
- psychologie
- reclame en verkoop
- strategisch management
- verandermanagement
- werk en loopbaan