I didn't really know what to expect from "Managing Software Debt." It was the first time I've seen the phrase software debt in a title so I was intrigued. The book does not assume you are a developer or a manager and makes it readable for both.
The descriptions of how debt creeps into the process was excellent.
My five favorite parts were:
"abuse stories" (anti-use cases)
the last chapter - people aren't resources and why this matters along with styles of teams
the word "done" repeatedly being in quotes and an exercise on how to create a definition
the cost of someone else paying the cost of your poor decisions
why silos create debt
I made lots of highlights and was engaged as I read. I didn't make notes in the book because some would be less than favorable to someone who could pick it up. It definitely hit home though.
I would have liked some more tips on how to deal with debt and how to prevent it. The book was certainly thought provoking and raised my awareness of debt in day to day work.
Disclosure: I received a copy of this book from the publisher in exchange for writing this review on behalf of CodeRanch.