level - 2 process areas (cmmi-dev)apps.ocac.in/uploaddocuments/news/newsddfcvbn.pdf · verification...

®Capability Maturity Model, Capability Maturity Modeling, CMM, and CMMI are registered in the U.S. Patent and Trademark Office by Carnegie

Mellon University. SMCMM Integration, IDEAL, and SCAMPI are service marks of Carnegie Mellon University.

Level - 2 Process Areas (CMMI-DEV)

Defined

Quantitatively

Managed

Managed

Initial

© Software Engineering Institute

Optimizing



Organizational Training

Organizational Process Definition

Organizational Process Focus

Organizational Process Performance

Project Monitoring and Control

Project Planning

Supplier Agreement Management

Requirements Management

Integrated Project Management

Risk Management

Quantitative Project Management

Requirements Development

Technical Solution

Product Integration

Verification

Validation

Organizational Performance Management

Configuration Management

Process & Product QA

Measurement & Analysis

Decision Analysis & Resolution

Causal Analysis & Resolution

Engineering Project Management Process Management Support

2

3

4

5

2

3

4

5

Staged View of Process Areas : CMMI-DEV


Mellon University. SMCMM Integration, IDEAL, and SCAMPI are service marks of Carnegie Mellon University. 3

• At this level, Projects establish the foundation for the organization to

become effective service providers

– Create project strategy and set realistic commitments

– Plan achievements within the project, evaluate actual progress and ensure

the service is delivered as planned

Level 2 - Managed

Source of drawings: CMU/SEI-93-TR-024

–Service provider establishes agreements with customers as well as develops

and manages customer and contractual requirements




Requirements




The purpose of Requirements Management (REQM) is to

manage requirements of the project’s products and product

components and to ensure alignment between those

requirements and the project’s plans and work products.




• Manage Requirements (SG1)

There are 1 specific goal in the process area -




SG1: Manage Requirements

Obtain Commitment To Requirements SP

1.2

Manage Requirements Changes SP

1.3

Maintain Bidirectional Traceability

of Requirements

SP

1.4

Understand Requirements SP

1.1

Planning

Data

Requirements

Ensure Alignment Between Project Work

And Requirements

SP

1.5



Project Planning



Project Planning

• Establish Estimates (SG1)

• Develop a Project Plan (SG2)

• Obtain Commitment to the Plan (SG3)

M05-CMMIL2 Jan 2011

CMMISM Development v1.3

There are 3 specific goals in the process area -



Project Planning

• The purpose of Project Planning is to establish and maintain

plans that define project activities.

M05-CMMIL2 Jan 2011


One of the keys to effectively managing a project is project

planning. The process area involves the following activities:

•Developing the project plan

•Interacting with relevant stakeholders appropriately

•Getting commitment to the plan

•Maintaining the plan



Project Planning

• Establish Estimates (SG1)

• Develop a Project Plan (SG2)

• Obtain Commitment to the Plan (SG3)

M05-CMMIL2 Jan 2011





Project Planning

SG1: Establish Estimates

Establish Estimates of Work products

and Task attributes

SP

1.2

Define Project Life Cycle Phases SP

1.3

Estimate Effort and Cost SP

1.4

Estimate the Scope of the Project SP

1.1

Planning

Data

Requirements



Project Planning

Establish the Project Plan SP

2.7

Pro

ject

Pla

n

SG2: Develop a Project Plan

Planning

Data

Identify Project Risks SP

2.2

Establish the Budget & Schedule SP

2.1

7:00

7:30

8:00

8:30

9:00

930

10:00

10:30

11:00

1130

12:00

12:30

1:00

1:30

2:00

2:30

3:00

3:30

4:00

4:30

5:00

Plan Data Management SP

2.3

Plan for Needed Knowledge & Skills SP

2.5

Plan Stakeholder Involvement SP

2.6

Plan the Project’s Resources SP

2.4



Project Planning

SG3: Obtain Commitment to the Plan

Pro

ject

Pla

n

Review Plans that Affect the Project SP

3.1

Su

b

Pro

ject

Pla

n

Su

b

Pro

ject

Pla

n

Su

b

Pro

ject

Pla

n

Reconcile Work and Resource Levels SP

3.2

Obtain Plan Commitment SP

3.3




M05-CMMIL2 Jan 2011





The purpose of Project Monitoring and Control

(PMC) is to provide an understanding of the

project’s progress so that appropriate corrective

actions can be taken when the project’s

performance deviates significantly from the plan.

M05-CMMIL2 Jan 2011





• Monitor Project Against Plan(SG1)

• Manage Corrective Action to Closure (SG2)

M05-CMMIL2 Jan 2011






SG1: Monitor Project Against Plan

Pro

ject

Pla

n

Monitor Project Risks SP

1.3

Monitor Commitments SP

1.2

7:00

7:30

8:00

8:30

9:00

930

10:00

10:30

11:00

1130

12:00

12:30

1:00

1:30

2:00

2:30

3:00

3:30

4:00

4:30

5:00

Monitor Data

Management

SP

1.4

Monitor Project

Planning Parameters SP

1.1

Monitor Stakeholder

Involvement

SP

1.5

Conduct Progress Reviews

SP

1.6

Conduct Milestone Reviews

SP

1.7

Project

Progress

Report

Milestone

Review

Report

M05-CMMIL2 Jan 2011





SG2: Manage Corrective Action to Closure

Project

Progress

Report

Milestone

Review

Report

Analyze Issues SP

2.1

WHY

Manage Corrective Action SP

2.3

Take Correction Action SP

2.2

Actions




• The purpose of Supplier Agreement Management (SAM) is

to manage the acquisition of products and services from

suppliers.

The Supplier Agreement Management process area involves the following

activities:

• Determining the type of acquisition

• Selecting suppliers

• Establishing and maintaining agreements with suppliers

• Executing supplier agreements

• Accepting delivery of acquired products

• Ensuring successful transition of acquired products

M05-CMMIL2 Jan 2011





• Establish Supplier Agreements(SG1)

• Satisfy Supplier Agreements(SG2)

M05-CMMIL2 Jan 2011






SG1: Establish Supplier Agreements

Establish Supplier Agreements SP

1.3

Requirements

Select Suppliers SP

1.2 Determine Acquisition type SP

1.1

Supplier

Requirements

M05-CMMIL2 Jan 2011





SG2: Satisfy Supplier Agreements

Execute the Supplier Agreement SP

2.1

Accept the Acquired Product SP

2.2

Ensure Transition Products SP

2.3

M05-CMMIL2 Jan 2011




Measurement and Analysis

M05-CMMIL2 Jan 2011





• The purpose of Measurement and Analysis (MA) is to

develop and sustain a measurement capability used to

support management information needs.

M05-CMMIL2 Jan 2011





• Align Measurement and Analysis Activities(SG1)

• Provide Measurement Results (SG2)

M05-CMMIL2 Jan 2011






SG1: Align Measurement and Analysis Activities

Specify Data Collection

and Storage Procedures

SP

1.3 DP

Specify Analysis

Procedures

SP

1.4 DP

Specify Measures SP

1.2

Establish Measurement

Objectives

SP

1.1

M05-CMMIL2 Jan 2011





SG2: Provide Measurement Results

Store Data and Results SP

2.3

Analyze Measurement Data SP

2.2

Analysis 34

Design 45

Coding 125

Testing 67

Communicate Results SP

2.4

Obtain Measurement Data SP

2.1

M05-CMMIL2 Jan 2011




Process and Product Quality Assurance




The purpose of Process and Product Quality Assurance

(PPQA) is to provide staff and management with objective

insight into processes and associated work products.

• Objectively evaluating performed processes and work products against

applicable process descriptions, standards, and procedures

• Identifying and documenting noncompliance issues

• Providing feedback to project staff and managers on the results of quality

assurance activities

• Ensuring that noncompliance issues are addressed

M05-CMMIL2 Jan 2011





• Objectively Evaluate Processes and Work

Products(SG1)

• Provide Objective Insight (SG2)

M05-CMMIL2 Jan 2011






SG1: Objectively Evaluate Processes and Work Products

Objectively Evaluate

Work Products

SP

1.2

Project

Plan

Requirements

Design

Test Plans

Objectively Evaluate Processes SP

1.1

M05-CMMIL2 Jan 2011





SG2: Provide Objective Insight

Communicate and Resolve

Noncompliance Issues

SP

2.1 Establish Records

SP

2.2 VWX

YZ

STUPQR

MNOJKL

GHI




M05-CMMIL2 Jan 2011





• The purpose of Configuration Management (CM) is to

establish and maintain the integrity of work products using

configuration identification, configuration control,

configuration status accounting, and configuration audits.

• Identifying the configuration of selected work products that compose

baselines at given points in time

• Controlling changes to configuration items

• Building or providing specifications to build work products from the

configuration management system

• Maintaining the integrity of baselines

• Providing accurate status and current configuration data to developers,

end users, and customers

M05-CMMIL2 Jan 2011





• Establish Baselines(SG1)

• Track and Control Changes (SG2)

• Establish Integrity (SG3)

M05-CMMIL2 Jan 2011






SG1: Establish Baselines

Identify Configuration Items SP

1.1

Project

Plan

Requirements

Design

Test Plans Create or Release Baselines SP

1.3

Establish a Configuration

Management System

SP

1.2

M05-CMMIL2 Jan 2011





SG2: Track and Control Changes

Track Change Requests SP

2.1

Change

Request

Control Configuration

Items

SP

2.2

M05-CMMIL2 Jan 2011





SG3: Establish Integrity

Establish Configuration

Management Records

SP

3.1 VWX

YZ

STUPQR

MNOJKL

GHI

Perform Configuration Audits SP

3.2

M05-CMMIL2 Jan 2011




Generic Goal (GG2)

GG2: Institutionalize a Managed Process

Plan the Process GP2.2

Provide Resources GP 2.3

Assign

Responsibility GP2.4

Train People GP 2.5

Establish an

Organizational

Policy

GP2.1 Control Work

Products GP2.6

Identify and Involve

Relevant Stakeholders GP 2.7

Monitor and Control

the Process GP2.8

Objectively Evaluate

Adherence GP2.9

Review Status with

Higher-Level

Management

GP 2.10

Plan

i

level - 2 process areas (cmmi-dev)apps.ocac.in/uploaddocuments/news/newsddfcvbn.pdf · verification...

Documents