Further thoughts by the author…

January 2002

"Should we do all this for every product we develop?"

The answer is no. How much you do use depends on the type of product and it's complexity. The suggestions in this article were actually 'a list of experience' from various development projects. 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.

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.

"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 (each of which you can not live without these days) 'live & survive' by well generated and maintained documentation, not by presumptions, beliefs, innuendoes, rumors, hearsay, notes on napkins or gossip. Therefore, find out exactly what documents you need for each dependency and make its generation and maintenance part of the development process.

View Complete Article