Skip to Main Content
Skip to Navigation
Project Management Orientation

Types of Change 

Changes might be technical or contractual as shown in the following figure.

Technical changes.  Technical changes result from the implementation of the solution.  Normally, the changes are generated internally and are within the scope of the project.  An example of a technical change is implementing a program that automates test cases.  This program helps improve the quality of the testing. 
  
Contractual changes result from changes in the terms and conditions, the scope of work, the requirements, schedule, and costs.  Normally, contractual changes are externally generated and out of the project scope.  For example, the sponsor might ask IBM to include maintenance of a system as part of a purchase agreement for the system with IBM.

For both technical and contractual changes, a formal change management procedure must be established.

Change Management and Project Baselines

A WWPMM domain addressing change management is available at the WWPMM Web site.

A graphic representation of both technical and contractual change.
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