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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

8 Introduction<br />

are different, but they still have a lot in common. It is this commonality that<br />

we are going to explore in this book. Both st<strong>and</strong>ards have large followings<br />

in the United States <strong>and</strong> internationally. They are based on predecessor<br />

st<strong>and</strong>ards created in the late 1980s <strong>and</strong> early 1990s. Both st<strong>and</strong>ards are often<br />

required by contracts. Customer representatives (or third-party organizations<br />

that are specifically chartered for appraising st<strong>and</strong>ard implementation) may<br />

examine <strong>and</strong> evaluate their implementation.<br />

When confronted with requirements for following multiple st<strong>and</strong>ards,<br />

most organizations will implement one st<strong>and</strong>ard, perform an appraisal to<br />

confirm that the st<strong>and</strong>ard was satisfactorily followed, <strong>and</strong> then address the<br />

next st<strong>and</strong>ard.<br />

Some organizations, in their quest for the shortest possible time to achieve<br />

<strong>ISO</strong> registration or a CMM ® maturity level, will opt for the cheapest <strong>and</strong><br />

the least complicated approach. They intend to revisit their <strong>process</strong>es after<br />

achieving registration or <strong>process</strong> maturity level, but in practice this is seldom<br />

done.<br />

By analyzing the requirements of <strong>ISO</strong> <strong>9001</strong>:<strong>2000</strong> <strong>and</strong> the <strong>CMMI</strong> ® ,we<br />

see that they have many commonalties that can be exploited. If we carry<br />

this concept further, by adding more <strong>and</strong> more details, we realize that we<br />

have to account for differences between the maturity of organizations that<br />

plan to implement those st<strong>and</strong>ards, their commitment to those st<strong>and</strong>ards, <strong>and</strong><br />

their willingness to accept necessary organizational changes. We analyzed<br />

several potential approaches <strong>and</strong> selected one that enables efficient <strong>process</strong><br />

<strong>improvement</strong> implementation <strong>and</strong> capitalizes on the synergy between the<br />

st<strong>and</strong>ards.<br />

What unifies those two frameworks When analyzing the principles on<br />

which they were built, we noticed that they have more similarities than<br />

differences. We were able to use the strengths of one st<strong>and</strong>ard to counter<br />

the weaknesses of the other, thus further unifying the <strong>process</strong> <strong>improvement</strong><br />

approach. For example, both documents are based on the following:<br />

• Process approach;<br />

• Full life cycle;<br />

• Integration of management <strong>and</strong> production <strong>process</strong>es;<br />

• <strong>Systematic</strong> planning;<br />

• Extensive <strong>process</strong> <strong>and</strong> product measurements;<br />

• Explicit requirement for the resources needed to implement the<br />

<strong>process</strong>es;

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

Saved successfully!

Ooh no, something went wrong!