Re: Design vs. Manufacturing

I'm of the opinion that this classic problem is the problem we are 
trying to solve in "lean software" and that if it can be solved for 
software, then the whole engineering community will benefit from it 
as ideas will be much more transferable to general product design 
than to manufacturing (and vice versa).

There is plenty of good work being done in quantitative ways to 
elicit requirements, and their importance. Look for Triz and 
Repertory grids on Google.

In other engineering disciplines, the amount of change is kept at a 
manageable level by restricting sign off and requirements discussions 
to the professional (or "chartered") engineers, and I think software 
would certainly benefit from that.

This is reflected a bit in the excellent article on Mary's site on 
Lean Construction here: http://www.poppendieck.com/construction.htm 
where the basic design is agreed, then building begun, then details 
like electrical fittings added after consultation with the customer. 
This analogy is more akin to software since it is a one off with at 
least some change between every project. 

--- In [email protected], "Bill Walton" 
<bill.walton@j...> wrote:
> Does anyone know of any writings that specifically address the 
differences (particularly with respect to ability to predict / define 
in advance what "done" will be, process improvement, etc.) between 
Product Manufacturing vs. Product Design / Development?
> 
> Thanks,
> Bill


To unsubscribe from this group, send an email to:
[email protected]

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/