Managing Technical Debt: Reducing Friction in Software Development

This book provides practical solutions for managing technical debt in software systems, offering insights from experienced authors and case studies. It helps software professionals identify, assess, and prioritize technical debt items, and choose the right solutions to reduce or mitigate them. The book emphasizes the importance of establishing technical debt management as a core practice in organizations to promote software quality and productivity.

\n Format: Paperback / softback
\n Length: 272 pages
\n Publication date: 06 June 2019
\n Publisher: Pearson Education (US)
\n

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 it is 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.

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 specific sources of technical debt, including design decisions, code quality, and testing practices.

Implement strategies for limiting new debt, such as refactoring, modularization, and automated testing.

Develop a plan for "paying off" debt over time, including prioritization, resource allocation, and continuous improvement.

Establish managing technical debt as a core software engineering practice in your organization.

By applying these principles and practices, software professionals can improve the manageability, quality, productivity, and morale of their software systems while reducing the risk of technical debt. This book is a valuable resource for anyone involved in software development, from developers and architects to project managers and executives.

\n Weight: 446g\n
Dimension: 232 x 181 x 14 (mm)\n
ISBN-13: 9780135645932\n \n