This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
A Proce ss Area is a cluster of related practice s in an area that, when implemented collectively, satisfy a se t of g oals considered important for making sig nificant improvement in that area. All CMMI process areas arecommon to both continuous and staged representations.
The continuous representation enables the org anization to choose the focus of its proce ss improve ment efforts by choosing those proce ss areas, or se ts of interre lated process are as, that best benefit the org anization and its business objectives. Although there are some limits on what an org anization can choose be cause of thedependencies among proce ss areas, the org anization has considerable free dom in its selection.
Once you select the process areas, you must also select how much you would like to improve the processesass ociated with those process areas (i.e., select the appropriate capability level). Capability levels and genericg oals and practice s support the improve ment of process es in individual process areas.
Conversely, you will see that the staged represe ntation encourag es you to always look at process areas in thecontext of the maturity leve l to which they belong . T he process areas are org anize d by maturity leve ls toreinforce this concept. When you use a process area, you use the entire process area: all goals and all practices.
The CMMI Proce ss Are as (PAs) can be g rouped into the following four categ ories to understand theirinteractions and links with one another re g ardless of their defined leve l:
Process Management
Project Management
Engineering
Support
Each proce ss area is defined by a se t of goals and practice s. T here are two categ ories of goals and practice s:
Generic goals and practices: They are part of every process area.
Spec ific g oals and practices: They are specific to a g iven process area.
A process are a is satisfied when company proce sses cover all of the g eneric and specific g oals and practice s forthat proce ss area.
Generic goals and practices:
Generic g oals and practices are a part of every process area.
NOTATIONS:GG --> Generic Goals and GP --> Generic Practice
GP 2.10 Review Status with Hig her Le vel Manag ement
GG 3 Institutionalise a Defined Process
GP 3.1 Establish a De fined Proces s
GP 3.2 C ollect Improvement Information
GG 4 Institutionalise a Quantitatively Manag ed Process
GP 4.1 Establish Quantitative Objectives for the Proce ss
GP 4.2 Stabilise Subprocess Performance
GG 5 Institutionalise an Optimising Proce ss
GP 5.1 Ensure Continuous Process Improvement
GP 5.2 Correct Root Causes of Problems
Common Features:
The common features are attributes that indicate whether the implementation and institutionalization of a key process are a is e ffective, repeatable, and lasting . The five common features are listed below:
Commitment to Perform: Commitment to Perform describes the actions the org anization must taketo ensure that the proce ss is established and will endure. Commitment to Perform typically involvesestablishing org anizational policies and se nior manag ement sponsorship.
Ability to Perform: Ability to Perform describes the preconditions that must exist in the project ororg anization to implement the software proce ss competently. Ability to Perform typically involvesresources, org anizational structures, and training .
Activities Performed: Activities Performed de scribes the roles and procedures necess ary toimplement a key process area. Activities Performed typically involve establishing plans and proce dures,performing the work, tracking it, and taking corrective actions as nece ss ary.
Measurement and Analysis: Measurement and Analysis describes the need to measure the processand analyze the measurements. Measurement and Analysis typically includes examples of themeasurements that could be taken to determine the status and effectiveness of the Activities Performed.
Verifying Implementation: Verifying Implementation describes the steps to ensure that the activities
are performed in compliance with the process that has been established. Verification typically encompass es reviews and audits by manag ement and software quality assurance .
The practices in the common feature Activities Performed describe what must be implemented to establish aprocess capability. The other practice s, taken as a whole, form the basis by which an org anization caninstitutionalize the practice s described in the Activities Pe rformed common feature .
Process Areas Detail:
The CMMI contains 22 process areas indicating the aspe cts of product deve lopment that are to be covered by company processes .
The purpose of Causal Analysis and Resolution (CAR) is to identify causes of defects and other problemsand take action to prevent them from occurring in the future .
Specific Practices by Goal
SG 1 Determine Causes of Defects
SP 1.1 Se lect Defect Data for Analysis
SP 1.2 Analyze Causes
SG 2 Addres s C ause s of Defects
SP 2.1 Implement the Action Proposals
SP 2.2 Evaluate the Effect of Chang es
SP 2.3 Record Data
2. Configuration Manag ement (CM)
A Support proce ss area at Maturity Level 2
Purpose
The purpose of Configuration Management (CM) is to establish and maintain the integ rity of work productsusing config uration identification, config uration control, config uration status accounting , and config uration audits.
Specific Practices by Goal
SG 1 Establish Baselines
SP 1.1 Ide ntify Config uration Items
SP 1.2 Establish a Config uration Management System
SP 1.3 Create or Release Baselines
SG 2 Track and Control Chang es
SP 2.1 Track Chang e Re quests
SP 2.2 Control Config uration Items
SG 3 Establish Integ rity
SP 3.1 Establish Config uration Manag ement Records
SP 3.2 Pe rform Config uration Audits
3. Decision Analysis and Resolution (DAR)
A Support proce ss area at Maturity Level 3
Purpose
The purpose of Decision Analysis and Resolution (DAR) is to analyze possible decisions using a formalevaluation proce ss that evaluates identified alternatives ag ainst established criteria.
A Proje ct Manag ement process are a at Maturity Level 3
Purpose
The purpose of Integ rated Projec t Management +IPPD (IPM) is to establish and manag e the projectand the involvement of the re levant stakeholders according to an integ rated and defined process that is tailore dfrom the organization's set of standard processes.
Specific Practices by Goal
SG 1 Use the Proje ct's Defined Process
SP 1.1 Establish the Project's De fined Proces s
SP 1.2 Use Org anizational Proce ss Assets for Planning Proje ct Activities
SP 1.3 Establish the Proje ct's Work Environment
SP 1.4 Integ rate Plans
SP 1.5 Manage the Proj ect Using the Integ rated Plans
SP 1.6 Contribute to the Org anizational Proce ss Assets
SG 2 Coordinate and Collaborate with Relevant Stakeholders
SP 2.1 Manage Stakeholder Involvement
SP 2.2 Manage Dependencies
SP 2.3 Resolve Coordination Issues
IPPD Addition:
SG 3 Apply IPPD Principles
SP 3.1 Establish the Proje ct's Shared Vision
SP 3.2 Establish the Integ rated T eam Structure
SP 3.3 Allocate Requirements to Integ rated T eams
SP 3.4 Establish Integrated Teams
SP 3.5 Ensure C ollaboration among Interfacing Teams
5. Measurement and Analysis (MA)
A Support proce ss area at Maturity Level 2
Purpose
The purpose of Measurement and Analysis (MA) is to develop and sustain a measurement capability that isused to support manag ement information needs.
SP 1.3 Specify Data Collection and Storage Procedures
SP 1.4 Specify Analysis Procedures
SG 2 Provide Measurement Results
SP 2.1 Collect Meas urement Data
SP 2.2 Analyze Measurement Data
SP 2.3 Store Data and Results
SP 2.4 Communicate Results
6. Org anizational Innovation and Deployment (OID)
A Proce ss Manag ement process are a at Maturity Level 5
PurposeThe purpose of Org anizational Innovation and Deployment (OID) is to select and deploy incre mentaland innovative improvements that measurably improve the org anization's proce sses and technolog ies. Theimprove ments support the org anization's quality and process-performance objectives as derived from theorg anization's business objectives.
Specific Practices by Goal
SG 1 Select Improvements
SP 1.1 Collect and Analyze Improvement Propos als
SP 1.2 Identify and Analyze Innovations
SP 1.3 Pilot Improvements
SP 1.4 Select Improvements for De ployment
SG 2 Deploy Improvements
SP 2.1 Plan the De ployment areas
SP 2.2 Manage the De ployment
SP 2.3 Measure Improvement Effects
7. Organizational Process Definition +IPPD (OPD)
A Proce ss Manag ement process are a at Maturity Level 3
Purpose
The purpose of Org anizational Process Definition +IPPD (OPD) is to establish and maintain a usablese t of org anizational proce ss assets.
Specific Practices by Goal
SG 1 Establish Organizational Process Assets
SP 1.1 Establish Standard Proce sses
SP 1.2 Establish Life-Cycle Model Descriptions
SP 1.3 Es tablish Tailoring Criteria and Guidelines
SP 1.4 Establish the Org anization's Measurement Repository
SP 1.5 Establish the Organization's Process Asset Library
IPPD Addition:
SG 2 Enable IPPD Management
SP 2.1 Establish Empowerment Mechanisms
SP 2.2 Establish Rules and Guidelines for Integ rated T eams
SP 2.3 Balance Team and Home Org anization Responsibilities
8. Org anizational Process Focus (OPF)
A Proce ss Manag ement process are a at Maturity Level 3
Purpose
The purpose of Organizational Process Focus (OPF) is to plan and implement org anizational proce ssimprovement base d on a thorough understanding of the curre nt streng ths and weaknesses of the org anization's
processes and process assets.
Specific Practices by Goal
SG 1 De termine Proce ss Improve ment Opportunities
SP 1.1 Establish Organizational Process Needs
SP 1.2 Appraise the Org anization's Proce ss es
SP 1.3 Identify the Org anization's Proce ss Improve ments
SG 2 Plan and Implement Process Improvement Activities
SP 2.1 Establish Process Action Plans
SP 2.2 Implement Process Action Plans
SG 3 Deploy Org anizational Proce ss Assets and Incorporate Lessons Learned
SP 3.1 Deploy Org anizational Proces s Assets
SP 3.2 Deploy Standard Proce ss es
SP 3.3 Monitor Implementation
SP 3.4 Incorporate Proce ss -Related Experience s into the Org anizational Process Assets
9. Org anizational Process Performance (OPP)
A Proce ss Manag ement process are a at Maturity Level 4
Purpose
The purpose of Organizational Process Performance (OPP) is to e stablish and maintain a quantitativeunderstanding of the performance of the org anization's set of standard proce sses in support of quality andprocess -performance obje ctives , and to provide the process performance data, base lines , and models toquantitatively manag e the org anization's projects.
Specific Practices by Goal
SG 1 Establish Pe rformance Base lines and Mode ls
SP 1.3 Establish Quality and Process Performance Objectives
SP 1.4 Establish Proce ss Performance Baselines
SP 1.5 Establish Process Performance Models
10. Org anizational Training (OT)
A Proce ss Manag ement process are a at Maturity Level 3
Purpose
The purpose of Org anizational Training (OT) is to develop the skills and knowledg e of people so they canperform their roles effectively and efficiently.
Specific Practices by Goal
SG 1 Es tablish an Org anizational Training Capability
SP 1.1 E stablish the Strateg ic T raining Needs
SP 1.2 Determine Which Training Needs Are the Responsibility of the Org anization
SP 1.3 Es tablish an Org anizational Training Tactical Plan
SP 1.4 Establish Training Capability
SG 2 Provide Necessary Training
SP 2.1 Deliver Training
SP 2.2 Es tablish Training Records
SP 2.3 Asses s T raining Effectiveness
11. Product Integ ration (PI) An Engineering process are a at Maturity Level 3
Purpose
The purpose of Product Integ ration (PI) is to assemble the product from the product components, ensurethat the product, as integ rated, functions properly, and deliver the product.
Specific Practices by Goal
SG 1 Prepare for Product Integ ration
SP 1.1 Determine Integ ration SequenceSP 1.2 Es tablish the Product Integ ration Environment
SP 1.3 Establish Product Integ ration Proce dures and Criteria
SG 2 Ensure Interface Compatibility
SP 2.1 Review Interface Descriptions for Completeness
SP 2.2 Manage Interfaces
SG 3 Assemble Product Components and De liver the Product
SP 3.1 C onfirm Readiness of Product Components for Integ ration
SP 3.2 Assemble Product Components
SP 3.3 Evaluate Assembled Product Components
SP 3.4 Package and Deliver the Product or Product Component
A Proje ct Manag ement process are a at Maturity Level 2
Purpose
The purpose of Project Monitoring and Control (PMC) is to provide an understanding of the project'sprogress so that appropriate corrective actions can be taken when the project's performance deviatessignificantly from the plan.
Specific Practices by Goal
SG 1 Monitor Proje ct Ag ainst Plan
SP 1.1 Monitor Proje ct Planning Parameters
SP 1.2 Monitor Commitments
SP 1.3 Monitor Project Risks
SP 1.4 Monitor Data Manag ement
SP 1.5 Monitor Stakeholder Involvement
SP 1.6 Conduct Progress Reviews
SP 1.7 Conduct Milestone Reviews
SG 2 Manag e Corrective Action to Closure
SP 2.1 Analyze Issues
SP 2.2 Take Corrective Action
SP 2.3 Manage Corrective Action
13. Project Planning (PP)
A Proje ct Manag ement process are a at Maturity Level 2
Purpose
The purpose of Proje ct Planning (PP) is to establish and maintain plans that define project activities.
Specific Practices by Goal
SG 1 Establish Estimates
SP 1.1 Estimate the Scope of the Project
SP 1.2 Establish Estimates of Work Product and Task Attributes
The purpose of Proc ess and Pro duct Quality Assurance (PPQA) is to provide staff and manag ement with objective insig ht into processes and associated work products.
Specific Practices by Goal
SG 1 Objectively Evaluate Proces se s and Work Products
SP 1.1 Objectively Evaluate Processes
SP 1.2 Objectively Evaluate Work Products and Services
SG 2 Provide Objective Insig ht
SP 2.1 Communicate and Ensure Resolution of Noncompliance Issues
SP 2.2 Establish Records
15. Quantitative Project Manag ement (QPM)
A Proje ct Manag ement process are a at Maturity Level 4
Purpose
The purpose of the Quantitative Projec t Management (QPM) proce ss area is to quantitatively manag e theproje ct's defined proce ss to achieve the proje ct's established quality and proce ss -performance obje ctives .
Specific Practices by Goal
SG 1 Quantitatively Manag e the Proje ct
SP 1.1 Establish the Project's Objectives
SP 1.2 Compose the Defined Processes
SP 1.3 Se lect the Subprocesses that Will Be Statistically Manag ed
SP 1.4 Manage Project Performance
SG 2 Statistically Manag e Subprocess Performance
SP 2.1 Select Measures and Analytic Techniques
SP 2.2 Apply Statistical Methods to Understand Variation
SP 2.3 Monitor Performance of the Selected Subprocesses
SP 2.4 Re cord Statistical Manag ement Data
16. Requirements Development (RD)
An Engineering process are a at Maturity Level 3
Purpose
The purpose of Requirements Development (RD) is to produce and analyze customer, product, andproduct-component requirements.
SP 2.1 Establish Product and Product-Component Requirements
SP 2.2 Allocate Product-Component Requirements
SP 2.3 Identify Interface Requirements
SG 3 Analyze and Validate Requirements
SP 3.1 Establish Ope rational Concepts and Scenarios
SP 3.2 Establish a Definition of Required Functionality
SP 3.3 Analyze Requirements
SP 3.4 Analyze Requirements to Achieve Balance
SP 3.5 Validate Requirements
17. Requirements Management (REQM)
An Engineering process are a at Maturity Level 2
Purpose
The purpose of Requirements Management (REQM) is to manag e the requirements of the project'sproducts and product components and to identify inconsistencies between those requirements and the project'splans and work products.
Specific Practices by Goal
SG 1 Manag e Requirements
SP 1.1 Obtain an Understanding of Re quirements
SP 1.2 Obtain Commitment to Requirements
SP 1.3 Manage Requirements Chang es
SP 1.4 Maintain Bidirectional Traceability of Re quirements
SP 1.5 Identify Inconsistencies between Proje ct Work and Requirements
18. Risk Management (RSKM)
A Proje ct Manag ement process are a at Maturity Level 3
Purpose
The purpose of Risk Management (RSKM) is to identify potential problems before they occur so that risk-handling activities can be planned and invoked as needed across the life of the product or project to mitig ateadverse impacts on achieving objectives.
SP 2.2 Evaluate, Categ orize , and Prioritize Risks
SG 3 Mitigate Risks
SP 3.1 Develop Risk Mitig ation Plans
SP 3.2 Implement Risk Mitig ation Plans
19. Supplier Agreement Manag ement (SAM)
A Proje ct Manag ement process are a at Maturity Level 2
Purpose
The purpose of Supplier Agreement Management (SAM) is to manag e the acquisition of products fromsuppliers for which there exists a formal ag reement.
Specific Practices by Goal
SG 1 Establish Supplier Ag reements
SP 1.1 Determine Acquisition Type
SP 1.2 Se lect SuppliersSP 1.3 Establish Supplier Ag reements
SG 2 Satisfy Supplier Agreements
SP 2.1 Execute the Supplier Agreement
SP 2.2 Monitor Se lected Supplier Proce sses
SP 2.3 Evaluate Se lected Supplier Work Products
SP 2.4 Acce pt the Acquired Product
SP 2.5 Transition Products
20. Technical Solution (TS)
An Engineering process are a at Maturity Level 3
Purpose
The purpose of Technical Solution (TS) is to de sign, develop, and implement solutions to requirements.Solutions, desig ns, and implementations encompass products, product components, and product-related life-cycle processe s either sing ly or in combination as appropriate.
Specific Practices by Goal
SG 1 Select Product-Component Solutions
SP 1.1 Develop Alternative Solutions and Selection Criteria
The purpose of Validation (VAL) is to demonstrate that a product or product component fulfills its intended use when place d in its intended environment.
Specific Practices by Goal
SG 1 Prepare for Validation
SP 1.1 Se lect Products for Validation
SP 1.2 Establish the Validation Environment
SP 1.3 Establish Validation Procedures and Criteria
SG 2 Validate Product or Product Components
SP 2.1 Perform Validation
SP 2.2 Analyze Validation Results.
22. Verification (VER)
An Engineering process are a at Maturity Level 3
Purpose
The purpose of Verification (VER) is to ensure that selected work products mee t their specifiedrequirements.
Specific Practices by Goal
SG 1 Prepare for Verification
SP 1.1 Select Work Products for Verification
SP 1.2 Establish the Verification Environment
SP 1.3 Establish Verification Procedures and Criteria
SG 2 Perform Peer Reviews
SP 2.1 Prepare for Peer Reviews
SP 2.2 Conduct Pee r Reviews
SP 2.3 Analyze Peer Review Data
SG 3 Verify Selected Work Products
SP 3.1 Perform Verification
SP 3.2 Analyze Verification Results
Chang es made in Version 1.2
Only chang es made to the se t of Process Areas are considere d here. For a more detail visit the SEI homepage.
The following Proce ss Are as have be en removed (all on Maturity Level 3):
Org anisational Environment for Integ ration (OEI)
Integ rated Te aming (IT)
Integ rated Supplier Manag ement (ISM)
The following additions have been made within existing Proce ss Are as:
IPM . SG3 and SG4 were eliminated, new SG3 was adde d (all IPPD PAs)
OPF . two SPs were extracted from SG and cre ated SG3 together with two new SPs
REQD . SP3.5 was renamed Validate Requirements
SAM . SP2.1 was eliminated, two new SPs added in SG2
TS . SP1.2 was eliminated
VER . SP3.2 was re named Analyze Verification Results
What is Next:
Now you have completed all the major sessions related to C MMI. In the next chapter we will discuss CMMI Appraisals.
CMMI Appraisal is an examination of one or more processe s by a trained team of profes sionals using anappraisal refere nce model as the basis for de termining streng ths and weakness es.