I am a design quality engineer working on a new product development project. We are currently working on putting together the development plan which defines all the project design deliverables for the DHF. One deliverable of this includes the quality strategy for the project. The basis of this document is defined as a plan to assure all required documents, etc to show the design was completed in compliance with our QMS. This is a very broad description of what this document should contain. I am looking for advice on what information should be included in this document and to what level of detail.
Thanks!
It's best to keep the plan as pragmatically 'value add' as possible within the context of your corporation's process and knowledge-base maturity levels. Dependent upon these key drivers, such a plan can take significantly different form - and provide drastically different value add potentials. For example, if the corporation's DNA is major-league in the areas of continuous improvement, diligence, process discipline, achieving design excellence, and the design effort has a mix of contributors with gaps in their personal bodies-of-knowledge and experience, then it is appropriate and desirable to frame the plan with details which will assist in optimizing results for design activities and work products. Conversely, if the corporate vision for the preceding operational attributes is low / dim, then it may be more appropriate to itemize the required tasks in a simplistic form, along with their relationship to other tasks, work-products, and project execution control points. In either case, it is both reasonable and appropriate to delineate tasks and deliverables in a framework like this:
* TASK / ACTIVITY
> Inputs
> Processing Criteria / Requirements
> Outputs (Deliverables)
SIDE NOTE: The human race has a much higher propensity to make significant and meaningful change for improvement in an environment of desperation rather than inspiration.
Regards & Peace Out