In real design, there’s more feedback than in the first game above, of course. The point-based approach proposes a solution, and then iterates by revising to a different point. Instead, let’s use a “set-based” approach: Is it animal, vegetable or mineral? Animal. You probably know the game of 20 Questions. You can also see the Poppendiecks’ Implementing Lean Software Development for more on this idea. Reading the book The Toyota Product Development System has me considering these notions again. They see the approach as set-based because it’s built around the idea of finding a solution as the intersection of a set of feasible choices, and it’s concurrent because teams are trying to work “all at once,” not in a sequential, hand-off style. People trying to describe Toyota’s product development process seem to have settled on “set-based concurrent engineering” as a term for one key part. This lets several groups work at the same time, as they converge on a solution. One of the ideas in lean product development is the notion of set-based concurrent engineering: considering a solution as the intersection of a number of feasible parts, rather than iterating on a bunch of individual “point-based” solutions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |