I got this book on 2014/06/17 and I've read into Chapter 3.
Chapter 1 is somewhat different from the other chapters in that rather than being a series of principles, it provides an overall view of practice orthodoxy and how many of these closely held beliefs are based on secondary or proxy variables. The chapter continues with an overview of several examples and then summarizes and discusses where things are going in the rest of the book as well as the layout. The first chapter is great. I did expect it to end a bit sooner than it did (I was thinking in terms of self-referential, small batch sizes), but I'm not sure a shorter chapter would have been better.
The second chapter introduces the approach for the rest of the book as well as the model underpinning the principles. The approach works for me. I imagine myself reading this book, going back and creating queue cards for each of the principles, then periodically looking up individual ones and refreshing my memory. It seems like a book I can keep going back to and reading just because I want 5 minutes of good reading.
For some context, I'm a software developer. I learned about the Theory of Constraints (ToC) before I really learned software development processes in depth. When I did being the software process journey, it was under the OO umbrella, so incremental and iterative, feedback, etc. This learning, however, I've recently realized (by first reading Kanban and now this book) was heavily influenced by the ToC. At the beginning of this century, I jumped on the XP and Scrum bandwagons, even working with a few of the original signatories on the manifesto for agile development.
ToC came up a number of times while coaching. Moving from ToC to thinking in terms of Kanban isn't much of a leap to me. However, since I was applying things I learned and internalized, things that seem obvious to me are often not obvious to my customers or even my colleagues (yes, sometimes I'm wrong, but often I'm not). For example, at many, many places I've been, companies claim they are practicing continuous integration or even continuous delivery, but then their builds are broken (red) 80+ % of the time. This is a huge cost to productivity, morale, feedback, etc. This is one example of many such examples that, in in the context of ToC are obvious bottlenecks, which cause queueing. If I look with lean glasses, many of these are worthy of stopping the line, but people march on, building up queues of work to be committed, which lead to more broken builds, integration problems, demoralization, etc.
However, what seems obvious to me doesn't seem obvious to others. More importantly, many people don't even see that there's a problem at all! They think, for example, when developers complain about being blocked due to the build being broken, it's just developers complaining about a minor glitch, but it is more typically a systemic problem.
This books presents a model based on economics. One thing that I observed myself observing about the book was that I thought it might be over emphasizing one dimension, cost of delay, or one approach, economics. However, "all models are wrong, some are valuable." While I had this observation, I didn't find anything wrong about the conclusions, and in fact find my self thinking "yes and," so I've kept reading. So while this model may be wrong in some ways (I'm not aware of any), I clearly see immediate and near-term value for me with its use.
What this model does is allow me to speak to upper management, and maybe middle management using a language they are likely to appreciate. I'm able to justify things like slack using economic models, so that I might be better able to communicate with them. So rather than talking about the flexibility and agility that well under 100% utilization might offer, instead I can discuss the cost of delivery related to high utilization (lack of slack). My primary failing up until now is not being able to explain what seems intuitive to me in a way that bridges the communication gap. This model seems to give me another way to both think about it and communicate it.
I have not finished reading the book, but in the the spirit of small batch sizes, this is my first delivery. I'll be making updates as I read the book. I am already confident that I'll finish this book and that I can recommend it to people. It'll have to really work hard to go under a 5 star review.
Finally (so far): my impression so far reading the book is that it seems well researched, brings together a number of disciplines in a non-trivial manner and seems to come form someone who legitimately has many good years of experience, not just the same 1 year of experience repeated over and over.
Enjoy fast, free delivery, exclusive deals, and award-winning movies & TV shows with Prime
Try Prime
and start saving today with fast, free delivery
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet, or computer - no Kindle device required.
Read instantly on your browser with Kindle for Web.
Using your mobile phone camera - scan the code below and download the Kindle app.
Something went wrong. Please try your request again later.
Frequently bought together
$39.95
Get it as soon as Sunday, May 19
In Stock
Total price:
To see our price, add these items to your cart.
Choose items to buy together.
More items to explore
Page 1 of 1 Start overPage 1 of 1
About the author
Follow authors to get new release updates, plus improved recommendations.
Top reviews from other countries
Christoph Dibbern
Groundbreaking book about fostering the right balance between efficiency, effectiveness and predictability
Reviewed in Germany on September 22, 2023Barbara Schultz
What an awesome way to speak the language of business ($$) in order to promote business agility.
Reviewed in Canada on March 1, 2021
DT
Revolutionary Thoughts on Product Development Management in Bite-size chunks
Reviewed in the United Kingdom on July 26, 2020Riccardo Ianniello
Uno dei migliori libri sul product management
Reviewed in Italy on December 27, 2018