It+Project+Templates

June 13, 2018 | Author: tmujtaba | Category: Change Management, Project Manager, Accountability, Business, Leadership & Mentoring


Comments



Description

Your Organization Name Your Project Name Change Management PlanPrepared by: Version: Document #: Date: Your Name Your Version Your Reference # Release Date 0 .com and contains an embedded digital signature verifying its ownership. Document # Page i Version 1.Project Name Change Management Plan Proprietary Notice This document is the property of IT-Project-Templates. This document is released for the sole use of authorized clients and their delegates and may not be copied or reproduced for resale. 0 .Project Name Change Management Plan Approval Signatures Project Sponsor: Project Manager: Client Representative: Quality Assurance: Author: Name Name Name Name Name Signature: _____________________ Signature: _____________________ Signature: _____________________ Signature: _____________________ Signature: _____________________ Document # Page ii Version 1. 0 Release Notes Initial Draft Issue Date Document # Page iii Version 1.0 .Project Name Change Management Plan Revision History Version # 1. ......................1.............................................................4 3........1...............................................1................1...............0 .....1 1.............. CHANGE MANAGEMENT PROCEDURES............................................... CHANGE MANAGEMENT OVERVIEW.............2......... Change Management Approach..........................4 3........................................ Close Change Request.............4......................2 2................ Asses Change Request..............5......................................................... Change Management Cycle............2.........3 3.....................3 2.............................................................................................4 3...........................................................................1...................4 3.....4 3..................6 APPENDIX B – CHANGE CONTROL LOG..........................................4.......... Approve/Reject Change Request............... Raise Change Request................................ Sources of Change..........1 1................................... Audience.................................................2...............................................3................................. Purpose.............................................1..............2 2............ INTRODUCTION.................. Roles and Responsibilities.......3........ Implement Change.......1.................5 APPENDIX A – CHANGE REQUEST..........................1....................................................................7 Document # Page iv Version 1.2 2.......................................1 2.........................Project Name Change Management Plan Table of Contents 1.... and timing as set out in the Project Plan Deliverable. product and process Quality 1.2.Project Name Change Management Plan 1. Audience This Change Management Plan is intended for the Project Board. Purpose The purpose of this Change Management Plan is to set out the methods and procedures to handle all changes affecting this project’s: • • Resources. key stakeholders. and the core project team. INTRODUCTION 1.1. costs.0 . Document # Page1 Version 1. Change Management Cycle The Change Management Cycle is comprised of the following events: • • • • • Raise and record Change Request (CR) Assess impact and value of change Present assessment results and obtain approval Implement change and re-baseline plan Close CR The following diagram represents the flow of change management events. 2.Project Name Change Management Plan 2. processes and procedures are used for all project changes Facilitate efficient and prompt handling of all changes Maintain a proper balance between the benefits of change and the detrimental impact of change on the Project Plan.0 . Change Management Approach This Change Management Plan employs an industry standard cyclical approach to: • • • Ensure standardized methods.2. Document # Page2 Version 1. CHANGE MANAGEMENT OVERVIEW 2.1. scope. Technical and User representatives. log and track CR’s Change Advisory Board – comprised of Sponsor.0 . Legitimate changes may stem from: • • • • Responses to problems internal to the project Externally imposed requirements Change in business requirements or strategy Proactive changes to improve performance or benefit 2.Project Name Change Management Plan 2. Sources of Change All project changes must enter the Change Management cycle in the format of a Change Request. responsible for accepting or rejecting CR implementation Document # Page3 Version 1. authorizing and funding changes Project Coordinator – assists with estimating and scheduling change against existing baseline Configuration Manager/Change Manager – accept. schedule and resources Project Sponsor – responsible for reviewing.assigned full responsibility for facilitating or executing the change management process to officially provide new requirements. Roles and Responsibilities The following list outlines the key responsibilities of personnel involved in the Change Management process: • • • • • Project Manager .4.3. 3. such as the Project Manager. Document # Page4 Version 1.0 .3. sign-off represents a new agreement on the updated Project Plan. the project authority may direct the initiator to prepare a Change Request. CHANGE MANAGEMENT PROCEDURES 3. Based on the value judgement passed on the CR.4.2. The Project Manager completes a brief Business Case with the assistance of the Project Board members (technical and user representatives). costs and schedule are baselined. 3. This constitutes the initial informal change communication. Completion is assessed at the appropriate milestone.1. or that duty may be delegated to the Project Manager or Change Manager (if one exists for the project).1. A high level assessment is first performed by the Project Manager to determine if the CR is of sufficient magnitude to require independent funding for detailed assessment. Implement Change The new work required by the change is undertaken and completed according to the new Project Plan. The CR is assessed for its impact on the project plan (resourcing. A separate timeline is built for later incorporation into the master plan. Scope. costs and schedule) by the Project Manager and Project Coordinator. Success criteria or testing for the change are applied to the CR work. 3.1. or any other member of the Change Advisory Board or Project Board. If accepted. if and when the CR is approved.Project Name Change Management Plan 3. the Project Manager requests additional funding to carry out the extra assessment tasks. At this point.1. it is accepted or rejected.1. Once the details of the change have been recorded on a Change Request form. Raise Change Request The change initiator communicates the details of the change to any project authority. The new timeline. Project Sponsor. Asses Change Request The Change Request is escalated to the project core team for evaluation. Approve/Reject Change Request The results of the CR assessment are presented to the Change Advisory Board and/or the Project Board. If so. it is submitted to the Configuration Manager or Change Manager to log into the Change Log. 5. Close Change Request Following successful implementation and testing of the CR work.Project Name Change Management Plan 3. the Configuration Manager makes a closing entry in the Change Management Log.1.0 . Document # Page5 Version 1. T=Tech Chg Description of Change Request: Reason for Change: EVALUATION SECTION Identify requirements. D. & products/deliverables changes: Identify plan changes: Total Hours: Description of risks: Risks associated with making and not making changes to system.0 . A=Architecture Chg. D=Design Chg. and business: Recommendation: Evaluated by: DECISION APPROVAL SECTION Cancel __ Decision Approval Signatures: Sponsor: Technical/User Rep: Project Mgr: Postpone __ Reconsider on: ____________ Integrate into Project __ Date: Estimate of effort (hrs) : Document # Page6 Version 1. T): P=Plan/Sched Chg. A. project.Project Name Change Management Plan APPENDIX A – CHANGE REQUEST Change Request Form CHANGE IDENTIFICATION SECTION Change Control # Short Title: Requested by: Name or Project/Program Date: Affected System(s): Supporting Materials Attached (yes/no) Type of request (P. Project Name Change Management Plan APPENDIX B – CHANGE CONTROL LOG CHANGE MANAGEMENT LOG YOUR PROJECT NAME Impact and Deliverables affected No Issue date Requestor Title of request Resp.0 . Person Compl Date Status Document # Page7 Version 1.
Copyright © 2020 DOKUMEN.SITE Inc.