Hello, Thank you for visiting my blog. I would greatly appreciate contributions in terms of new thoughts & concepts towards this blog. Please Click on the links above to access the different sections of the blog. If you want some perspective on how you or your company needs to enhance their Sales or Client Management Capabilities, please email me (Shubhanjan Saha) at shubhanjan.saha@gmail.com & do not forget to subscribe to my posts ! :-) .

Click here to go to Dealsupportguy.com

Monday, October 3, 2011

Change Management Plan document

You can use an Change Management Plan document to address changes which may be encountered during the project lifecycle. Typical areas of change occur in the scope, schedule, budget, and resources.
Use this Change Management Plan to:
  • Define the process, tools, and stakeholders that will be used to manage any changes to the project.
  • Specify how change requests will be accepted, analyzed, and assessed regarding potential impact on the schedule, budget and scope
  • Improve customer relationships, establish greater financial performance, accountability, reduction in project delays, and on-time deliverables.
  • Ensure that changes will be proactively managed as they occur and that all changes are coordinated across the project.
Table of Contents
1 Introduction
1.1 Audience
1.2 Purpose
1.3 Constraints
1.4 Change Management Guidelines
1.5 Anticipated Change Volumes
1.6 Points of Contact
2 Roles and responsibilities
2.1 Change Management Chart
2.2 Roles and Responsibilities
3 Change Management Process
3.1 Raise Change Request
3.2 Evaluate Change Request
3.2.1 Change Request Criteria
3.2.2 Change Type
3.2.3 Status Type
3.3 Update Change Request Log
3.4 Assess the Change Request
3.4.1 Perform Feasibility Study
3.5 Approve/Reject Change Request
3.6 Implement Change Request
3.7 Update the Project Plan
4 Schedule
5 Costs

If you want some perspective on how you or your company needs to enhance their Sales/Client Management Capabilities, please email me (Shubhanjan Saha) at shubhanjan.saha@gmail.com

No comments: