Found 13 comments on HN
jrs235 · 2018-05-22 · Original thread
The Principles of Product Development Flow: Second Generation Lean Product Development
knightofmars · 2018-04-05 · Original thread
The Principles of Product Development Flow: Second Generation Lean Product Development

by Donald G. Reinertsen

jrs235 · 2018-02-03 · Original thread
The one I'm about to finish: The Principles of Product Development Flow: Second Generation Lean Product Development [1]

Wish I had read this years ago! I think every developer can benefit greatly from understanding these principles. Plus if they were more widely known and adopted it would be easier to get other managers to go along with them.

[1] (affiliate link)

knightofmars · 2016-10-03 · Original thread
I second this. Additionally, get a grip on your queues!

I have yet to find a better text on how to properly manage software projects than, "The Principles of Product Development Flow: Second Generation Lean Product Development"[0].


I recently read "The Principles of Product Development Flow: Second Generation Lean Product Development"[1] that was recommended to me.

Some of it was familiar. Some of it was new. The language used and how the book articulates the reasoning behind various strategies has been invaluable to me in expressing to others why something is a tractable problem as opposed to an unavoidable one that is just the cost of doing business.

To date I have not succeeded in getting anyone to read it though.


ianmcgowan · 2015-05-15 · Original thread
You may not have control over things like scope, timeframe, budget, "resources" (how I hate that word), but be expected to meet an arbitrary deadline. Get used to that. As sjg007 says, double any estimates you get, and don't confuse effort with duration. A task may require 4 hours of effort, but take 2 weeks to complete.

Google "planning fallacy", or see In general getting a list of tasks together and thinking you have a handle on what it will take is a delusion. Trust your gut.

These books shifted my thinking on why some projects work out and others are disasters.

* *

You could go the PMP route, I suppose. And get used to MS Project, which is a tool of the devil, but a necessary evil.

tmoullet · 2015-03-11 · Original thread
Finally an HN question that I can respond to!

I would recommend reading this book for a very good, but broad and high level intro:

This will cover topics like BOMs, MOQ, Safety Stock, Inventory strategy, warehousing etc.

Next I would recommend reading up on the following phrases: "product development" and "new product introduction" / "NPI"

Lean training/reading never hurts either. Note: this is supply chain lean vs "lean start up".

ianmcgowan · 2013-10-23 · Original thread
This is true, but not intuitive or readily explainable to "people" (usually senior management, hence the quotes :).

A great read on the subject of batch sizes and limiting WIP:

reginaldo · 2012-07-31 · Original thread
The book linked from the show is The Principle of Product Development Flow: Second Generation Lean Product Development.

Link (no affiliates):

deyan · 2011-09-16 · Original thread
Thanks, I will check those out.

To add: I highly recommend Principles of Product Development Flow ( - incredibly difficult book to read (i.e. lots of good but dense information) but it explains well the underlying principles - and thus goes beyond the buzzwords.

leegonzales · 2011-03-13 · Original thread
The realization which the proponents of lean products and software have had is that there are many strategies which have proven incredibly effective in other domains and that they can also be used to make products, business models and ultimately organizations better, faster and cheaper.

Simply put lean startups result from the combination of lean manufacturing principals and maneuver warfare (agility) principals combined and used in business. Which if you want to boil it down further could be thought of as using the scientific method as quickly and efficiently as possible to create organizations and products where teams have fully adopted a culture of continuos improvement.

Lean is probably best known for its ability to enable Toyota to be the amazing manufacturing organization they have been (ignoring recent growth related fuckups). See the book Lean Thinking or the many Lean Software books to see the ways in which people have translated Lean concepts to software development. Of course if you want to really grok lean in the context of making products you should study

Agile principals as codified by the god father of agile strategic thinking, John Boyd would be the other crucial element to lean startups. He is famous for driving maneuver warfare doctrine into the US military establishment and codifying some of the most advanced strategies and concepts regarding the nature of competition, agility and strategy. If you have seen the OODA loop or heard the phrase operating inside the enemies decision cycle then you have seen his work in action. See the book Certain to Win by Chet Richards for a good primer on Boyds work.

These concepts rigorously and intentionally applied to developing products, teams and companies are IMO what makes a startup lean.

And of course if you are interested, you can also read Eric Ries or Steve Blanks blogs.

Get dozens of book recommendations delivered straight to your inbox every Thursday.