CONCLUSIONS

Documentation is always required for product development efforts, and viewing 'Product Development Through the Eyes of Documentation' will ensure support for your specific product while adhering to the Guidelines-Of-Business and demands of the Groups-Of-Influence. Anything more is unnecessary and is fodder for bureaucracy.

Friend, Bill once said, "Lawyers always advise that if you can agree to something then you should capture it in an agreement or by a handshake. Likewise, in product development if you can think of something that is important to the product, market, and project then document it." Now we know why this is such sage advice.

Declaring the appropriate documents can take some time and require experienced help, but when established documentation will greatly add to the strength and direction to your development project.

---

The opinions expressed in this article are those of the author only and do not represent the views of the Techman/Kanata or of any of its directors, officers or employees. The author, Mr. Richard (Dick) Haney, can be reached at RichardMHaney@cs.com

For other articles by Dick Haney refer to the following link: http://www.techmankanata.com/dev/author/Richard-Dick-Haney/6.htm