Can you comment on (or does the book go into) using DFSS in software development (lean or otherwise).
The book does not cover much on DFSS, even though it does go into classic data-driven process improvement processes in some depth.
The reason is that I personally find many DFSS environments to be data-driven and variation adverse, rather than purpose-driven and waste adverse. (Waste and variation are NOT the same!)
I like the DFSS tools quite a bit - and I used them for many years before they made it into the DFSS toolkit. I am not so sure, however, that using all of the VOC (voice of the customer) tools necessarily gives you a winning product (in fact I have seen lots of evidence to the contrary). There is nothing wrong with the DFSS tools, but there can be a lack of balance with insight and intuition. I've seen a shift in this balance destroy a great product development environment, so I'm a bit gunshy.
Good tools in the hands of good people will usually produce great results. Good tools used in a process designed to factor out the insights and intuition of intelligent people will usually fail.
Author of Lean Software Development, Implementing Lean Software Development, and Leading Lean Software Development
Juan Rolando Prieur-Reza
posted 9 years ago
Thanks. Your writing here expresses the kind of depth and clarity that now makes me want to read your book.
Juan Rolando Prieur-Reza, M.S., LSSBB, SCEA, SCBCD, SCWCD, SCJP/1.6, IBM OOAD, SCSA
And then we all jump out and yell "surprise! we got you this tiny ad!"
create, convert, edit or print DOC and DOCX in Java