Skip to content
Description
By: Neil Ernst, Rick Kazman, Julien Delange
The practical implications of technical debt for the entire software lifecycle; with examples and case studies.
Technical debt in software is incurred when developers take shortcuts and make ill-advised technical decisions in the initial phases of a project, only to be confronted with the need for costly and labor-intensive workarounds later. This book offers advice on how to avoid technical debt, how to locate its sources, and how to remove it. It focuses on the practical implications of technical debt for the entire software life cycle, with examples and case studies from companies that range from Boeing to Twitter.
Technical debt is normal; it is part of most iterative development processes. But if debt is ignored, over time it may become unmanageably complex, requiring developers to spend all of their effort fixing bugs, with no time to add new features--and after all, new features are what customers really value. The authors explain how to monitor technical debt, how to measure it, and how and when to pay it down. Broadening the conventional definition of technical debt, they cover requirements debt, implementation debt, testing debt, architecture debt, documentation debt, deployment debt, and social debt. They intersperse technical discussions with "Voice of the Practitioner" sidebars that detail real-world experiences with a variety of technical debt issues.
The practical implications of technical debt for the entire software lifecycle; with examples and case studies.
Technical debt in software is incurred when developers take shortcuts and make ill-advised technical decisions in the initial phases of a project, only to be confronted with the need for costly and labor-intensive workarounds later. This book offers advice on how to avoid technical debt, how to locate its sources, and how to remove it. It focuses on the practical implications of technical debt for the entire software life cycle, with examples and case studies from companies that range from Boeing to Twitter.
Technical debt is normal; it is part of most iterative development processes. But if debt is ignored, over time it may become unmanageably complex, requiring developers to spend all of their effort fixing bugs, with no time to add new features--and after all, new features are what customers really value. The authors explain how to monitor technical debt, how to measure it, and how and when to pay it down. Broadening the conventional definition of technical debt, they cover requirements debt, implementation debt, testing debt, architecture debt, documentation debt, deployment debt, and social debt. They intersperse technical discussions with "Voice of the Practitioner" sidebars that detail real-world experiences with a variety of technical debt issues.
You may also like
Top Trending
Dog Man 14: Dog Man: Big Jim Believes: A Graphic Novel (Dog Man #14)
Sale priceHK$85.00
Regular priceHK$150.00
In stock
Press Start! #17 The Super Jump Between Worlds! (Branches)
Sale priceHK$55.00
Regular priceHK$98.00
In stock
Anzu and the Realm of Darkness: A Graphic Novel
Sale priceFrom HK$85.00
Regular priceHK$140.00
In stock
The Midnight Heist (Geronimo Stilton and The Kingdom of Fantasy #17)
Sale priceHK$128.00
Regular priceHK$200.00
In stock
Cat Kid Comic Club (正版) #04 Collaborations (Dav Pilkey)
Sale priceFrom HK$65.00
Regular priceHK$90.00
In stock
Maisy's (正版) Holiday Picture Book Bag Collection (Lucy Cousins)
Sale priceHK$185.00
Regular priceHK$504.00
In stock
