Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your mobile phone number.

Kindle Price: £25.00

Save £18.99 (43%)

includes VAT*
* Unlike print books, digital books are subject to VAT.

These promotions will be applied to this item:

Some promotions may be combined; others are not eligible to be combined with other offers. For details, please see the Terms & Conditions associated with these promotions.

Deliver to your Kindle or other device

Deliver to your Kindle or other device

Managing Software Debt: Building for Inevitable Change (Adobe Reader) (Agile Software Development Series) by [Sterling, Chris]
Kindle App Ad

Managing Software Debt: Building for Inevitable Change (Adobe Reader) (Agile Software Development Series) 1st , Kindle Edition

4.0 out of 5 stars 1 customer review

See all 3 formats and editions Hide other formats and editions
Amazon Price
New from Used from
Kindle Edition
"Please retry"
£25.00

20 Years of Harry Potter
Celebrating 20 Years of Harry Potter Magic Learn more
Get a £1 reward for movies or TV
Enjoy a £1.00 reward to spend on movies or TV on Amazon Video when you purchase any Amazon Kindle Book from the Kindle Store (excluding Kindle Unlimited, Periodicals and free Kindle Books) offered by Amazon.co.uk. A maximum of 1 reward per customer applies. UK customers only. Offer ends at 23:59 on Wednesday, September 27, 2017. Terms and conditions apply

Product description

Review

“If you work in technology, you’re probably familiar with terms like ‘technical debt.’ The metaphor seems easy, but using it to influence change can be remarkably hard. To do that, you’re going to want to present options to decision makers, backed up by evidence. I’ve been impressed watching Chris Sterling research and refine his work in just this area for several years, and I’m pleased to see him release it as a book. If you want to go beyond clichés to talk about how to deal with the problem of software debt, this is the seminal work in the field—and it’s also the book for you.”

—Matthew Heusser, Software Process Naturalist

 

“Inertia: It’s what restricts change and leads to a cost of making a change or starting a change after a period of no investment or maintenance. This book explains in great detail what the different types of debt are that lead to inertia and, ultimately, to a cost to the business in managing software maintenance and development. The richness of explanation in this book of how to manage the virtual debt that every business incurs is unmatched. Every business-focused CIO, enterprise architect, software architect, or project manager should have a copy.”

—Colin Renouf, Enterprise Architect

 

“Software debt is an important concept and Sterling does a sterling job of explaining what it is, why it is bad, and how to avoid it. A healthy dose of theory sprinkled with lots of pragmatic examples.”

—Roger Sessions, CTO, ObjectWatch (objectwatch.com)

 

“Chris Sterling’s experience in Agile architecture and his focus on software debt make this book a must-read for architects and engineers on Agile teams.”

—Jan Bosch, VP Engineering Process, Intuit

 

“This book offers highlights and shortcomings of managing inherited software code and the debts that come with quality software. The author offers a unique perspective on dealing with software development issues. A must-read for all software developers.”

—Leyna Cotran, Institute for Software Research, University of California, Irvine

 

“The vital importance of rapid feedback to the software process is a fundamental premise of modern software methods. When such feedback is quantified in the form of software debt, the software process becomes most effective. Chris Sterling’s book holds the details you need to know in order to quantify the debt and pay it back. Moreover, it will teach you how to avoid debt in the first place.”

—Israel Gat, The Agile Executive (theagileexecutive.com and on Twitter at @agile_exec)

 

“This book represents a wonderful opportunity for a larger community to take advantage of Chris’s many years of experience and his innovative approaches to Agile architecture and continuous quality. . . . His book distills many of his principles and techniques into practical guidelines, and he manages to convey very powerful ideas in accessible prose, despite the inherent complexity of architecture and technical debt. . . . Chris’s book will help architects, leaders, and teams see their way to better systems and better organizational performance.”

—Evan Campbell, Founder of Chinook Software Consulting

About the Author

Chris Sterling, Partner at Sterling Barton, LLC, works with widely diverse clients as a technology, management, and Agile consultant. A Certified Scrum Trainer and Innovation Games Facilitator, he has created—and continues contributing to—multiple open source projects. He has been a speaker at many conferences and events, including Agile conferences, Better Software, SD West, Scrum Gatherings, and PNSQC. He teaches the Advanced Topics in Agile Software Development course for the University of Washington’s Agile Developer Certificate extension program.

Product details

  • Format: Kindle Edition
  • File Size: 2656 KB
  • Print Length: 288 pages
  • Simultaneous Device Usage: Up to 5 simultaneous devices, per publisher limits
  • Publisher: Addison-Wesley Professional; 1 edition (10 Dec. 2010)
  • Sold by: Amazon Media EU S.à r.l.
  • Language: English
  • ASIN: B004GXB3YO
  • Text-to-Speech: Enabled
  • X-Ray:
  • Word Wise: Not Enabled
  • Screen Reader: Supported
  • Enhanced Typesetting: Enabled
  • Average Customer Review: 4.0 out of 5 stars 1 customer review
  • Amazon Bestsellers Rank: #779,718 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
  • Would you like to tell us about a lower price?

Customer Reviews

4.0 out of 5 stars
5 star
0
4 star
1
3 star
0
2 star
0
1 star
0
See the customer review
Share your thoughts with other customers

Top Customer Reviews

Format: Hardcover
Technical debt has become a trendy term for an issue that exists since the beginning of software development projects. It is what happens when you neglect, consciously or not, the long-term quality of your software to achieve other usually short term benefits. After defining the concept of software debt, Chris Sterling explores the topic of managing software debt in all software development activities. Three chapters are dedicated to the topic of design and architecture, discussing how they should fit in Agile approaches.

As its title suggests, this book goes even further than the concept of technical debt as it try to cover all dimensions of software development debt. My favorite chapter comes at the end where the notion of experience debt is explored. I have witnessed many projects where the technical or product knowledge was concentrated on fewer and fewer people, due to change in project team composition, effectively making them the bottlenecks where all application evolutions had to be processed. We sometimes create more debt in the heads than in the code.

The book is well written and easy to read. Every chapter begins with a mindmap of the topic that will be explored, thus giving a big picture of its content. The material mixes high level definitions with practical examples and real life stories. A summary is proposed at the end of each chapter

At every stage of the software development life cycle, we make decisions that have long term consequences. This book provides meaningful insights on how to prevent creating too much debt and how to reduce the existing burden. I will recommend it to everybody who is concerned with software quality with a longer view than the end of the next iteration.
Comment One person found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse

Most Helpful Customer Reviews on Amazon.com (beta) (May include reviews from Early Reviewer Rewards Program)

Amazon.com: 4.4 out of 5 stars 9 reviews
1 of 1 people found the following review helpful
5.0 out of 5 stars Software debt and technical debt explained clearly in laymans terms. 12 Sept. 2011
By Daron Levy - Published on Amazon.com
Format: Hardcover Verified Purchase
This book should be mandatory reading for anyone who manages a team of software developers. The same goes for project managers over software development as well. After being in the industry for almost 7 years now, I've seen many of the same mistakes made that this book warns against, and the real costs involved. I have seen software projects bogged down in the same ways that this book describes. I was startled at how accurate the book predicted the root causes of software debt, and the outcomes when software debt problems are ignored.

From a superficial level, I found this book easy to read, and simple to understand. The book is intended for anyone in the software industry, though managers will definitely get more out of it. Despite the textbook look and feel, it's not overly technical. My only complaint is that I wish it were more affordable. If it were, I'd buy a copy for my boss... and his boss too!
4.0 out of 5 stars Good resource for leaders in the Software Development space 15 May 2013
By Scott Benners - Published on Amazon.com
Format: Hardcover Verified Purchase
After spending many years in Software Development, with the last few years managing agile teams, I found Sterling's assessment to be spot-on. The author did a very good job covering so many different types of software debt. As I was reading through each chapter I would say to myself, "oh yes, I remember an instance of that". This should be a required read for any software development leader, whether you're in development, architecture or management. If you haven't yet experienced the different scenarios of debt mentioned, you eventually will.
5.0 out of 5 stars Right on target... 17 April 2013
By Amazon Customer - Published on Amazon.com
Format: Kindle Edition Verified Purchase
I am not personally aware of many organizations that do this well. It is a level of discipline that few can maintain 100% of the time. Chris presents a pragmatic, and well reasoned approach to managing tech debt that I can continue to learn from.
0 of 1 people found the following review helpful
4.0 out of 5 stars A few years ahead... Agile +++ 22 May 2012
By Ash - Published on Amazon.com
Format: Kindle Edition Verified Purchase
This is a good book for anyone who:
1. Is looking for the way forward with software product development using Agile methodology.
2. Wants to build robust yet flexible software.
3. Has a focus on long haul software product development

I especially like the aspects of technology debt which have been explained very well.
This is the future of software product development as I see it.
4.0 out of 5 stars This book provides meaningful insights on how to prevent creating too much debt 5 Aug. 2011
By Methods & Tools Software Development Magazine - Published on Amazon.com
Format: Hardcover
Technical debt has become a trendy term for an issue that exists since the beginning of software development projects. It is what happens when you neglect, consciously or not, the long-term quality of your software to achieve other usually short term benefits. After defining the concept of software debt, Chris Sterling explores the topic of managing software debt in all software development activities. Three chapters are dedicated to the topic of design and architecture, discussing how they should fit in Agile approaches.

As its title suggests, this book goes even further than the concept of technical debt as it try to cover all dimensions of software development debt. My favorite chapter comes at the end where the notion of experience debt is explored. I have witnessed many projects where the technical or product knowledge was concentrated on fewer and fewer people, due to change in project team composition, effectively making them the bottlenecks where all application evolutions had to be processed. We sometimes create more debt in the heads than in the code.

The book is well written and easy to read. Every chapter begins with a mindmap of the topic that will be explored, thus giving a big picture of its content. The material mixes high level definitions with practical examples and real life stories. A summary is proposed at the end of each chapter

At every stage of the software development life cycle, we make decisions that have long term consequences. This book provides meaningful insights on how to prevent creating too much debt and how to reduce the existing burden. I will recommend it to everybody who is concerned with software quality with a longer view than the end of the next iteration.
Were these reviews helpful? Let us know
click to open popover