CHANGE MANAGEMENT PLAN变更管理计划 英文版.docx

CHANGE MANAGEMENT PLAN变更管理计划 英文版.docx

《CHANGE MANAGEMENT PLAN变更管理计划 英文版.docx》由会员分享，可在线阅读，更多相关《CHANGE MANAGEMENT PLAN变更管理计划 英文版.docx（9页珍藏版）》请在冰豆网上搜索。

CHANGEMANAGEMENTPLAN变更管理计划英文版

ChangeManagementPLAN

Version<1.0>

VERSIONHISTORY

[ProvideinformationonhowthedevelopmentanddistributionoftheChangeManagementPlan,uptothefinalpointofapproval,wascontrolledandtracked.Usethetablebelowtoprovidetheversionnumber,theauthorimplementingtheversion,thedateoftheversion,thenameofthepersonapprovingtheversion,thedatethatparticularversionwasapproved,andabriefdescriptionofthereasonforcreatingtherevisedversion.]

Version

#

Implemented

By

Revision

Date

Approved

By

Approval

Date

Reason

1.0

UPTemplateVersion:

11/30/06

NotetotheAuthor

[ThisdocumentisatemplateofaChangeManagementPlandocumentforaproject.Thetemplateincludesinstructionstotheauthor,boilerplatetext,andfieldsthatshouldbereplacedwiththevaluesspecifictotheproject.

∙Blueitalicizedtextenclosedinsquarebrackets（[text]）providesinstructionstothedocumentauthor,ordescribestheintent,assumptionsandcontextforcontentincludedinthisdocument.

∙Blueitalicizedtextenclosedinanglebrackets（）indicatesafieldthatshouldbereplacedwithinformationspecifictoaparticularproject.

∙Textandtablesinblackareprovidedasboilerplateexamplesofwordingandformatsthatmaybeusedormodifiedasappropriatetoaspecificproject.Theseareofferedonlyassuggestionstoassistindevelopingprojectdocuments;theyarenotmandatoryformats.

Whenusingthistemplateforyourprojectdocument,itisrecommendedthatyoufollowthesesteps:

1.Replacealltextenclosedinanglebrackets（i.e.,）withthecorrectfieldvalues.Theseanglebracketsappearinboththebodyofthedocumentandinheadersandfooters.TocustomizefieldsinMicrosoftWord（whichdisplayagraybackgroundwhenselected）:

a.SelectFile>Properties>SummaryandfillintheTitlefieldwiththeDocumentNameandtheSubjectfieldwiththeProjectName.

b.SelectFile>Properties>CustomandfillintheLastModified,Status,andVersionfieldswiththeappropriateinformationforthisdocument.

c.AfteryouclickOKtoclosethedialogbox,updatethefieldsthroughoutthedocumentwiththesevaluesbyselectingEdit>SelectAll（orCtrl-A）andpressingF9.OryoucanupdateanindividualfieldbyclickingonitandpressingF9.ThismustbedoneseparatelyforHeadersandFooters.

2.Modifyboilerplatetextasappropriatetothespecificproject.

3.Toaddanynewsectionstothedocument,ensurethattheappropriateheaderandbodytextstylesaremaintained.StylesusedfortheSectionHeadingsareHeading1,Heading2andHeading3.StyleusedforboilerplatetextisBodyText.

4.ToupdatetheTableofContents,right-clickandselect“Updatefield”andchoosetheoption-“Updateentiretable”

5.Beforesubmissionofthefirstdraftofthisdocument,deletethis“NotestotheAuthor”pageandallinstructionstotheauthor,whichappearthroughoutthedocumentasblueitalicizedtextenclosedinsquarebrackets.]

TABLEOFCONTENTS

1Introduction5

1.1PurposeofTheChangeManagementPlan5

2ChangemanagementProcess5

2.1ChangeRequestProcessFlowRequirements5

2.2ChangeRequestFormandChangeManagementLog6

2.3EvaluatingandAuthorizingChangeRequests6

2.3.1ChangeControlBoard7

3Responsibilities7

AppendixA:

ChangeManagementPlanApproval8

AppendixB:

References9

AppendixC:

KeyTerms10

AppendixD:

ChangeRequestFormExample11

AppendixE:

ChangeManagementLogTemplate12

1

Introduction

1.1PurposeofTheChangeManagementPlan

[ProvidethepurposeoftheChangeManagementPlan.Thisdocumentshouldbetailoredtofittheparticularprojectneeds.]

TheChangeManagementPlandocumentsandtacksthenecessaryinformationrequiredtoeffectivelymanageprojectchangefromprojectinceptiontodelivery.

TheChangeManagementPlaniscreatedduringthePlanningPhaseoftheproject.Itsintendedaudienceistheprojectmanager,projectteam,projectsponsorandanyseniorleaderswhosesupportisneededtocarryouttheplan.

2ChangemanagementProcess

TheChangeManagementprocessestablishesanorderlyandeffectiveprocedurefortrackingthesubmission,coordination,review,evaluation,categorization,andapprovalforreleaseofallchangestotheproject’sbaselines.

2.1ChangeRequestProcessFlowRequirements

[Outlinetheprojectteam’sagreeduponchangerequest（CR）processflow.Thefollowingoutlinesagenericchangerequestprocessflow.]

Step

Description

GenerateCR

AsubmittercompletesaCRFormandsendsthecompletedformtotheChangeManager

LogCRStatus

TheChangeManagerenterstheCRintotheCRLog.TheCR’sstatusisupdatedthroughouttheCRprocessasneeded.

EvaluateCR

ProjectpersonnelreviewtheCRandprovideanestimatedlevelofefforttoprocess,anddevelopaproposedsolutionforthesuggestedchange

Authorize

Approvaltomoveforwardwithincorporatingthesuggestedchangeintotheproject/product

Implement

Ifapproved,makethenecessaryadjustmentstocarryouttherequestedchangeandcommunicateCRstatustothesubmitterandotherstakeholders

2.2

ChangeRequestFormandChangeManagementLog

[ListanddefinethedataelementstheprojectteamneedstoincludeontheChangeRequestFormandintheChangeManagementLog.ExamplesoftheseareprovidedinAppendixDandAppendixE.Ataminimum,thefollowingdatashouldbeincludedontheproject’sChangeRequestFormandChangeManagementLog.]

Element

Description

Date

ThedatetheCRwascreated

CR#

AssignedbytheChangeManager

Title

Abriefdescriptionofthechangerequest

Description

Descriptionofthedesiredchange,theimpact,orbenefitsofachangeshouldalsobedescribed

Submitter

NameofthepersoncompletingtheCRFormandwhocananswerquestionsregardingthesuggestedchange

Phone

Phonenumberofthesubmitter

E-Mail

Emailofthesubmitter

Product

Theproductthatthesuggestedchangeisfor

Version

Theproductversionthatthesuggestedchangeisfor

Priority

Acodethatprovidesarecommendedcategorizationoftheurgencyoftherequestedchange（High,Medium,Low）

2.3EvaluatingandAuthorizingChangeRequests

[Inordertoevaluateandprioritizeachangerequest,the“priority”and“type”ofthechangearetakenintoconsideration.Usethefirstandsecondtablesbelowtolistanddefinethe“priority”and“type”dataelementsthatareapplicablefortheproject.Thethirdtableprovidesexamplesofcommonlyusedprojectstatustypes.Thelistofelementsisatthediscretionoftheprojectmanager.]

Changerequestsareevaluatedusingthefollowingprioritycriteria:

Priority

Description

High

Medium

Low

Changerequestsareevaluatedandassignedoneormoreofthefollowingchangetypes:

Type

Description

Scope

Changeaffectingscope

Time

Changeaffectingtime

Duration

Changeaffectingduration

Cost

Changeaffectingcost

Resources

Changeaffectingresources

Deliverables

Changeaffectingdeliverables

Product

Changeaffectingproduct

Processes

Changeaffectingprocess

Quality

Changeaffectingquality

Changerequestsareevaluatedandassignedoneofthefollowingstatustypes:

Status

Description

Open

Entered/Openbutnotyetapprovedorassigned

WorkinProgress

CRapproved,assigned,andworkisprogressing

InReview

CRworkiscompletedandinfinalreviewpriortotesting

Testing

CRworkhasbeenreviewedandisbeingtested

Closed

CRworkiscomplete,haspassedalltests,andupdateshavebeenreleased.

2.3.1ChangeControlBoard

[AChangeControlBoard（CCB）isaformallyconstitutedgroupofstakeholdersresponsibleforapprovingorrejectingchangestotheprojectbaselines.Thisgroupmaymeetonapredefinedscheduleoronanasneededbasis.ThetablebelowprovidesabriefdescriptionofpersonnelactingastheChangeControlBoard（CCB）andtheirrole/levelofauthoritywithinthatgroup.]

Role

Name

Contact

Description

[InsertRole]

[InsertName]

[InsertContact#]

[InsertRoleDescription]

3Responsibilities

[Provideabriefdescriptionofpersonsresponsibleforeachstepofthechangemanagementprocessfortheproject.]

Role

Name

Contact

Description

ProjectManager

ChangeManager

[InsertRole]

[InsertName]

[InsertContact#]

[InsertRoleDescription]

AppendixA:

ChangeManagementPlanApproval

TheundersignedacknowledgetheyhavereviewedtheChangeManagementPlanandagreewiththeapproachitpresents.ChangestothisChangeManagementPlanwillbecoordinatedwithandapprovedbytheundersignedortheirdesignatedrepresentatives.

[Listtheindividualswhosesignaturesaredesired.ExamplesofsuchindividualsareBusinessSteward,ProjectManagerorProjectSponsor.Addadditionallinesforsignatureasnecessary.Althoughsignaturesaredesired,theyarenotalwaysrequiredtomoveforwardwiththepracticesoutlinedwithinthisdocument.]

Signature:

Date:

PrintName:

Title:

Role:

Signature:

Date:

PrintName:

Title:

Role:

Signature:

Date:

PrintName:

Title:

Role:

AppendixB:

Ref