Pm Change Management

Front 1

Three Types of Change Requests

Back 1

Corrective Actions
Preventive Actions
Defect Repairs

Front 2

Corrective Actions

Back 2

Bring the work of the project into alignment with the project plan.

Front 3

Preventive Actions

Back 3

Implemented to help reduce the probability of a negative risk event.

Front 4

Defect Repairs

Back 4

Either correct or replace components that are substandard or malfunctioning.

Front 5

Change Control System

Back 5

Documented procedures that describe and manage the documentation required to request and track the changes and the updates to the project plan. Uses Integrated change control technique. Three big project killers.

Front 6

Three Big Project Killers

Back 6

Inadequate planning
Poor risk planning
Inadequate change control processes

Front 7

Integrated Change Control

Back 7

Looks at the impact of any change across all aspects of the plan. Impacts have an impact on the triple constraints, scope, or any combination of these factors.

Front 8

Three Constraints

Back 8

Time
Cost
Quality

Front 9

Change Management System process includes

Back 9

Change request forms (and other documentation)
Change request log
Analysis of impacts of change
CCB
Coordination and communication with stakeholders
Updating affected project-planning documents

Front 10

Change Request Documentation

Back 10

After PM plan is approved, all change requests must go through the change control system. Change requests should always be in writing. A form will be provided to document them, the reason change is needed, and the impact if the change is not made.

Front 11

Change Request Log: What should happen when Change request is submitted

Back 11

It should be assigned an identifying number for tracking.
Recorded in the change request log.
An analysis of the change request.

Front 12

Analyzing Change

Back 12

Analyzed by experts working on the change request impacts, with input from the PM. Specific elements of the change request should be analyzed (equipment, resource hours, etc). PM will analyze the schedule, budget, and resource allocations to determine impacts. Info is presented to the CCB for approval or rejection.

Front 13

Emergency Change

Back 13

Established separate procedures. Includes description and definition of an emergency, authority level of PM, and process for reporting the change after. Requires follow-up with CCB and completion of formal change request.

Front 14

Four Elements of Change

Back 14

Resource changes
Requirements changes
Infrastructure changes
Configuration changes

Front 15

Resource Change

Back 15

When a team member is added or leaves, important to document the reason, the name of replacement, person requesting change, and impact.

Front 16

Requirements Change

Back 16

As detail is added or updated to clarify expectations, make sure they do not involve a scope change. New requirements go through the change control process.

Front 17

Infrastructure Change

Back 17

Infrastructure remains permanently after the project is completed. Components that may change include: Computing systems, Software development environment, Server operating platforms, etc. Infrastructure changes can have a major impact on overall project plan.

Front 18

Configuration Change

Back 18

Design teams will sometimes make a decision about a software or hardware configuration only to find out that another configuration would work better.

Front 19

Change Control Board (CCB)

Back 19

Established to review all change requests. Includes stakeholders, managers, team members, and others who have a connection to the project. Change request and the impact analysis are given to the board for review to approve, deny, or delay it. Note their decision on the change request log.