This webpage was compiled to serve those of you who are early adopters of CMMI-SVC (and are therefore familiar with version 0.5) to help you quickly understand the differences between version 0.5 and version 1.2.
Below you will find the following:
Version 0.5 was the pilot version available for comment. Version 1.2 is the result of improving version 0.5 based on the feedback from those who used and commented on the pilot draft.
Major improvements made during that time include the following:
A comparison between version 0.5 and version 1.2 is summarized in this table:
| CMMI-SVC, V1.2 | CMMI-SVC, V0.5 |
|---|---|
Part 1 is complete and written with all model users in mind. |
Part 1 is abbreviated and focused on pilot participants |
Part 3 is complete and includes references, acronyms, project participants, and the glossary. |
Part 3 is not included. |
The SSD process area is an addition (optional). |
The SSD, SCON, and OSM process areas are additions (optional). |
The model has 24 process areas. |
The model has 25 process areas. |
There are seven services-specific process areas:
|
There are eight services-specific process areas:
|
Generic practices are covered only in the Generic Goals and Generic Practices section. |
Generic practices are covered both in the Generic Goals and Generic Practices section and at the end of each process area. |
Service Delivery (SD) is staged at maturity level 2. |
Service Delivery (SD) is staged at maturity level 3. |
Strategic Service Management (STSM) is categorized as a Service Establishment and Delivery process area. |
Organizational Service Management (OSM) is categorized as a Process Management process area. |
There are additional integrated teaming practices in IPM and OPD. |
No integrated teaming practices are included. |
IRP is staged at maturity level 3. |
IRM is staged at maturity level 2. |
Preface
The preface of each model version serves a different purpose. The preface of version 0.5 directly addresses those piloting the model and describes how to send pilot feedback to the CMMI-SVC development team. The preface of version 1.2 introduces the final release of the model for use in process improvement.
Part 1 in version 0.5 is brief and addresses only the services-related content of the model. Part 1 in version 1.2 is much more detailed and describes the content of the entire model. No comparison files are provided for these chapters because they use different approaches to describing the model.
The Generic Goals and Generic Practices section of Part 2 is similar in both models. However, in version 1.2 generic practices and their elaborations are not present at the end of each process area as they are in version 0.5. Therefore, when reviewing the comparison redlines for the process areas listed below, notice that the generic goals and practices are removed. In version 1.2, the generic goals and practices are presented only in the Generic Goals and Generic Practices section of Part 2.
The following seven CMMI-SVC, V1.2 process areas are unique to the CMMI-SVC model. The entry for each process area describes the changes made as version 0.5 developed into version 1.2. Click on the process area name to see the version 0.5 to version 1.2 redline comparison of the process area contents.
Capacity and Availability Management (CAM)
The informative material in this process area was expanded and revised to clarify its purpose and details. The use of the phrase “baselines and models” was replaced with “service system representations” to differentiate this concept from process performance baselines and models. Throughout CAM, “analyze and monitor” was replaced with “monitor and analyze.” In the introductory notes, capacity and availability are explained and service system representations are defined.
Incident Resolution and Prevention (IRP)
The incident-related portions of the Incident Request Management (IRM) and Problem Management (PRM) process areas in version 0.5 were combined to form a new process area, Incident Resolution and Prevention (IRP). (The service request portions of IRM and PRM were incorporated into SD.) IRP practices help you prepare for incident management; identify, control, and address incidents; and analyze data to define approaches to resolving incidents (including workarounds). Use of the word “problem” as a special term was abandoned and instead descriptions of incidents and how they are addressed are used. How “underlying causes” relate to “root cause analysis” is explained. Incidents are no longer presented as problems to remove, instead incidents are addressed according to business and customer needs.
This process area was reorganized and revised for clarity and completeness. What is meant by “organization” was clarified. There are now three goals instead of four. SCON now discusses both essential functions and essential resources. SCON terminology and discussion has changed to focus on the establishment of service continuity plans, training to support service continuity, and the verification and validation of service continuity plans. SCON is no longer an optional process area.
This process area was moved from maturity level 3 to maturity level 2. SD was expanded to cover the establishment of service agreements, establishing a service delivery approach, preparing for service system operations, preparing a request system, and processing service requests. As mentioned before, the service request related practices (formerly in IRM) were moved to SD.
Service System Development (SSD)
The notes were expanded throughout this process area. The coverage of peer reviews was expanded to include more details. The use of “customer requirement” was replaced with “stakeholder requirement.” Verification and validation are more consistently discussed in SSD and references to “testing” were minimized since testing can be either verification or validation. SSD remains an optional process area.
Service System Transition (SST)
The name of this process area was changed from Service Transition (ST) to Service System Transition (SST) to emphasize the transition of the whole service system. SG3, Retire the Service System, was removed and retirement instead was covered at the informative level. The content of SST was also restructured to move some material from expected to informative and vice versa.
Strategic Service Management (STSM)
This process area was moved from the Process Management PA category to the Service Establishment and Delivery PA category. Its name was changed from Organizational Service Management (OSM) to Strategic Service Management (STSM) to emphasize its strategic nature and de-emphasize customer satisfaction, since customer satisfaction is only one of the drivers for developing strategic standard services. STSM is no longer an optional process area.
The following CMMI-SVC, V1.2 process areas are shared with other CMMI models. All but one of them are common to all CMMI models. (SAM is shared with CMM-DEV but is not included in CMMI-ACQ.) The entry for each process area describes the changes made as version 0.5 developed into version 1.2. Click on the process area name to see the version 0.5 to version 1.2 redline comparison of the process area contents.
Causal Analysis and Resolution (CAR)
The discussion in this process area was revised to consistently refer to “defects and problems.” This change affected the wording of goals and practices as well as informative material.
The revisions to this process area were either editorial or were in the informative material. There were no major changes.
Decision Analysis and Resolution (DAR)
The revisions to this process area were either editorial or were in the informative material. There were no major changes.
Integrated Project Management (IPM)
The specific practice, Establish Integrated Teams, was added to IPM (based on similar content in CMMI-ACQ). Other revisions to this process area were either editorial or were in the informative material.
The revisions to this process area were either editorial or were in the informative material. There were no major changes.
Organizational Innovation and Deployment (OID)
The revisions to this process area were either editorial or were in the informative material. There were no major changes.
Organizational Process Definition (OPD)
The specific practice, Establish Rules and Guidelines for Integrated Teams, was added to OPD (based on similar content in CMMI-ACQ). Other revisions to this process area were either editorial or were in the informative material.
Organizational Process Focus (OPF)
In SG2, “process improvements” was replaced with “process actions.” In SG3, “lessons learned” was replaced with “experiences.” Other revisions to this process area were either editorial or were in the informative material.
Organizational Process Performance (OPP)
The revisions to this process area were either editorial or were in the informative material. There were no major changes.
The revisions to this process area were either editorial or were in the informative material. There were no major changes.
Project Monitoring and Control (PMC)
The revisions to this process area were either editorial or were in the informative material. There were no major changes.
The specific practice, Establish the Project Strategy, was added to meet the strategic needs of planning. Other revisions to this process area were either editorial or were in the informative material.
Process and Product Quality Assurance (PPQA)
In this process area, the phrase “work products and services” was restated to be only “work products” because the meaning was confusing for service providers. This change affected the wording of goals and practices as well as informative material.
Quantitative Project Management (QPM)
The revisions to this process area were either editorial or were in the informative material. There were no major changes.
Requirements Management (REQM)
SG2, Establish Service Requirements Agreements, was removed from this process area and added to SD. Other revisions to this process area were either editorial or were in the informative material.
The revisions to this process area were either editorial or were in the informative material. There were no major changes.
Supplier Agreement Management (SAM)
In this process area, the SP 1.3 statement was changed to no longer refer to “formal agreements with the supplier” but instead to refer to “supplier agreements.” The SP 2.3 statement was revised to remove the phrase “of custom-made products” since suppliers of services are not clearly covered by the practice with this phrase. The phrase “as appropriate” was added to the SP 2.5 statement about ensuring transition of products because services cannot be stored and therefore this practice would not apply to services.
Version 0.5 did not include appendices whereas version 1.2 has all the appendices expected in a CMMI model, including references, acronyms, project participants, and a glossary.