Transcription
Configuration Management PlanProject NameVersionYour Company NameConfiguration Management PlanDateConfidential – 2015 Documentation Consultants (www.SDLCforms.com)Document: 2300Page 1 of 11
Configuration Management PlanProject NameVersionRevision HistoryDateVersionAuthorChangeCOPYRIGHT NOTICEConfidential – 2015 Documentation ConsultantsAll rights reserved. These materials are for internal use only. No part of these materials may bereproduced, published in any form or by any means, electronic or mechanical, including photocopy or anyinformation storage or retrieval system, nor may the materials be disclosed to third parties without the writtenauthorization of (Your Company Name).Confidential – 2015 Documentation Consultants (www.SDLCforms.com)Document: 2300Page 2 of 11
Configuration Management PlanProject NameVersionTable of Contents1 Purpose . 42 Target audience . 43 Abbreviations and glossary of terms. 53.13.2Abbreviations . 5Glossary of Terms. 54 Organization. 64.14.2Activities and Responsibilities . 6Decision Process and Responsibilities . 75 Configuration Control Board (CCB) . 75.1Individual CCB Responsibilities. 86 The Configuration Control process . 96.16.2Definition of Configuration Control . 9Configuration Control Steps . 97 Configuration audits. 108 Configuration Management Plan Approval . 11Confidential – 2015 Documentation Consultants (www.SDLCforms.com)Document: 2300Page 3 of 11
Configuration Management PlanProject NameVersionNote: Text displayed in blue italics is included to provide guidance to the author and should bedeleted before publishing the document. In any table, select and delete any blue line text; thenclick Home Styles and select “Table Text” to restore the cells to the default value.1PURPOSEThe primary objective of a Configuration Management (CM) Plan is to inform project stakeholders abouthow CM is used to manage the project, what tools are used, and how they will be implemented toachieve project success.The CM Plan defines the project’s structure and methods for: 2Identifying, defining and baselining Configuration Items (CI)Controlling modifications and release of CI itemsRecording and reporting the status of CIs and any requested modificationEnsuring completeness, accuracy and consistency of CIsControl of the storage, handling and delivery of the CIs.TARGET AUDIENCEThe minimal intended audience for the plan includes the following personnel:oooooooProject sponsorsProject ManagerProject teamSoftware Configuration ManagerQuality ManagerDevelopment ManagerLead Engineer.Confidential – 2015 Documentation Consultants (www.SDLCforms.com)Document: 2300Page 4 of 11
Configuration Management PlanProject NameVersion3ABBREVIATIONS AND GLOSSARY OF guration ManagementCIConfiguration ItemSCMSoftware Configuration ManagerGlossary of TermsTermMeaningConfiguration ManagementInform project stakeholders about how CM is used to managethe project, what tools are used, and how they will beimplemented to achieve project success.Configuration Control BoardThe CCB is comprised of the project sponsor, project manager,software configuration manager, the Lead Engineer and anysoftware engineers (depending on issues) for configurationitems under discussion.Confidential – 2015 Documentation Consultants (www.SDLCforms.com)Document: 2300Page 5 of 11
Configuration Management PlanProject NameVersion4ORGANIZATIONDescribe the Configuration Management organization. Software configuration is managed byteam members. Responsibilities are shared between:oooo4.1Software Configuration Manager (SCM)Project Manager (PM)Quality Manager (QM)Development Manager (DM).Activities and ResponsibilitiesList the functions required to manage the configuration of the software and the associatedresponsibilities.Setting Up Project ActivitiesIndividual ResponsibleIdentify configuration itemsSoftware Configuration ManagerInstall bug repository tool and set up a databaseSoftware Configuration ManagerDefine the configuration processSoftware Configuration ManagerProject Planning Life Cycle ActivitiesIndividual ResponsibleCreate version, write version delivery documentSoftware Configuration ManagerApprove reference configurationSoftware Configuration ManagerDo configuration auditsSoftware Configuration ManagerArchive reference versionSoftware Configuration ManagerDo configuration auditsQuality ManagerVerify version to be delivered and authorize deliveriesProject ManagerManagement ActivitiesIndividual ResponsibleManage versions and archivesSoftware Configuration ManagerManage configuration recordsSoftware Configuration ManagerManage reference space and its access control listSoftware Configuration ManagerManage quality reportsQuality ManagerConfidential – 2015 Documentation Consultants (www.SDLCforms.com)Document: 2300Page 6 of 11
Configuration Management PlanProject NameVersion4.2Decision Process and ResponsibilitiesList the responsibilities required to manage the configuration of the software and theassociated responsibilities.Project ActivitiesPresent a configuration state of the componentsimpacted by the activitySoftware Configuration ManagerPresent a documentation state of the componentsimpacted by the activitySoftware Configuration ManagerProcess Audit Activities5Individual ResponsibleIndividual ResponsibleAccomplish the configuration process auditProject ManagerPresent the records of the configuration managementprocessSoftware Configuration ManagerPresent the quality records of the configurationmanagement processQuality ManagerPresent the records of the documentation managementprocessSoftware Configuration ManagerCONFIGURATION CONTROL BOARD (CCB)The CCB is comprised of the project sponsor, project manager, software configuration manager, theLead Engineer and any software engineers (depending on issues) for configuration items underdiscussion.The CCB is responsible for the following activities:oooReview and approve/reject configuration change requestsEnsure all approved changes are added to the Configuration Management Database (CMDB)Seeking clarification on any Configuration Items, as becomes necessary.Confidential – 2015 Documentation Consultants (www.SDLCforms.com)Document: 2300Page 7 of 11
Configuration Management PlanProject NameVersion5.1Individual CCB ResponsibilitiesRoleProject SponsorResponsibilities Project Manager Software ConfigurationManager Lead Engineer Software Engineers Chairing all CCB meetingsProvide approval for any issues that require additional scope,time and cost.Participation in CM meetings.Overall responsibility for all CM activities.Identification of Configuration Items (CIs).Communicating CM activities to project sponsors andstakeholders.Participation in CM meetings.Re-baselining, if necessary, any items impacted by CMchanges.Overall management of the CMDB.Identification of CIs.Providing configuration standards and templates to the projectteam.Providing any required configuration training.Assigning the CI to a Lead Engineer.Participation in CM meetings.Creating a focus group of engineers to develop the changerecord.Ensure all change requests comply with approved templatesand standards prior to the CCB.Identification of CIs.Each member of the selected focus group will provide input tothe change required prior to submitting the change request tothe Lead Engineer for review and presentation at the CCB.Confidential – 2015 Documentation Consultants (www.SDLCforms.com)Document: 2300Page 8 of 11
Configuration Management PlanProject NameVersion6THE CONFIGURATION CONTROL PROCESS6.1Definition of Configuration ControlConfiguration Control is the process of systematically controlling and managing all steps of theconfiguration throughout the project life cycle. In order to effectively accomplish project ConfigurationManagement, it is important to use a process which ensures only necessary configuration changes areimplemented.As with any change management efforts, configuration change decisions must be made with theunderstanding of the impact of the change. Configuration control is an integral and important part ofthe Configuration Management Plan.6.2Configuration Control StepsAll CIs are identified by the project team. The sequence of processing a CI is as follows:oooooooooooThe Configuration Manager will assign a CI name.The CI will be entered into the CMDB in an “initiate” status.The CI will then be assigned to an engineer focus group.Each member of the focus group will have the ability to access the CI through the CMDB,make changes and edits, and enter the CI back into the CMDB with a description of thechange annotated in the CMDB log.It is imperative that for any software changes, testing is conducted by the focus group inorder to validate the changes made. The focus group Lead Engineer is responsible forensuring that successful testing has been accomplished. The Lead Engineer is alsoresponsible for assigning new version numbers and CMDB status for any changes made byhis/her assigned focus group.The Lead Engineer, Configuration Manager, and Project Manager will work together toensure that these relationships are fully understood.The Lead Engineer and Configuration Manager will then be responsible for illustrating theserelationships and co-dependencies in the CMDB to ensure a complete understanding ofeach CI and how they related to one another.Any configuration changes which are identified by the project team or stakeholders must becaptured in a Configuration Change Request (CCR) and submitted to the CCB.The CCB will review, analyze, and approve/reject the request based on the impact, scope,schedule and cost of the proposed change.If the change is approved, the project requirements will be re-baselined, if necessary, and allchanges will be communicated to the project team and stakeholders by the Project Manager.Rejected CCRs may be resubmitted with additional information for reconsideration by theCCB.Confidential – 2015 Documentation Consultants (www.SDLCforms.com)Document: 2300Page 9 of 11
Configuration Management PlanProject NameVersion7CONFIGURATION AUDITSAudits are an important part of the project and configuration management. The purpose of an audit isto ensure that established processes are being followed as intended and to provide an opportunity tocorrect any deviations from these processes.Configuration audits will be an ongoing part of the life cycle. The express purpose of the configurationaudit is to ensure all team members understand their roles and that they are following the establishedprocedures and processes for configuration management.Project audits will be accomplished by the CM and will occur prior to any major software release or atthe Project Manager or Sponsor’s discretion, if they determine the need exists.Throughout the project, the CM will work closely with Lead Engineers to ensure that all configurationprocesses and procedures are being followed.The CM will accomplish the following tasks:oooooooooEstablish an audit environment in the CMDB.Copy all of the latest software, data and document versions in to the audit environment;Ensure that all versions are correctly numbered and the version control has been performingproperly.Analyze historical versions and timestamps of all software, data and documents to ensurethat all changes/edits were properly recorded and captured.Copy the latest software versions and conduct software testing to ensure requirements arebeing met.Ensure all required artifacts are present and current in the CMDB.Ensure all approved CCRs have been incorporated into the project and are recorded in theCMDB.The CM will compile his/her audit findings. For each finding, the CM must work with theProject Manager and team to identify the corrective action(s) necessary to resolve thediscrepancy and assign responsibility for each corrective action.Upon completion of the project audit and findings, the CM will note all discrepancies andcompile a report to be presented to the Project Manager, project sponsor and senior ITexecutives.Confidential – 2015 Documentation Consultants (www.SDLCforms.com)Document: 2300Page 10 of 11
Configuration Management PlanProject NameVersion8CONFIGURATION MANAGEMENT PLAN APPROVALThe undersigned acknowledge that they have reviewed the Project Name ConfigurationManagement Plan and agree with the information presented therein.List the individuals whose signatures are desired. Examples of these individuals are shownbelow.TitleProject SponsorSignatureRoleDirector, AccountsPayablePrint NameDateTitleProject ManagerSignatureRoleProject ManagerPrint NameDateTitleSoftware Configuration ManagerSignatureRoleManager, SCMPrint NameDateTitleRoleSignaturePrint NameDateTitleRoleSignaturePrint NameDateConfidential – 2015 Documentation Consultants (www.SDLCforms.com)Document: 2300Page 11 of 11
As with any change management efforts, configuration change decisions must be made with the understanding of the impact of the change. Configuration control is an integral and important part of the Configuration Management Plan. 6.2 Configuration Control Steps All CIs are identified by the project team. The sequence of processing a CI is as .
