Название: Taming Your Dragon: Addressing Your Technical Debt
Автор: Andrew Richard Brown
Издательство: Apress
Год: 2024
Страниц: 372
Язык: английский
Формат: pdf
Размер: 10.1 MB

Technical debt is an often-overlooked problem that the software industry needs to take more seriously. All organizations are impacted by it, most wish that they had less of it, but need help in understanding the nature of the beast. This book aims to clear up any misconceptions and show you how to implement a sound technical debt management program to suit your company’s needs.

You’ll learn the greatest challenge in solving the technical debt dilemma is not to find solutions to it, but rather to find solutions to the human and organizational issues that lead to that debt. For example, convincing senior stakeholders of the importance of addressing technical debt, getting stakeholders to acknowledge how their actions lead to unintentional debt, and enabling teams to prioritize technical debt over short-term goals.

Therefore, this book is divided into three parts: defining technical debt, understanding technical debt, and tackling technical debt. It begins by explaining why technical debt should not be considered a technical problem, but rather a problem of how trade-off decisions are made. You’ll then examine how making decisions using the affect heuristic, more commonly known as a “gut feeling,” can lead to unnecessary technical debt, followed by some techniques for combating your vulnerability to this trap.

Reducing your organization’s level of technical debt is not easy. Taming Your Dragon will show you how to implement a technical debt management program.

What You Will Learn:

Review a new paradigm based on technical debt being a combination of trade-off problems and system problems
Understand the many ways that technical debt adversely affects an organization’s ability to deliver IT change
Create an effective process for addressing technical debt
See why analogies are important

Who This Book Is For:
This book is aimed at people in software teams, both those on projects, who are sometimes making decisions that result in technical debt, as well as those in support of DevOps, who must deal with the consequences of that debt. However, the book is not intended to be used to address that debt directly. Such an approach will not lead to any lasting change. Instead, this book will help you understand technical debt’s underlying causes and then enable you to advocate to stakeholders how you can address those causes in a planned intervention aimed at producing lasting improvement.

This book is also aimed at managers and business stakeholders, who wish to understand why software development takes so long and costs so much. This book will help you understand how you end up with high levels of technical debt that slow down every software project. It will also help you devise a program to reduce your technical debt to manageable levels and then keep it manageable.

This book is also aimed at consultants who have traced an organization’s problems to its high level of technical debt. This book will show you how to implement a technical debt management program.








[related-news] [/related-news]