Project Management/Change Management

Change Management involves identifying, evaluating and managing changes throughout the project life-cycle.

Objectives and Skills
Objectives and skills for the change management portion of Project+ PK0-003 certification include:
 * Outline a process for managing changes to the project
 * Approvals required
 * Forms needed
 * Turnaround times
 * Document routing
 * Communication flow
 * Given a scenario, implement proper change management procedures
 * Identify change
 * Document using the appropriate change control forms
 * Perform impact analysis
 * Coordinate with the appropriate stakeholders to select the course of action
 * Update the appropriate project plan components based on the approved change request
 * Evaluate the impact of potential changes to triple constraint
 * Time / Schedule
 * Cost / resources
 * Quality
 * Scope

Objectives and skills for the change management portion of Project+ PK0-004 certification include:
 * Given a scenario, use the following change control process within the context of a project.
 * Change control process
 * Identify and document
 * Evaluate impact and justification
 * Regression plan (Reverse changes)
 * Identify approval authority
 * Obtain approval
 * Implement change
 * Validate change/quality check
 * Update documents/audit documents/version control
 * Communicate throughout as needed
 * Types of common project changes
 * Timeline change
 * Funding change
 * Risk event
 * Requirements change
 * Quality change
 * Resource change
 * Scope change

Readings

 * 1)  Change management
 * 2)  Change management (ITSM)
 * 3)  Change control
 * 4)  Change request
 * 5)  Change control board
 * 6)  Change impact analysis
 * 7)  Change management auditing
 * 8)  Change order
 * 9)  Scope creep
 * 10)  Change Log

Multimedia

 * 1) YouTube: What Is Change Management In Project Management Terms?
 * 2) YouTube: How to Lead Change Management
 * 3) YouTube: Do's & Don'ts of ITIL Change Management
 * 4) YouTube: How to Control Change Requests on a Project
 * 5) YouTube: Implement change more successfully with Impact Analysis
 * 6) YouTube: Change Management Process

Activities

 * 1) Read  Change management.
 * 2) * List John Kotters 8-step process for leading change.
 * 3) * Describe the factors of successful change management.
 * 4) Read  Change control board.
 * 5) * Mention the purpose of a change control board.
 * 6) * List examples of members of the change control board.
 * 7) * Define your CCB.
 * 8) Read  Change control.
 * 9) * Create a change control process.
 * 10) Watch the video How To Control Change Requests On a Project and read the article How to manage change requests.
 * 11) * Explain how change is fundamental to a project and the significant impact it can have on a project.
 * 12) * Elaborate how to control change requests.
 * 13) * Create a change request form.
 * 14) Read  Changelog and the article What is a change log?
 * 15) *Define and detail a change log.
 * 16) *Create a change log.

Lesson Summary

 * Change Management involves identifying, evaluating and managing changes throughout the project lifecycle.
 * Change Management is used to ensure that standardized methods and procedures are used for efficient and prompt handling of all changes to control.
 * The three main objectives are: influencing factors that create change to ensure that the change is beneficial, determining that a change has occurred and managing changes as they occur.
 * Change management would typically be composed of: raising and recording of changes, assessing the impact, cost, benefit and risk of proposed changes, developing business justification and obtaining approval, managing and coordinating change implementation, monitoring and reporting on implementation, reviewing and closing change requests.
 * Every change that enters the project must pass through this change control process.
 * A CCB (change control board) is a formal group of people responsible for approving or rejecting changes to a project. The primary functions of a CCB are to provide guidelines for preparing change requests, evaluating change requests and managing the implementation of approved changes.
 * When the change control board approves or declines the change request the change requestor is informed of the project decision. All decisions on change requests are documented for future reference. If an approved change request affects the project scope then configuration management is enforced. The authority of the change control board may vary from project to project, but decisions reached by the change control board are often accepted as final and binding.
 * A change log is a record of requests for change (RFCs) submitted for all changes in a service.
 * Change requests typically originate from one of five sources: problem reports that identify bugs that must be fixed, which forms the most common source, system enhancement requests from users, events in the development of other systems, changes in underlying structure and or standards (e.g. in software development this could be a new operating system), demands from senior management.
 * Change management procedures are formally documented and controlled.
 * Change impact analysis identifies the potential consequences of a change, or estimates what needs to be modified to accomplish a change.
 * Risk event is an occurrence that has a negative impact on the project.
 * Scope creep is a risk in most projects. It can be a result of poor change control, lack of proper initial identification of what is required to bring about the project objectives, weak project manager or executive sponsor, poor communication between parties and lack of initial product versatility.
 * Cost Control is a factor that creates cost fluctuation and variance that can be influenced and controlled using various cost management tools.
 * Successful change management is more likely to occur if the following are included:
 * Define measurable Project stakeholder aims and create a business case for their achievement (which should be continuously updated)
 * Monitor assumptions, risks, dependencies, costs, return on investment, dis-benefits and cultural issues
 * Effective communication that informs various stakeholders of the reasons for the change (why?), the benefits of successful implementation (what is in it for us, and you) as well as the details of the change (when? where? who is involved? how much will it cost? etc.)
 * Devise an effective education, training and/or skills upgrading scheme for the organization
 * Counter resistance from the employees of companies and align them to overall strategic direction of the organization
 * Provide personal counseling (if required) to alleviate any change-related fears
 * Monitoring of the implementation and fine-tuning as required


 * In some cases, even after a change is evaluated and approved, it may be necessary to return to the project state prior to the incorporation of the change. For this reason, the project manager creates a Regression Plan.
 * Turnaround time means the amount of time taken to fulfill a request.

Key Terms

 * CCB (Change Control Board)
 * A committee that makes decisions regarding whether or not proposed changes to a software project should be implemented.


 * change impact analysis (IA)
 * Identifies the potential consequences of a change, or estimating what needs to be modified to accomplish a change.


 * change log
 * Record of all notable changes made to a project.


 * change management
 * Structured process and set of tools for managing the people side of change such that business results are achieved, on time and on budget.


 * change request
 * Document containing a call for an adjustment of a system.


 * cost control
 * A factor that creates cost fluctuation and variance that can be influenced and controlled using various cost management tools.


 * organizational change management
 * Includes specific actions and steps that can be taken to implement a change management program. Prosci's 3-phase change management process (preparing for, managing and reinforcing change) is a methodology for implementing organizational change management.


 * regression plan
 * A plan developed in case the change needs to be reversed.


 * risk event
 * An occurrence that has a negative impact on the project


 * schedule control
 * The actual process of maintaining control of the changes that may occur to a schedule.


 * scope change
 * A change to the agreed scope and objectives of the project to accommodate a need not originally defined to be part of the project.


 * triple constraint
 * A combination of the three most significant restrictions on any project- scope, schedule and cost. It is sometimes referred to as the project management triangle or the iron triangle.


 * turnaround time (TAT)
 * The amount of time taken to fulfill a request.

Assessments

 * Flashcards: Quizlet: Chapter 7: Change Management
 * Quiz: Quizlet: Chapter 7: Change Management