CMMI_Appraisal_Results - An Example

7/25/2019 CMMI_Appraisal_Results - An Example

1/30

CMMI Appraisal Rating Guidance

Rating Specific Practices

Code Name

FI Practice Fully Implemeted

LI Practice Largely Implemented

PI Practice Partially Implemented

NI Practice Not Implemented

Rating Specific Goals

Code Name

S Goal Satisfied

NS Goal Not Satisfied


2/30

Guidance

Guidance

A CMMI specific practice should be rated as Fully Implemented if in the opinion of the appraisal team:! "he #P$%# contains acti&ities that' if performed' (ould meet all re)uirements of the specific practice' and*! "he #P$%# identifies output artifacts that' if produced' (ould pro&ide e&idence of the specific practice being underta+e,! No ma-or or minor (ea+nesses can be identified in the #P$%# (ith respect to the specific practice

A CMMI specific practice should be rated as Largely Implemented if in the opinion of the appraisal team:! "he #P$%# contains acti&ities that' if performed' (ould meet most of re)uirements of the specific practice' and*! "he #P$%# identifies output artifacts that' if produced' (ould pro&ide e&idence of the specific practice being underta+e,! At least one minor (ea+ness can be identified in the #P$%# (ith respect to the specific practice' and.! No ma-or (ea+nesses can be identified in the #P$%# (ith respect to the specific practice

A CMMI specific practice should be rated as Partially Implemented if in the opinion of the appraisal team:! "he #P$%# contains acti&ities that' if performed' (ould meet only some of re)uirements of the specific practice' and*! "he #P$%# identifies output artifacts that' if produced' (ould pro&ide limited e&idence of the specific practice being un,! At least one ma-or (ea+ness can be identified in the #P$%# (ith respect to the specific practice

A CMMI specific practice should be rated as Not Implemented if in the opinion of the appraisal team:! "he #P$%# does not contain any acti&ities relating to the specific practice' and*! "he #P$%# does not identify any output artifacts that' if produced' (ould pro&ide e&idence of the specific practice bein,! At least one ma-or (ea+ness can be identified in the #P$%# (ith respect to the specific practice

A CMMI specific goal should be rated as satisfied if and only if:! All specific practices associated (ith that goal ha&e been characterised as either Fully Implemented and Largely Imple*! "he aggregation of (ea+nesses associated (ith the goal does not ha&e a significant negati&e impact on goal achie&em

A CMMI specific goal should be rated as not satisfied if:! Any specific practices associated (ith that goal ha&e been characterised as either Partially Implemented or Not Implem*! "he aggregation of (ea+nesses associated (ith the goal has a significant negati&e impact on goal achie&ement


3/30

Process Area: Configuration ManagementGoals and Practices Implementation Description Direct and Indirect Artifacts Prod

SG 1 sta!lis" #aselines

SP ! Identify Configuration Items

SP !*

SP !, Create or /elease 0aselines

SG $ %rac& and Control C"anges

SP *! "rac+ Change /e)uests

SP *!* Control Configuration Items

SG ' sta!lis" Integrit(

SP ,!

SP ,!* Perform Configuration Audits

"he #P$%# contains a (or+flo( (ithin the Configuration and ChangeManagement %iscipline called Plan Pro-ect Configuration! 1ithin this(orflo(' a person (ith the role of Configuration Manager is re)uired to

(rite a Configuration Management Plan' (hich (ill specifically identify theconfiguration items to be produced throughout the pro-ect! "his plan (ill bere&ie(ed by rele&ant sta+eholders and appro&ed by the Pro-ect Manager!

Configuration Management Plan

/ecords from CM Plan re&ie(CM Plan appro&al documentation

$stablish a ConfigurationManagement System

"he #P$%# re)uires that a CM Plan be (ritten and that it contains adescription of the configuration management en&ironment! "he acti&ityCreate 1or+spaces (ithin the Change and %eli&er Configuration Items(or+flo( specifically relates to the creation of (or+spaces (ithin the CMsystem!

Configuration Management PlanPro-ect repository populated (ithconfiguration items

"he #P$%# re)uires that the pro-ect CM Plan contain a list of thebaselines to be created for the pro-ect! "hese baselines are applied toconfiguration items in the pro-ect as part of the 2Create 0aselines2 acti&ity(ithin the 2Change and %eli&er Configuration Items2 (or+flo(!

Configuration Management Plan0aselines identified (ithin the CM s

"he #P$%# 2Manage Change /e)uests2 (orflo( defines acti&ities forensuring that changes to configuration items are made in a consistenmanner! "his (or+flo( re)uires that proposed changes to baselinedconfiguration items are submitted' re&ie(ed and appro&ed by theConfiguration Manager and a Configuration Control 0oard before thechange is allo(ed to proceed!

Change /e)uestsMinutes from CC0 meeting

"he acti&ity 2Ma+e Changes2 (ithin the 2Change and %eli&er ConfigurationItems2 (or+flo( describes the control of configuration items! Multiple&ersion of configuration items are maintained using chec+out and chec+infacilities pro&ided by the configuration management system!

Configuration items in the pro-ect re3ersion history of configuration item

$stablish ConfigurationManagement /ecords

"he storage of appropriate configuration management records is facilitatedby the CM system!

Pro-ect repository

3ersion history for configuration item0aselines established in pro-ect repConfiguration Status Accounting /e

"he pro-ect CM Plan identifies the configuration status accountingacti&ities to be conducted! "he 2/eport on Configuration Status2 acti&ity inthe 2Monitor and /eport on Configuration Status2 (or+flo( re)uires that theConfiguration Manager performs periodic chec+s on the integrity of theconfiguration management system and established baselines!

Configuration Status Accounting /eFunctional Configuration Audit /epoPhysical Configuration Audit /eport


4/30

Process Area: Pro)ect MonitoGoals and Practices

SG 1 Monitor Pro)ect Against Plan

SP !

SP !* Monitor Commitments

SP !, Monitor Pro-ect /is+s

SP !. Monitor %ata Management

SP !4 Monitor Sta+eholder In&ol&ement

SP !5 Conduct Progress /e&ie(s

SP !6 Conduct Milestone /e&ie(s

SG $

Monitor Pro-ect PlanningParameters

Manage Corrective Action toClosure


5/30

SP *! Analy7e Issues

SP *!* "a+e Correcti&e Action

SP *!, Manage Correcti&e Action


6/30

ring and ControlImplementation Description

"he #P$%# 2Monitor 8 Control Pro-ect2 (orflo( in 2Pro-ect Management2discipline defines an acti&ity called 2Monitor Pro-ect Status2 that aimed tocapture current status of the pro-ect and e&aluate status against plans9Soft(are %e&elopment Plan' Iteration Plan' Measurement Plan!;n this acti&ity' the Pro-ect Manager must collect )uality and progressinformation on the pro-ect for assessing current status' deri&es progress 8)uality indicators' and then compares these indicators against thee


7/30

"he #P$%# 2%e&elop Soft(are %e&elopment Plan2 (orflo( in 2Pro-ectManagement2 discipline defines 2/e&ie( Pro-ect Planning2 acti&ity thatre)uires the /e&ie(ers to conduct re&ie( meetings during the pro-ect! ;nthese meetings' the /e&ie(ers must re&ie( some artifacts 93ision'0usiness Case' /is+ List' Soft(are %e&elopment Plan and its enclosedplans to analy7e issues and propose strategy ho( to ta+e correcti&e

action 9(hen it be needed !

"he #P$%# 2Monitor 8 Control pro-ect2 (orflo( in 2Pro-ect Management2discipline defines an acti&ity called 2Schedule and Assign (or+2 that mustbe performed by the pro-ect manager to accommodate appro&ed changes9defects' enhancements' to product and process' (hich arise during aniteration! "he correcti&e actions must be ta+en based on the result of there&ie( meeting conducted before!

"he #P$%# 2Monitor 8 Control pro-ect2 (orflo( in 2Pro-ect Management2discipline also defines an acti&ity called 2Ma+e Changes2 to accommodatethe team members2 need for access to the set of artifacts to be changed9change set in order to ta+e correcti&e action based on the 2Schedule andAssign 1or+2 and to fulfill 9through performing &arious acti&ities there)uirements of their (or+ order!


8/30

Direct and Indirect Artifacts Produced Opportunities for Improvement Rating

NS

None FI

Pro-ect Measurements None FI

None FI

Pro-ect Measurements None FI

= NI

PI

PI

S

Pro-ect Measurements/is+ List

Soft(are %e&elopment PlanMeasurement PlanPro-ect Measurements/is+ List

"he #P$%# currently doesn2t pro&ide anyguidance on ho( to monitor thesta+eholder in&ol&ement during thepro-ect! "he a&ailability of guidelines andtemplates in this area must be of benefit!

/e&ie( /ecordMinutes from re&ie( meetings

"he sta+eholders must be participate onthe re&ie( meetings!


"he sta+eholders must be participate onthe re&ie( meetings!


9/30

None FI

None FI

None FI


1or+ ;rderSoft(are %e&elopment PlanIteration Plan

Pro-ect /epository1or+ ;rder


10/30

Process Area: Pro)ect Planni

Goals and Practices

SG 1 sta!lis" stimates

SP !

SP !*

SP !, %efine Pro-ect Lifecycle

SP !.

SG $ Develop a Pro)ect Plan

SP *!

SP *!* Identify Pro-ect /is+s

SP *!, Plan for %ata Management

SP *!. Plan for Pro-ect /esources

SP *!4

SP *!5 Plan Sta+eholder In&ol&ement

SP *!6 $stablish the Pro-ect Plan

SG ' O!tain Commitment to Plan

SP ,!

SP ,!*

SP ,!, ;btain Plan Commitment

$stimate the Scope of the

Pro-ect$stablish $stimates of 1or+Product and "as+ Attributes

%etermine $stimates of $ffortand Cost

$stablish the 0udget andSchedule

Plan for Needed >no(ledge andS+ills

/e&ie( Plans "hat Affect thePro-ect

/econcile 1or+ and /esourceLe&els


11/30

ng

Implementation Description


12/30



13/30

Process Area: Re*uirementGoals and Practices

SG 1 Manage Re*uirements

SP !

SP !*

SP !,

SP !.

SP !4

;btain an #nderstanding of/e)uirements

;btain Commitment to/e)uirements

Manage /e)uirementsChanges

Maintain 0idirectional"raceability of /e)uirements

Identify Inconsistencies0et(een Pro-ect 1or+ and/e)uirements


14/30

ManagementImplementation Description

"he #P$%# 2#nderstand "he Problem2 (orflo( in 2/e)uirements2

discipline defines t(o acti&ities 92$licit Sta+eholder /e)uests2 and 2FindActors and #se cases2 that system analyst must perform for collectingand eliciting information from the sta+eholders of the pro-ect in order tounderstand (hat re)uirements they need to be pro&ided in the intendedsystem!

"he #P$%# 2Plan for Ne


15/30


S

None FI

Iteration Plan None FI

None FI

None FI

None FI

Actor#se Case

#se=Case ModelSupplementary SpecificationsGlossarySoft(are /e)uirements Specifications9S/S


Soft(are /e)uirements Specifications9S/S



16/30

Process Area: %ec"nical SolGoals and Practices

SG 1

SP !

SP !*

SG $ Develop t"e Design

SP *!

SP *!*

SP *!, %efine Interfaces #sing Criteria

SP *!.

SG '

SP ,! Implement the %esign

SP ,!*

Select Product ComponentSolutions

%e&elop Alternati&e Solutions

and Selection CriteriaSelect Product ComponentSolutions

%esign the Product or ProductComponent

$stablish a "echnical %ataPac+age

Perform Ma+e' 0uy' or /euse

Analysis

Implement t"e ProductDesign

%e&elop Product Support%ocumentation


17/30

utionImplementation Description


18/30



19/30

Process Area: +erificationGoals and Practices

SG 1 Prepare for +erification

SP !

SP !*

SP !,

SG $ Perform Peer Revie,s

SP *! Prepare for Peer /e&ie(s

SP *!* Conduct Peer /e&ie(s

SP *!, Analy7e Peer /e&ie( %ata

SG '

SP ,! Perform 3erification

SP ,!* Analy7e 3erification /esults

Select 1or+ Products for3erification

$stablish the 3erification$n&ironment

$stablish 3erificationProcedures and Criteria

+erif( Selected -or&Products


20/30



21/30



22/30

Process Area: Product IntegratGoals and Practices

SG 1 Prepare for Product Integration

SP ! %etermine Integration Se)uence

SP !*

SP !,

SG $ nsure Interface Compati!ilit(

SP *!

SP *!* Manage Interfaces

SG '

SP ,!

SP ,!* Assemble Product Components

SP ,!,

SP ,!.

$stablish the Product Integration

$n&ironment$stablish Product IntegrationProcedures and Criteria

/e&ie( Interface %escriptions forCompleteness

Assem!le Product Componentsand Deliver t"e Product

Confirm /eadiness of Product

Components for Integration

$&aluate Assembled ProductComponents

Pac+age and %eli&er the Product orProduct Component


23/30

ionImplementation Description


24/30



25/30

Process Area: Re*uirements DeGoals and Practices

SG 1 Develop Customer Re*uirements

SP ! $licit Needs

SP !* %e&elop the Customer /e)uirements

SG $ Develop Product Re*uirements

SP *!

SP *!*

SP *!, Identify Interface /e)uirements

SG ' Anal(se and +alidate Re*uirements

SP ,!

SP ,!*

SP ,!, Analy7e /e)uirements

SP ,!.

SP ,!4 3alidate /e)uirements

$stablish Product and ProductComponent /e)uirements

Allocate Product Component/e)uirements

$stablish ;perational Concepts and

Scenarios

$stablish a %efinition of /e)uiredFunctionality

Analy7e /e)uirements to Achie&e0alance


26/30

elopmentImplementation Description


27/30



28/30

Process Area: +alidationGoals and Practices

SG 1 Prepare for +alidation

SP ! Select Products for 3alidation

SP !*

SP !,

SG '

SP ,! Perform 3alidation

SP ,!* Analy7e 3alidation /esults

$stablish the 3alidation$n&ironment

$stablish 3alidationProcedures and Criteria

+erif( Product or ProductComponents


29/30


"he #P$%# contains a (or+flo( (ithin the 2"est2 discipline called 2Plan and%esign "est2! 1ithin this (orflo(' persons (ith the role of "esters are

re)uired to (rite a "est Plan! "he "est Plan must specifically define theproducts?items for the &alidation 9i!e! testing process! List of products that(ill be &alidated are listed on 2/e)uirement for "est2 section of the "est Plandocument! "his list is represents (hat (ill be &alidated!

"he #P$%# re)uires that a "est Plan be (ritten and that it contains adescription of the &alidation en&ironment that (ill be used during the&alidation 9i!e! testing process! "he &alidation en&ironment is described onthe 2/esources2 section of the "est Plan document!

"est Plan contains a section named 2"est Strategy2 (hich contains a sub=section named 2"est "ype2! "he 2"est "ype2 sub=section describes theprocedure and the criteria for the &alidation process for each functionality onthe product?product component!

1ithin the 2$


30/30


S

"est Plan None FI

"est Plan None FI

None FI

S

None FI

"est $&aluation /eport None FI

"est Plan"est Cases

"est /esults%efect

Documents

CMMI_Appraisal_Results - An Example