This chapter covers key concepts related to Project Integration Management.
The knowledge area of Project Integration Management consists of the following seven processes -
Project Integration Processes
Process
Project Phase
Key Deliverables
Develop Project Charter
Initiating
Project Charter
Develop Preliminary Project Scope Statement
Initiating
Preliminary Project Scope Statement
Develop Project Management Plan
Planning
Project Management Plan
Direct and Manage Project Execution
Execution
Deliverables
Manage and Control Project Work
Control
Requested Changes
Integrated Change Control
Control
Approved Change Requests
Close Project
Closure
Final product
A project charter
Formally authorizes the project.
Gives the objectives and business case
Identifies the Project Manager.
Generic enough not to change often.
Written by a Manager higher in authority than Project Manager.
Includes name, description, deliverables
A project does not start unless it has a Project charter.
During project execution the project team focuses on completing the tasks assigned. The Senior Management
protects the project from changes and loss of resources.
The Project Manager integrates all the pieces into the project as a whole.
The Inputs, Tools and Techniques, and Outputs of the Project Plan Development process are given in the
table below.
Project Plan Development
Inputs
Tools & Techniques
Outputs
Other Planning outputs
Project Planning Methodology
Project Plan
Historical Information
Stake holder skills and Knowledge
Organizational Policy
Project Management Information System (PMIS)
Constraints
Earned Value Management (EVM)
Assumptions
At the end of each phase of a project, a lessons learned document must be prepared. The lessons learned document defines what was done right, wrong etc. It is required to be completed in order for the project to be completed.
Project Management Information System (PMIS) is a system that keeps track of status of all the project tasks.
It is used to track the status of the project. The exam does not focus on any specific system (for example Microsoft Project ).
Project Plan is developed by Project Manager with inputs from the team, stake holders and management.
Project Plan development is iterative. A project plan is bought into, approved, realistic and formal.
A Project Plan includes -
Project Charter
Budget
Schedule
Resources
Scope Statement
WBS
Responsibility charts/assignments
Management Plans
Project baseline refers to the original version of the project plan.
Progressive Elaboration involves the process of taking a project from concept to
detailed design.
Kick-off meeting happens after the planning phase and before the project execution.
It is typically used to communicate responsibilities of key stake holders.
Change Control Board is formed to review change requests. It is used to approve or reject
change requests.
After the project scope has been baselined, each requested change must go through a change control review process.
Project Manager needs to be proactive in looking for deviations from project plan and then take
timely corrective action. After that the Project Manager needs to evaluate the effectiveness of corrective action,
and measure performance of corrective action, and then determine the need for further corrective action.
When a change request is received, the following steps must be taken (in this order) -
Evaluate (assess) the impact of change to the project
Create alternatives including cutting other tasks, crashing, fast-tracking etc.