The latest Tweets from Donald Reinertsen (@DReinertsen). Product Development Consultant, Author, Always trying to learn more about math, science, and. Donald G. Reinertsen. · Rating details · 1, ratings · 94 reviews. In this book, Reinertsen provides an examination of product development practices. 14 quotes from Donald G. Reinertsen: ‘In product development, our greatest waste is not unproductive engineers, but work products sitting idle in process.
|Published (Last):||9 June 2004|
|PDF File Size:||9.88 Mb|
|ePub File Size:||7.63 Mb|
|Price:||Free* [*Free Regsitration Required]|
Low to High Price: I consider this a must-read for product development companies in the 21st century. Managing The Design Factory ratings.
The more we increase planning detail and the harder we try to incentivize performance, the worse our problem becomes. For the principles that cannot, the philosophy behind those principles is g.reinerrsen to develop new principles for product development.
Synchronization is the observation that if work is arriving to a queue at a random wait, then wait times will be longer than if the two workflows are syncronized so that the first produces work at approximately the rate at which capacity is available at the next work flow.
This is a deep and heavy book describing the principles of any flow-based system, how to identify constraints, and how to optimize throughput.
Reinertsen basically takes the principles of Lean Manufacturing and explains the ways in which they can apply to product development and the ways in which they cannot. Jun 10, Charles Eliot rated it really liked it. In this book, Reinertsen provides an examination of product development practices. Amazon Drive Cloud storage from Amazon.
Quotes from The Principles of To see what your friends thought of this book, please sign up.
TOC even prescribes smaller batch sizes, as it enables higher utilization g.reiinertsen the bottlenecks. He also readily uses terminology from disparate fields that the reader might not have exposure to such as probability and statistics, control theory, and economics. Reinertsen’s attempt to write a condense book. To get the last star the book had to be readable – the format is very condensed, making it a quite tough read.
Apr 21, Ben rated it really liked it. In contrast, most product development organizations exclusively reward specialization. He explains why invisible and unmanaged queues are the underlying root cause of poor product development performance. This book is packed with principles that range from queue theory to batch size management to explain how “flow” works best in product development.
This is the section that had the most novel-to-me domain of inspiration: The standard view is g.reunertsen variability is bad. Amazon Rapids Fun stories g.rienertsen kids on the go.
Some of the terms used have very specific meanings, like transfer functions, transients, and step functions from the world of control theory. Probably the most important book on software development processes ever written.
Work in progress WIP constraints are one of the primary mechanisms for controlling queue size. Thanks for telling us about the problem. There are two aspects to a book: Each widget you make gives the same profit, but every new product you develop has different trade-offs for both profit and loss.
Reinertsen is flaming Goldratt’s theory of constraints TOC – apparently without understanding it. He warns in his introduction that his book is very technical, but it’s worse than that: Amazon Inspire Digital Educational Resources. The shape of the conclusions apply to other queueing disciplines, but the equations don’t apply exactly. Prasan At last I g.reinsrtsen it: I also think the economic case for the problems with queues isn’t particularly strong, everything else is very nuanced, but felt like I just had to agree with that premise.
All interesting, if a bit abstract. I’d have given it five stars but for two criticisms. Reinertsen’s principles together are truly more than just the sum of their parts. The most important moment in the book is probably Figure 8.
Being clear about the end state that a group is trying to achieve, the constraints, and the reasoning behind that goal help create alignment.
It would be easy to declare a principle about what the right batch size is, but instead, the particular economic trade-offs of batches in a particular situation should be taken into account. You sort of have to trust him on this if you can’t do the proofs yourself.