18 of 18 people found the following review helpful:
5.0 out of 5 stars
"quite simply the most advanced product development book you can buy", July 15, 2009
This review is from: The Principles of Product Development Flow: Second Generation Lean Product Development (Hardcover)
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.
[...]
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
11 of 11 people found the following review helpful:
5.0 out of 5 stars
Must read, January 27, 2010
This review is from: The Principles of Product Development Flow: Second Generation Lean Product Development (Hardcover)
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.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No
10 of 10 people found the following review helpful:
5.0 out of 5 stars
Challenges Orthodox Thinking On Every Side, August 11, 2010
This review is from: The Principles of Product Development Flow: Second Generation Lean Product Development (Hardcover)
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.
Help other customers find the most helpful reviews
Was this review helpful to you? Yes
No