professional documents
home
Profile
docsters
request
Blogs
Upload
about me
contact me
user photo
submit clear
Word Document

Change Management Plan center doc

Change Management Plan Project Manager: Change may be encountered during the life of the _______________________ project. The project scope, schedule, budget, and resources will all be areas of potential change. The sources of these changes will be internal changes initiated by the project team; external changes initiated by the contractor or consultant; and external changes that are a result of stakeholder requests, resource availability, etc. The acknowledgement that change may be encountered, along with a commitment to on-time, on-budget delivery of the agreed upon project scope emphasizes the importance of active project and change management for attaining project success. Managing change will require planning, discipline, and effective communication among the entire project team (including specialty groups, consultants, and contractors), management, customers and stakeholders. As the Change Management Plan is executed, the following should occur: improved relationship with customers, improved financial performance, reduced project delays, better project teamwork, improved management of project quality, and ultimately on-time delivery. The following defines the plan the team will use to Manage Change. Potential change may fall in the following categories or types: Scope Deliverables Schedule Technical change Project Cost Resources/Technologies/Materials Available Funding Process/Policy Staffing Unforeseen field conditions, weather, etc. Step-by-Step Process to Manage Change Changes proposed or encountered will be addressed using the following process. 1. Identify and Manage Change Issues During “Plan the Work”; change identification involves determining what changes may occur during the project life cycle. Planning for change can maximize positive and minimize negative impacts to the project. Review business processes and thresholds in the Project Control & Reporting Guide, the Guide can be located at: wwwi.wsdot.wa.gov/projectreporting/During “Work the Plan”; when change occurs implement the Change Management Plan when it is first encountered. Identify the source and nature of the change as follows: Determine the category or type of change. Establish a formal change description. Determine the potential impact of the change. Document the origin of the change (who initiated it, what precipitated it). Identify who may potentially be affected. Identify who is responsible for the managing the change. 2. Verify and Analyze the Change Concurrence of the change condition will be obtained from the Project Manager. If a change condition exists analyze the effects of the change to the project. • Evaluate and quantify the impact to the project performance baseline (scope, schedule, and/or budget) • Does it introduce additional risks to the project? • Evaluate the effects on other project tasks or deliverables. • Identify and coordinate with effected specialty groups, contractors, consultants, etc. • Brainstorm, analyze, and prioritize strategies for change management. • When necessary, consult with subject matter experts. 3. Develop a Mitigation/Recovery Strategy. A response strategy is the process of developing options and determining actions to enhance positive changes and to reduce threats to project objectives. Document the analysis: • What needs to be done, who will do it, and by when? • Formally establish the scope of the change & direction for incorporating the changed work or conditions. • Formally establish required adjustments to the project performance baseline. • Identify level of authority for endorsement. • Provide appropriate notifications to team members affected by the change. 4. Gain endorsement for the change. • Notify and consult with Region Management, Region Program Management, and Project Control and Reporting regarding the change and its impacts. • Obtain endorsement from the appropriate level of authority 5. Update the Project Performance Baseline and monitor the effects of change. • Update the Project Management Plan and Project Performance Baseline to document the change. • Identify responsibilities and timelines for carrying out • Monitor and evaluate implementation 6. Communicate changes per this Change Management Plan and the Project Communication Plan. • Notify appropriate team members, management, contractors, consultants, stakeholders, and customers as identified in the Communication and Change Management Plans.
rate this doc
email this doc
embed this doc
add to folder
digg reddit stumble delicious
flag this doc
624
153
8(2)
0
1/6/2008
English
search termpage on Googletimes searched
Preview

Change Management Plan Template

ocak 1/10/2008 | 783 | 138 | 0 | business
Preview

Project Change Control Management Plan Template

ocak 1/28/2008 | 658 | 135 | 0 | business
Preview

Organizational Change Management Plan Template

ocak 1/10/2008 | 1960 | 214 | 0 | business
Preview

Change and Configuration Management Plan Template

ocak 1/28/2008 | 433 | 87 | 0 | business
Preview

Change and Resistance to change

nbalajhi 6/4/2008 | 51 | 8 | 0 | business
Preview

Change Management

banter 1/8/2008 | 711 | 216 | 0 | business
Preview

Change Management Guideline

user002 2/5/2008 | 297 | 62 | 0 | business
Preview

Change and Configuration Management Standards

ocak 1/28/2008 | 292 | 75 | 0 | business
Preview

Project Management Plan

banter 1/8/2008 | 1209 | 179 | 0 | business
Preview

Project Management Plan 1

banter 1/8/2008 | 2288 | 475 | 1 | business
Preview

Change control management process-example

ocak 1/28/2008 | 445 | 145 | 0 | business
Preview

Project Management - Change Register

jpberes 12/24/2007 | 350 | 70 | 0 | business
Preview

Change Control Plan Template

ocak 1/6/2008 | 705 | 65 | 0 | business
Preview

OAKS Change Management Plan

Ohio 6/18/2008 | 9 | 0 | 0 | legal
Preview

Project Management Plan - Generic

ocak 1/10/2008 | 1617 | 289 | 0 | business
Preview

Template Project Scale[1]

ocak 1/28/2008 | 1379 | 1540 | 2 | business
Preview

Strategic Asset Plans[1]

ocak 1/28/2008 | 798 | 284 | 2 | business
Preview

Steering Committee Charter template[1]

ocak 1/28/2008 | 1571 | 340 | 3 | business
Preview

Status Report Management Process Flow example[1]

ocak 1/28/2008 | 1685 | 549 | 1 | business
Preview

Status Report example[1]

ocak 1/28/2008 | 1898 | 712 | 2 | business
Preview

Software Requirement Specifications Document Template[1]

ocak 1/28/2008 | 1483 | 267 | 1 | business
Preview

Scope Statement Development Instructions[1]

ocak 1/28/2008 | 567 | 35 | 0 | business
Preview

Schedule Of Excess Risks[1]

ocak 1/28/2008 | 290 | 19 | 0 | business
Preview

Sample Performance Based Requirement Template for use with Task Orders[1]

ocak 1/28/2008 | 470 | 22 | 0 | business
Preview

Risk Value Assessment Tool

ocak 1/28/2008 | 494 | 64 | 1 | business
 
review this doc