Your Reliability Engineering Professional Development Site
In my last article, we reviewed a proposed Product Life Cycle process, which starts with a “Define” phase. In the “Define” phase, we are defining the project as well as the product.
We previously discussed the ‘technical leg’ of this process with the market analysis, identifying customer needs, product requirements, verification and validation, etc. [Read more…]
In my previous article we covered the advantages of a phase and gate structure for new product development. Now we can discuss some proposed phase names for a new product development or product life cycle (PLC) process.
An organization may have an existing PLC process ‘baked-in’ to their culture and process documentation. Accordingly, there’s a wide range of PLC phase names, all of which are likely acceptable and based on solid reasoning.
In previous articles we defined an element of lean as a phase and gate structure for new product development. This assumes a waterfall approach to the project (versus agile product development).
A new product life cycle phase gate structure might entail, for example: “Definition, Concept, Design, Verification, Qualification, Production and End-of-Life”. (Your organization might decide on different phase names.)
There’s an apparent contradiction in using a waterfall project approach and calling it lean project management, however. A goal of any lean process is to work toward ‘single piece’ or continuous flow: agile product development is more like ‘single piece flow’ of information, versus waterfall which is more like ‘batch processing’ of information.
My last article covered a scalable model for lean product development depending on the number of projects and technical objectives.
Let’s start with the foundational elements from this model:
In my previous article we established the lean product development goal statement as:
We then derived high-level objectives as follows: