Skip to Main Content
Skip to Navigation
Project Management Orientation

Guidelines for Managing Change 

Follow these guidelines for managing project changes:

How to Implement the Guidelines for Managing Change
  
IBM's policy is that all projects have change management procedures in place.
  
You, as the project manager, must implement these guidelines on every project in a strict and conscientious way.  The change management process must be executed and strictly enforced in order to maintain control of your project.
  
The process of managing change should not be complex.  Problems arise, however, when project managers, in an attempt to reduce bureaucracy, adopt an informal process to handle change requests.  Misunderstandings often result from informality.  As project manager, you might find that, because the project is committed to deliver a changed output, you have to absorb the added cost involved and scramble to meet the old schedule.  Changes to your project might also affect projects managed directly by the customer or other organizations.  For these reasons, change control is an important part of the project manager's job on every project.
1: Getting Started
2: Define the Project Team
3: Team Management
4: Identify and Validate Requirements
5: Create Decomposition Structures
6: Risk Management
7: Project Estimates
8: Project Schedules
9: Change Management
10: Project Control and Execution
Defining the Project
11: Project Management Review
12: Project Closeout
13: Project Management Tool Suite
14: Self-Assessment and Final Exam
Fast Points
Concepts
Seven Keys
Case Study
WWPMM
Mentor
Check Point
Previous button
Next button
Print button
Help button
Glossary button
Exit course button