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
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
164 Transitioning from Legacy St<strong>and</strong>ards<br />
obtaining commitment from relevant stakeholders, both internal <strong>and</strong> external.<br />
It also distinguishes between an informal go-ahead <strong>and</strong> formal full<br />
commitment to the plan.<br />
Project Monitoring <strong>and</strong> Control (PMC)<br />
The PMC PA parallels the PP PA <strong>and</strong> does not add any major requirements<br />
to the CMM ® SPTO KPA. It seems a little crisper than the CMM ® —requirements<br />
are specified for monitoring commitments, monitoring stakeholder<br />
involvement (explicitly required in SG 1), <strong>and</strong> managing corrective actions<br />
to closure (SG 2). This second specific goal is significant because it requires<br />
that issues identified by verification <strong>and</strong> validation <strong>process</strong>es, reviews, deviations<br />
from project plans, or changes in risk status are gathered <strong>and</strong> analyzed.<br />
Corrective actions are then taken <strong>and</strong> managed. These requirements are<br />
scattered over many SPTO activities in the CMM ® (such as activities 5 through<br />
9). It is important to note that this PA supports GP 2.8, Monitor <strong>and</strong> Control<br />
the Process, in the other <strong>CMMI</strong> ® PAs.<br />
It is interesting that while the CMM ® does not address planning of the<br />
project tracking <strong>process</strong>, except by inference in SPP activity 6 <strong>and</strong> later in<br />
OPD activity 2 <strong>and</strong> Integrated Software Management (ISM) activity 1, it is<br />
required by the <strong>CMMI</strong> ® by virtue of GP 2.2.<br />
Supplier Agreement Management (SAM)<br />
The SAM PA replaces <strong>and</strong> exp<strong>and</strong>s the Software Subcontract Management (SSM)<br />
KPA of the CMM ® . It extends subcontract management to include management<br />
of product acquisition from suppliers <strong>using</strong> formal agreements. Inhouse<br />
vendors <strong>and</strong> commercial vendors, including subcontractors, are distinguished<br />
<strong>and</strong> the PA can be extended to the acquisition of development tools<br />
<strong>and</strong> test environments. New <strong>process</strong>es to be addressed include determination<br />
of the type of acquisition, evaluation of COTS products to ensure they satisfy<br />
specified requirements, <strong>and</strong> transition of these products to the projects.<br />
Although most CMM ® SSM key practices can be traced to the <strong>CMMI</strong> ® ,it<br />
appears that this PA is more encompassing <strong>and</strong> more detailed in its requirements.<br />
Two specific practices, SP 1.1, Determine Acquisition Type, <strong>and</strong> SP 1.2,<br />
Select Suppliers, are not covered in the CMM ® . Similarly, several CMM ® practices<br />
dealing with the subcontractor’s project planning, QA, <strong>and</strong> CM activities<br />
are not addressed in the <strong>CMMI</strong> ® .<br />
Process <strong>and</strong> Product Quality Assurance (PPQA)<br />
The PPQA PA may appear, at first, to be more dem<strong>and</strong>ing than the CMM ®<br />
SQA KPA, but it has fewer practices <strong>and</strong> covers basically the same topics.