Project Integration Management
Project Integration Management: Unifies and integrates all process specific to the following knowledge: scope, time, risk, cost, quality, HR, procurement, and communication
Content of Project Integration Management
1. Develop project charter: working with stakeholders to create the document that formally authorizes a project
Description
Inputs
A. Project statement of work: narrative description of products and services to be delivered by the project
B. Business case: document detailing the reasons for the project and the benefits that the execution of the project will result in.
C. Contract: a legal document signed between a client and the project contractor
D. Enterprise environmental factors: includes government laws and regulations, market conditions, organization infrasturcture
E. Organizational process assets: organizational standards, processes, policies, templates, lessons learned database etc.
Output - Project charter:
A. Purpose of the project; justification
B. Measurable project objectives
C. Success criteria
D. High level project description
E. High level requirement
F. High level risks
G. Summary milestone schedule
H. Summary budget
I. Assigned project manager, responsibility and authority level
J. Name and authority of the project sponsor
K. Other people authorising the project charter
Expert judgement:
A. Subject matter experts
B. Consultants
C. Stakeholders
D. Professional, Technical and Industry associations
E. Lessons learned from previous projects
2. Develop project management plan: coordinating all planning efforts to create a consistent, coherent document
Description
Project management plan: a document that spells out how the project will be planned, executed, controlled and closed. It covers all the knowledge areas such as scope, schedule, risks, quality etc. This document is used to coordinate all project planning documents and help guide a project's execution and control.
Inputs
A. Project charter
B. Outputs from all the planning processes
C. Enterprise environmental factors: includes government laws and regulations, market conditions, organization infrasturcture
D. Organizational process assets: organizational standards, processes, policies, templates, lessons learned database etc.
Outputs - Project management plan
A. Introduction or overview of the project
B. Description of how the project is organised
C. Life cycle selected for the project and the processes that will be applied to the each phase of the project.
D. Management and technical processes used in the proejct - this covers how scope, time, risk, cost, quality, HR, procurement, and communication will be managed.
E. The project environment, dependencies, assumptions and responsibilities of all parties involved.
F. Project schedule and budget information
G. Templates for various procedures and reports
Expert judgement:
A. Subject matter experts
B. Consultants
C. Stakeholders
D. Professional, Technical and Industry associations
E. Lessons learned from previous projects
3. Direct and manage project execution: carrying out the project management plan by performing the activities included in it
Description
Direct and manage project execution: the process of performing all the work that needs to be done to manage and execute the project in a manner that all project objectives are met.
Inputs
A. Project management plan
B. Change requests
C. Enterprise environmental factors: includes government laws and regulations, market conditions, organization infrasturcture
D. Organizational process assets: organizational standards, processes, policies, templates, lessons learned database etc.
Output
A. Work products and deliverables
B. Work performance information
a. Deliveralbe status
b. Schedule progress
c. costs incurred
C. Change requrest
a. corrective actions
b. preventive actions
c. defect repair
d. updates
D. Project document updates
a. Requirements documents
b. project logs
c. risk register
d. stakeholder register
E. Project plan updates
a. Requirements management plan
b. Schedule management plan
c. Cost management plan
d. Quality management plan
e. Human resource plan
f. Communications management plan
g. Risk management plan
h. Procurement management plan
i. Project baselines.
Expert judgement:
A. Subject matter experts
B. Consultants
C. Stakeholders
D. Professional, Technical and Industry associations
E. Lessons learned from previous projects
Project management information systems: includes they systems and tools made available to the project manager for managing and execution the project
4. Monitor and control project work: overseeing project work to meet the performance objectives of the project
Descripton
Inputs:
A. Project management plan
B. Performance reports
a. Current status
b. Significant accomplishments for the period
c. Forecasts
d. Issues
e. Risks
C. Enterprise environmental factors: includes government laws and regulations, market conditions, organization infrasturcture
D. Organizational process assets: organizational standards, processes, policies, templates, lessons learned database etc.
Outputs:
A. Change requests
a. Corrective actions
b. Preventive actions
c. Defect repair
d. Update
B. Project management plan updates
C. Project document updates
Expert judgement:
A. Subject matter experts
B. Consultants
C. Stakeholders
D. Professional, Technical and Industry associations
E. Lessons learned from previous projects
5. Perform integrated change control: coordinating changes that affect the project's deliverables and organizational process assets
Description
Inputs
A. Project management plan
B. Project document updates
C. Change requests
D. Enterprise environmental factors: includes government laws and regulations, market conditions, organization infrasturcture
E. Organizational process assets: organizational standards, processes, policies, templates, lessons learned database etc.
Outputs
A. Change request status updates
B. Project management plan updates
C. Project document updates
Expert judgement:
A. Subject matter experts
B. Consultants
C. Stakeholders
D. Professional, Technical and Industry associations
E. Lessons learned from previous projects
Change control meeting
Change control board (CCB): a formal group of people responsible for approving or rejecting changes on a project
Meeting type:
1. Occasionally
2. Time-sensitive: "48-hour policy" project team members have 48 hours to inform senior management and request the approval from them.
6. Close project or phase: finalizing all project activities to formally close the project or phase
Comments
Post a Comment