08.02.2015 Views

Systematic process improvement using ISO 9001:2000 and CMMI

Systematic process improvement using ISO 9001:2000 and CMMI

Systematic process improvement using ISO 9001:2000 and CMMI

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4.1 <strong>ISO</strong> <strong>9001</strong>:<strong>2000</strong> 63<br />

Principle 4: <strong>process</strong> approach<br />

Any activity or set of activities that transforms inputs to outputs can be<br />

considered a <strong>process</strong> [4]. In any organization, many <strong>process</strong>es interact in<br />

various ways during the product life cycle. The output of one <strong>process</strong> may<br />

feed another <strong>process</strong> or <strong>process</strong>es. Thus, work products produced by one<br />

<strong>process</strong> may impact the work products of the downstream <strong>process</strong>es. When<br />

consuming resources, a <strong>process</strong> must add value to the input. If it does not<br />

add value, it should be changed or even eliminated. The <strong>process</strong> has to be<br />

captured, documented, planned, given adequate resources, measured, <strong>and</strong><br />

improved. The purpose of the <strong>process</strong> <strong>and</strong> responsibility for its implementation<br />

must be clearly defined. The impact of the <strong>process</strong> on the final product,<br />

customers, <strong>and</strong> other stakeholders must be understood.<br />

Principle 5: system approach to management<br />

A system is a set of interrelated or interacting elements or <strong>process</strong>es. Therefore,<br />

an organization can be considered to be a system of interrelated <strong>and</strong><br />

interacting <strong>process</strong>es. From identification of customer requirements to delivery<br />

of the final product, the <strong>process</strong>es interact, transforming inputs into<br />

outputs, consuming resources, <strong>and</strong> adding value. Therefore, each <strong>process</strong><br />

may affect other <strong>process</strong>es in the system. To succeed, an organization must<br />

be able to analyze its <strong>process</strong>es <strong>and</strong> their interactions, determine if they are<br />

efficient <strong>and</strong> effective, <strong>and</strong> make corrections when required. At the same<br />

time, the roles <strong>and</strong> responsibilities associated with each <strong>process</strong> must be<br />

understood <strong>and</strong> optimized to achieve corporate goals <strong>and</strong> objectives.<br />

Principle 6: continual <strong>improvement</strong><br />

<strong>ISO</strong> 9000:<strong>2000</strong> emphasizes continual 1 <strong>improvement</strong>. A companion st<strong>and</strong>ard,<br />

<strong>ISO</strong> 9004, is dedicated to the principle of continual <strong>improvement</strong>. This principle<br />

requires an organization to set continual <strong>improvement</strong> as one of its<br />

permanent objectives; note, however, that <strong>ISO</strong> does not provide guidelines<br />

for achieving this objective. Continual <strong>improvement</strong> can reduce rework <strong>and</strong><br />

scrap, reduce variation, <strong>and</strong> improve the ability to react quickly to emerging<br />

development opportunities. It is up to each company to determine where<br />

<strong>and</strong> when <strong>improvement</strong>s will occur—at the component, department, or<br />

division levels, or across the whole organization. Each organization must<br />

1. <strong>ISO</strong> uses the word continual versus continuous. Continual means repeated regularly, recurring, whereas continuous<br />

means without interruption. We will use these two terms interchangeably, with the emphasis where appropriate.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!