IDEAS

You should (1) review what is known and presumed about a product and its associated processes that are to be developed and (2) take from the article's suggestions those items, which will economically and efficiently provide the best defense against problems. No one can really predict the future success of a product, but past experience can be applied to lessen the chances of project and/or product failure. For a discussion about how to help assist a product's success during a product development effort see Product Development From the Top - So… I have a Product Idea… Now what?

Also, no one person can be an expert in all stages of product development. There is knowledge and experience in all parts of a company. This expertise must be used in the planning process to help hedge against failure. 'Ego management' (i.e. one person doing all the thinking and planning because that person 'knows the way') is not the best methodology to counter potential failure mechanisms.

Another major issue that comes up is…

    "Is all that documentation necessary?"

Again, the answer is no, because it depends on the type of product and it's complexity. Remember that (1) intra/inter-project communications, (2) regulatory agencies and (3) manufacturers are important parts of product development today. 'Live & survive' by well-generated and maintained documentation, not by presumptions, beliefs, innuendoes, rumors, hearsay, notes on napkins, some engineer's gray matter or gossip. Therefore, find out exactly what documents you need for each dependency and make its generation and maintenance part of the development process.



The GPEP process can be as complicated as one would like. A successful implementation, however, requires that the process be as simple as possible, yet be able to cover all issues which are pertinent to the company business, the development process, the specific product, relevant agencies, and the users and market. This process is different for every company and this is where experience is vital for proper implementation.


 
JUMP TO PAGE
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

©1999, 2005, Richard M. (Dick) Haney
BACK TO: RICHARD (DICK) HANEY   IDEAS