Friday, March 12, 2010    
   You are here : PM Topics  >  Integration Mgmt
Register   Login   

"If project content is allowed to change freely the rate of change will exceed the rate of progress."

    - Anonymous

 
Project Integration Management

There is a macro and a micro aspect to project integration management. The macro level considers how the project fits with the organization, the community, and the constantly changing environment. The micro level considers how the project constraints are balanced, project change management, configuration management, and keeping the plans updated and communications current.

 

Configuration Management helps us to manage the product plan, including scope and features, as progressive elaboration occurs. The Configuration Management Plan, part of the Integrated Project Plan, provides version control of the product of the project.  It includes an Integrated Change Control process which facilitates the progressive elaboration process by maintaining snapshots of the picture, or level of elaboration, at any given time for the product of the project.

 

Some of the principles of Integration Management include the concept that the project manager should let the project stakedholders know what the process for handling changes should be in advance of the project work shifting into high gear. Changes should be decided upon and integrated into the project plans.

 

The project manager must be strong to filter out unwanted changes, patient in educating stakeholders on the implications of their desired changes, brutal in holding off changes that will distract from the priorities, and open in allowing process and product improvement ideas in when they enhance those priorities.

 
Configuration Management

Documentation for clarity and change. (Read now.)

 
What are Subsidiary Change Control Processes?

They are all of the control processes used to manage other knowledge areas (beyond the Integration Mgmt) such as scope change control, schedule change control, cost change control, risk change control, etc.

 
 

"People resist change only when they are not an active part of it."

-  Anonymous

 
CCB

Change Control Boards are a committee, often made up of the most important project sponsors or other stakeholders, that makes decisions on project change requests. The decisions made by the CCB generally are final and binding.

 

The formation of a CCB often reduces the pressure the project manager faces by helping to keep the responsibility of the important project decisions with the project sponsor role.

 
Copyright 2009 by Successful Projects