| | |  | Total Productive Maintenance (TPM) | Home » » » The Principles of Product Development Flow: Second Generation Lean Product Development | | | | | | | Description: | | "...the dominant paradigm for managing product development is wrong. Not just a little wrong, but wrong to its very core." So begins Reinertsen in his meticulous examination of today's product development practices. He carefully explains why invisible and unmanaged queues are the underlying root cause of poor product development performance. He shows why these queues form and how they undermine the speed, quality, and efficiency in product development. Then, he provides a roadmap for changing this. The book provides a well-organized set of 175 underlying principles in eight major areas. He shows you practical methods to: - Improve economic decisions
- Manage queues
- Reduce batch size
- Apply WIP constraints
- Accelerate feedback
- Manage flows in the presence of variability
- Decentralize control
The Principles of Product Development Flow will forever change the way you think about product development. Reinertsen starts with the ideas of lean manufacturing but goes far beyond them, drawing upon ideas from telecommunications networks, transportation systems, computer operating systems and military doctrine. He combines a lucid explanation of the science behind flow with a rich set of practical approaches. This is another landmark book by one of the foremost experts on product development. | | | Product Details: | | | Author:
| Donald G. Reinertsen | | Hardcover:
| 304 pages | | Publisher:
| Celeritas Publishing | | Publication Date:
| May 29, 2009 | | Language:
| English | | ISBN:
| 1935401009 | | Product Width:
| 1.56 centimeters | | Product Height:
| 2.25 centimeters | | Product Weight:
| 0.01 pounds | | Package Length:
| 9.2 inches | | Package Width:
| 6.1 inches | | Package Height:
| 1.2 inches | | Package Weight:
| 1.45 pounds | | Average Customer Rating:
|  based on 14 reviews |
| | | | Customer Reviews: | |
Average Customer Review:
 ( 14 customer reviews )
Write an online review and share your thoughts with other customers.
Most Helpful Customer Reviews
18 of 18 found the following review helpful:
 "quite simply the most advanced product development book you can buy"Jul 15, 2009
By foobar
If you've ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Reinertsen is the book for you. It's quite simply the most advanced product development book you can buy.
For those who hunger for a rigorous approach to managing product development, Donald Reinertsen's book is epic. Myths are busted on practically every page, even myths that are associated with lean/agile. For example, take the lean dictum of working in small batches. I push this technique quite often, because traditional product development tends to work in batches that are much too large. Yet it's not correct to say that batch sizes should be as small as possible. Reinertsen explains how to calculate the optimal batch size from an economic point of view, math and all. It's wonderful to have an author take these sorts of questions seriously, instead of issuing yet another polemic.
The book is structured as a series of principles, logically laid out and briefly discussed - 175 in all. It moves at a rapid clip, each argument backed up with the relevant math and equations: marginal profit, Little's law, Markov processes, probability theory, you name it. This is not for the faint of heart.
The use of economic theory to justify decisions is a recurring theme of the book. Its goal is to help us recognize that every artifact of our product development process is really just a proxy variable. Everything: schedules, efficiency, throughput, even quality. In order to trade them off against each other, we have to convert their impact into economic terms. They are all proxies for our real goal, maximizing an economic variable like profit or revenue. Therefore, in order to maximize the true productivity (aka profitability) of our development efforts, we need to understand the relationships between these proxy variables.
[...]
12 of 12 found the following review helpful:
Challenges Orthodox Thinking On Every SideAug 12, 2010
By Maurice Hagar
"Project Leadership Coach & Trainer"
I won't repeat what others have said except that this new standard on lean product and software development challenges orthodox thinking on every side and is required reading. It's fairly technical and not an easy read but well worth the effort.
For the traditionalist, add to cart if you want to learn:
- Why prioritizing work "on the basis of project profitability measures like return on investment (ROI)" is a mistake
- Why we should manage queues instead of timelines
- Why "trying to estimate the amount of work in queue" is a waste of time
- Why our focus on efficiency, capacity utilization, and preventing and correcting deviations from the plan "are fundamentally wrong"
- Why "systematic top-down design of the entire system" is risky
- Why bottom-up estimating is flawed
- Why reducing defects may be costing us money
- Why we should "watch the work product, not the worker"
- Why rewarding specialization is a bad idea
- Why centralizing control in project management offices and information systems is dangerous
- Why a bad decision made rapidly "is far better" than the right decision made late and "one of the biggest mistakes a leader could make is to stifle initiative"
- Why communicating failures is more important than communicating successes
For the Agilist, add to cart if you want to learn:
- Why command-and-control is essential to prevent misalignment, local optimization, chaos, even disaster
- Why traditional conformance to a plan and strong change control and risk management is sometimes preferable to adaptive management
- Why the economies of scale from centralized, shared resources are sometimes preferable to dedicated teams
- Why clear roles and boundaries are sometimes preferable to swarming "the way five-year-olds approach soccer"
- Why predictable behavior is more important than shared values for building trust and teamwork
- Why even professionals should have synchronized coffee breaks
And the list goes on and on and on.
My favorite sections are Reducing Batch Size, which I use in my Agile courses, The Human Side of Feedback, and Achieving Decentralized Control, on "what we can learn from military doctrine."
Mind-expanding! Bonus: the author includes his email address and promptly responds to inquiries.
11 of 11 found the following review helpful:
Must readJan 28, 2010
By Michael T. Nygard
"Systems Thinker"
I read a lot of books. This is the most important one I've read in 10 years.
Reinertsen synthesizes several tough subject areas: queuing, ToC, Lean, and Real Options. There's rigor here, but it's incredibly accessible and presented in a set of concise principles.
I've bought copies to hand out, and I'm promoting this as a way to put business, technology, and marketing all on the same page. If we can all talk about the cost of delay, then all kinds of emotion-based debate just evaporates.
6 of 6 found the following review helpful:
Important book on product developmentJun 20, 2009
By David Walden
Don Reinertsen has written two of the three books I recommend
when someone asks me what to read about product development.
He wrote Managing the Design Factory and co-authored (with
Preston Smith) Developing Products in Half the Time: New Rules,
New Tools (2nd Edition). (The third book I recommend is the
first half of Kiyoshi Uchimaru's TQM for Technical Groups.)
Reinertsen has now written an important new book, The Principles of
Product Development Flow -- Second Generation Lean Product
Development. On page 1 of this book, Reinertsen states his ambition
for the book: "I believe that the dominant paradigm for managing
product development is fundamentally wrong....I believe a new
paradigm is emerging, one that challenges the current orthodoxy of
product development. I want to help accelerate the adoption of this
new approach. I believe I can do this by helping people understand
it. That is the purpose of this book."
I agree that practices like the phase gate review process are a
mistake (and counter productive in even more ways than Reinertsen
lists). My impression from my years leading development organizations
is that the developers themselves also thought much of current
practice was misguided, but they were stuck with what is claimed to
be "best practice."
Reinertsen's book does not give a new process for product
development. Rather, he provides explanations of what is wrong with
current practice, a discussion of eight general "themes" for
improvement, and 175 principles (divided among the eight themes) upon
which to base one's thinking as one develops one's own product
development system.
Buy the book. It is excellent. It will help you figure out how to do
product development better in your own organization.
4 of 4 found the following review helpful:
 Practical GuideJul 29, 2010
By Bob F, measurement guy
"Flow" digests the theory in "Managing the Design Factory (MtDF)" into a set of principles. I would suggest you read "Managing the Design Factory" first so you get a solid foundation for the principles. "Flow" is handy because it can be used as a quick reference. IF you have a question of how or why to apply a principle then you should dig back into the first book.
In my review of MtDF I observe that this earlier book covers a bit of queuing theory. The newer book leaves out nearly all of the theory. Still the summary of the principles is valuable. I'm happy I bought the book.
See all 14 customer reviews on Amazon.com
| | |
|
