SE423:Software Process Improvement (SPI)SCAMPI

Kittitouch Suteeca

Ref. Panit Watcharawitch, PhD (cantab)

2

Standard CMMI Appraisal Method for Process Improvement (SCAMPI)SCAMPI is designed to provide benchmark quality ratings

relative to Capability Maturity Model® Integration (CMMISM) models. It is applicable to a wide range of appraisal usage modes, including both internal process improvement and external capability determinations. SCAMPI satisfies all of the Appraisal Requirements for CMMI (ARC) requirements for a Class A appraisal method and supports the conduct of ISO/IEC 15504 assessments.

SCAMPI Appraisal System (SAS) Method Definition Document (MDD) Appraisal Requirements for CMMI (ARC) Appraisal Team Member (ATM) Appraisal Disclosure Statement (ADS)

3

SCAMPI class A, B, C

4

Objective SCAMPI class A Understand the current implemented process.Identify process weakness (and strengths) in the

organization unit.Determine degree of satisfaction of CMMI process area

goal investigated.Assign rating ,if request by appraisal sponsor.

5

Rating process attributes Process attribute rating values: The ordinal rating scale

defined below shall be used to express the levels of achievement of the process attributes. N Not achieved: There is little or no evidence of

achievement of the defined attribute in the assessed process.

P Partially achieved: There is some evidence of an approach to, and some achievement of, the defined attribute in the assessed process. Some aspects of achievement of the attribute may be unpredictable.

6

Rating process attributes L Largely achieved: There is evidence of a systematic

approach to, and significant achievement of, the defined attribute in the assessed process. Some weakness related to this attribute may exist in the assessed process.

F Fully achieved: There is evidence of a complete and systematic approach to, and full achievement of, the defined attribute in the assessed process. No significant weaknesses related to this attribute exist in the assessed process.

7

Rating process attributes The corresponding values shall be:

N Not achieved 0 to 15% achievement P Partially achieved >15% to 50% achievementL Largely achieved >50% to 85% achievement F Fully achieved >85% to 100% achievement.

8

Example: CMMI ML2 Appraisal of RUP

Reference: http://www.ibm.com/developerworks/rational/library/dec05/grundmann/

Requirement management (REQM)

9

Example: CMMI ML2 Appraisal of RUP #2Project planning(PP)

10

Example: CMMI ML2 Appraisal of RUP #3

Supplier Agreement Management (SAM)

11

Example: CMMI ML2 Appraisal of RUP #4

Generic goal and Generic Practice

12

Example: CMMI ML2 AppraisalR

EQ

M PP

PM

C

SA

M

MA

PPQ

A

CM

0.00%

20.00%

40.00%

60.00%

80.00%

100.00%

120.00%

SPI with CMMI Project Summary Chart Maturity Level 2

% Complete of each PAs

% Actual Complete of PAs

PAs

13

Example: CMMI ML2 AppraisalR

EQ

M PP

PM

C

SA

M

MA

PPQ

A

CM

0.00%

5.00%

10.00%

15.00%

20.00%

25.00%

SPI with CMMI Project Summary Chart Maturity Level 2

% PAs in Project (Es-timation)

% Complete of PAs in Project

PAs

14

Example: CMMI ML2 Appraisal

15

Scoring

16

Generic Goals & Generic PracticesGG 1 Achieve Specific Goals

GP 1.1 Perform Specific PracticesGG 2 Institutionalize a Managed Process

GP 2.1 Establish an Organizational PolicyGP 2.2 Plan and ProcessGP 2.3 Provide ResourcesGP 2.4 Assign ResponsibilityGP 2.4 Train PeopleGP 2.6 Manage ConfigurationGP 2.7 Identify and Involve Relevant StakeholdersGP 2.8 Monitor and Control the processGP 2.9 Objectively Evaluate Adherence

GP 2.10 Review Status with Higher Level ManagementGG 3 Institutionalize a Defined Process

GP 3.1 Establish a Defined ProcessGP 3.2 Collect Improvement Information

GG 4 Institutionalize a Quantitatively Managed ProcessGP 4.1 Establish Quality Objective for the ProcessGP 4.2 Stabilize Subprocess Performance

GG 5 Institutionalize an Optimizing ProcessGP 5.1 Ensure Continuous Process ImprovementGP 5.2 Correct Root Causes of Problem

Staged Representation

17

Appraisal keysAppraisal ConsiderationsDirect Artifact Indirect Artifact

18

Example:REQM ML215 Key practices

5 Specific Practices10 Generic Practices

SP 1.1-1 Obtain an Understanding of RequirementsDevelop an understanding with the requirements providers

on the meaning of the requirementsAppraisal Considerations

Consider existence of requirements at multiple levels (e.g., product and product component requirements.).

19

Example:REQM ML2Direct Artifact

Allocated Requirements DocumentAllocated Requirements DatabaseReview Report of RequirementsCommitments from affected groups on allocated

requirementsDefined criteria for evaluation and acceptance of

requirements

20

Example:REQM ML2Indirect Artifact

Evidence of early (before committing to develop the corresponding software) system requirement allocated to software review (e.g. meeting minutes, reports…)

A list or characterization of requirements providers authorized to provide direction

21

Example of ML2 and ML3Available in SPI. site.