SlideShare une entreprise Scribd logo
1  sur  15
Télécharger pour lire hors ligne
PM Notebook
Summarizing Project Management Concepts for the PMP
Exam
Mohammad Elsheimy Road to PMP
PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | KEY TERMS
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
1
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS
BASED ON DATA/INFORMATION GATHERED FROM VARIOUS
RELIABLE SOURCES. NONE OF THIS DATA/INFORMATION IS A
PROPERTY OF THE AUTHOR. NONE IS INTENDED TO MAKE A
PROFIT IN ANY WAY. THIS IS FOR PERSONAL USE ONLY.
PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | KEY TERMS
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
2
No great man ever complains of want of opportunity.
Ralph Waldo Emerson
PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | KEY TERMS
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
3
Table of Contents
Chapter 4 – Integration Management................................................................................................................ 4
Key Terms ............................................................................................................................................................... 4
Integration Types .............................................................................................................................................. 4
Changes, Defects, and Corrections............................................................................................................. 4
Processes................................................................................................................................................................ 4
1 – Develop Project Charter (Initiating) ....................................................................................................... 4
2 – Develop Project Management Plan (Planning)................................................................................... 5
3 – Direct and Manage Project Work (Executing)..................................................................................... 6
4 – Manage Project Knowledge (Executing).............................................................................................. 7
5 – Monitoring and Controlling Project Work (Monitoring & Controlling) .............................................. 8
6 – Perform Integrated Change Control (Monitoring & Controlling) ..................................................... 8
7 – Closing Project or Phase (Closing) .......................................................................................................... 9
Statement of Work (SOW) / Scope of Services ............................................................................................ 11
Product Analysis.................................................................................................................................................. 12
Knowledge Types ............................................................................................................................................... 12
Knowledge Management Techniques.......................................................................................................... 13
Configuration Management ........................................................................................................................... 13
Program/Project Evaluation and Review Technique (PERT)...................................................................... 14
PERT Planning .................................................................................................................................................. 14
Additional Terms ................................................................................................................................................. 14
PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | KEY TERMS
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
4
Key Terms
Integration – Keeping everybody working towards the same goals and dealing with changes.
Integration Types
Process-Level Integration – pre-defined actions will bring pre-defined results and that process
areas are integrated, meaning that what you do in one knowledge area affects other knowledge
areas.
Cognitive-Level Integration – Experience and maturity, leadership, and mastery of PM.
Context-Level Integration – the idea that the ways projects are managed have changed or
evolved as times have changed, with technology being a prime example.
Changes, Defects, and Corrections
Defect – Something faulty or erroneous in an item, procedure, component, or deliverable. In other
words, any deliverable that is not meeting its requirements.
Defect Repair (Rework) – When a component of the project does not meet specifications.
Corrective Action – Any action taken to bring expected future project performance in line with
the project management plan.
Preventive Action – Steps that you take to avoid anticipated or potential problems or deviations.
Processes
1 – Develop Project Charter (Initiating)
 A statement of objectives and milestones of a project.
 Usually it is the responsibility of project initiator, sponsor, or even portfolio steering committee.
Sometimes, the project manager creates it, and the sponsor approves it.
 Must be developed for all projects and for each phase.
 Must be broad enough so it does not need to change as the project progresses.
 Any change to the project charter should call into question whether project should continue.
 If the project is in progress and no project charter has been developed, you must continue
on the project without developing the charter as the project is already existed.
 It sets out –
 High-level goals and requirements
 Main stakeholders and sponsors
PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
5
 Level of authorization of PM
 Links the project to the strategic plan and ongoing work of the organization.
 Summary milestone schedule
 Overall project risk
 Responsibilities
 Measurable project objectives
 Success criteria
 Preapproved financial resources
 Pre-assigned resources
 Approval requirements
 High-level assumptions and constraints
 Exit criteria
Inputs
1. Contracts/Agreements – What you agreed to do like SLAs and vendor contracts.
2. Business Documents
 Business Case
 Benefits Management Plan
3. Statement of Work (SOW)
4. Enterprise Environmental Factors (EEFs)
5. Organizational Process Assets (OPAs)
 Monitoring and Reporting Methods
Tools
1. Expert Judgment
2. Data Gathering Techniques
 Facilitation Techniques
3. Interpersonal/Team/Soft Skills
4. Meetings
Outputs
1. Project Charter
2. Assumptions Log – List of constraints and things that you believe to be true or false.
Assumptions that prove wrong can become risks for the project.
 All identified assumptions must be recorded, analyzed, and tested.
 High-level strategic and operational assumptions are documents in business case.
2 – Develop Project Management Plan (Planning)
 A formal approved document used to manage project execution.
 It defines how the project is executed, monitored and controlled. It also defines baselines.
 Broken into subsidiary plans each dedicated to a knowledge area.
 After baseline, change control is required to update the plan.
 Participants in creating the management plan are project manager, team members,
customers, and management.
 Requires formal approval from sponsor or key stakeholders.
PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
6
 Contents of project management plan is primarily influenced by the application area and
complexity of project.
 Kick-off meeting –
o Happens after the plan is approved, and at the beginning of each phase.
o Establishes working relationships and standard format for global communication.
o Reviewing project plans.
o Establishing individual and group responsibilities and accountabilities.
Inputs
1. Project Charter
2. Outputs of the other planning processes
3. Enterprise Environmental Factors (EEFs)
4. Organizational Process Assets (OPAs)
Tools
1. Expert Judgment
2. Data Gathering Techniques
3. Interpersonal/Team/Soft Skills
4. Meetings
Outputs
1. Project Management Plan
 Project management processes that will be used on the project and the details degree.
 Knowledge area management plans – Scope, Schedule, Cost, Quality, Resources,
Communications, Risk, Procurements, and Stakeholder.
 Performance Measurement Baselines (PMB) – integrated scope-cost-schedule plan for
the project to measure and manage performance.
 Change Management Plan
 Configuration Management Plan
 Benefits Management Plan
 Project Lifecycle (Phases)
3 – Direct and Manage Project Work (Executing)
 Provide overall management of the project work.
 Implement approved changes.
 Lead and perform activities in the project management plan.
 Perform activities to accomplish project objectives.
Inputs
1. Approved Change Requests
2. Project Documents
3. Project Management Plan
4. Enterprise Environmental Factors (EEFs)
5. Organizational Process Assets (OPAs)
PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
7
Tools
1. Expert Judgment
2. Project Management Information System (PMIS)
3. Meetings
Outputs
1. Work Performance Data – Created by measuring how well the processes from each
knowledge area are being performed.
2. Deliverables – Products, services, documents, plans, schedules, budget, blueprints, and
everything gets made along the way.
3. Issue Log – a documentation that contains a list of ongoing and closed issues of the project.
It lists issue type, who and when the issue raised, priority, status, and so on.
4. Implemented Change Requests
5. Project Document Updates – Used to manage information which is not part of the plan.
Prepared by PM for his own needs.
6. Project Management Plan Updates
7. OPA Updates
4 – Manage Project Knowledge (Executing)
A way of using existing knowledge within the organization to achieve the project’s objectives and
then using new knowledge gained on the project to contribute to the organizations body of
knowledge.
Inputs
1. Project Management Plan
2. Project Documents
3. Deliverables
4. EEFs
5. OPAs
Tools
1. Expert Judgment
2. Knowledge Management Techniques
3. Information Management
4. Interpersonal/Team/Soft Skills
Outputs
1. Lessons Learned Register
2. Project Management Plan Updates
3. OPA Updates
PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
8
5 – Monitoring and Controlling Project Work (Monitoring & Controlling)
 Iterative activity
 Happens throughout the project
 Comparing actual project performance against project management plan.
Inputs
1. Project Management Plan
2. Project Documents
3. Work Performance Data
4. Agreements
5. Enterprise Environmental Factors (EEFs)
6. Organizational Process Assets (OPAs)
Tools
1. Expert Judgment
2. Data Analysis Techniques
3. Meetings
4. Decision Making
Outputs
1. Work Performance Information
2. Forecasts
3. Recommended Corrective Actions
4. Product Document Update
5. Project Management Plan Updates
6. Change Requests
6 – Perform Integrated Change Control (Monitoring & Controlling)
 How changes are managed and approved.
 Happens throughout the project after a baseline established.
 Responsibility of project manager.
 Verbal changes happen, but should be documented.
 Any change to project documents must be documented first in the change log and through
configuration control.
 When creating the outputs of processes in initiating and planning changes can be made
without a formal change request, however, once something lie the charter has been issued,
any requested changes would need to go through integrated change control.
 A change in one of the constraints should be evaluated for impacts on all of the other
constraints.
 You should consider terminating projects with excessive changes and starting new ones with
a more complete set of requirements.
 It is necessary to analyze and approve change requests promptly because slow decision
time may negatively affect time, cost or the feasibility of change.
PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
9
Steps
Whenever there is a change, the following steps must be followed –
1. Logging the change request in change log.
2. Analyzing the impact of proposed change on all project constraints.
3. Sending all data to CCB for approval/postponing/rejection.
4. If approved, where there are variances, plans and baselines must be updated with new
work, and new work should be implemented by direct and manage work.
5. If postponed or rejected, the results must be communicated to requestor/stakeholder.
6. Logging the request status in change log.
Inputs
1. Change Requests
2. Work Performance Information
3. Project Management Plan
4. Enterprise Environmental Factors (EEFs)
5. Organizational Process Assets (OPAs)
Tools
1. Expert Judgment
2. Change Control Board (CCB) Meetings
3. Change Control Tools – Software, forms, etc.
4. Decision Making Techniques
5. Data Analysis Techniques
Outputs
1. Change Request Status Updates
2. Product Document Update
3. Project Management Plan Updates
4. Change Log
7 – Closing Project or Phase (Closing)
Steps
1. Validate Scope – Confirm all requirements have been met. Happens after Control Quality.
2. Get Formal Acceptance
3. Create Project Closure Documents
 Write Lessons Learned
4. Handover Deliverables
5. Close Contract
6. Release project team.
PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
10
Stages
1. Work Closure
 Finalizing formal acceptance of work.
 Updating records to reflect results.
 Sign-off on work completed.
2. Contract Closure
 Finalizing open claims.
 Updating records to reflect results.
 Sign-off on work completed.
 Certificate of contract closure.
3. Administrative Closure – An internal process. The confirmation that all of your documents
and deliverables are correct.
 Closing project accounts
 Analyze project success or failure.
 Archive project information.
 Dealing with excess project material.
 Starting any warranty/guarantee work.
 Transferring product, service, or result to next phase.
 Reallocating project facilities, equipment, and other resources.
 Creating final project reports.
 Releasing project team.
 Measuring customer satisfaction.
Characteristics
 Closing Activities –
o Finalize project or phase records
o Audit project for success or failure
o Transfer project’s results to next phase, production, or operations
o Measure stakeholder satisfaction
 Early project closure implies full closure.
 All stakeholders must be involved in the creation of lessons learned.
 Success of the project is measured primarily by customer satisfaction.
 A project/phase is considered to be closed if the archives are completed.
 Risk is the lowest at this stage.
 Should not be delayed until project completion because useful information may be lost.
 At the end of each phases you should review your business case, project charter, and
benefits management plan.
Termination
 Sometimes there will be a termination manager who will carry out the closing procedures
except personnel performance evaluations (which is a core function of PM or whoever
supervising the work.)
 Causes of termination -
o Behavior-oriented reasons – account for the top causes of termination because it is
much more difficult to manage people than things.
PM NOTEBOOK
CHAPTER 4 – INTEGRATION MANAGEMENT | STATEMENT OF WORK (SOW)
/ SCOPE OF SERVICES
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
11
o Excessive Changes – consider terminating projects with excessive changes and
starting new ones with a more complete set of requirements.
o Starvation – When the project no longer receives the resources needed to continue.
Inputs
1. Project Charter
2. Project Management Plan
3. Accepted Deliveries
4. Acceptance Criteria
5. Project Documents
 Procurement Documentation
6. Business Documents
 Business Case
Tools
1. Expert Judgment
2. Meetings –
 To confirm that deliverables have been accepted.
To validate that the exit criteria have been met.
 To formalize completion of contracts.
 To evaluate the satisfaction of the stakeholders.
 To gather lessons learned.
 To transfer knowledge.
 To celebrate success.
3. Data Analysis Techniques
Outputs
1. Final Product, Service, or Result
2. Final Report – should include recommendations for changing current practices.
3. Project Document Updates
4. Organizational Process Assets (OPAs)
 Lesson Learned
 Historical Information
Statement of Work (SOW) / Scope of Services
Created by customer or sponsor. No formal signs required. Defines the following –
 Purpose
 Project-specific activities and deliverables.
 Project durations and milestones.
 Resource hours.
 Billing rates.
 Service fees.
 Payment schedule and terms.
PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PRODUCT ANALYSIS
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
12
 Listing of representatives.
Product Analysis
Product Breakdown
Requirements Analysis
System Analysis
System Engineering
Value Analysis (VA) –
 Concerned with existing products.
 Involves a current product being analyzed and evaluated by a team, to reduce costs,
improve product function or both.
 Value Analysis exercises use a plan which step-by-step, methodically evaluates the
product in a range of areas. These include costs, function, alternative components and
design aspects such as ease of manufacture and assembly.
 A significant part of VA is a technique called Functional Analysis, where the product is
broken down and reviewed as a number of assemblies. Here, the function is identified and
defined for each product assembly. Costs are also assigned to each one.
Value Engineering (VE) –
 Concerned with new products.
 It is applied during product development.
 The focus is on reducing costs, improving function or both, by way of teamwork-based
product evaluation and analysis.
 This takes place before any capital is invested in tooling, plant or equipment.
Knowledge Types
Formal/Explicit Knowledge – knowledge that can be quickly and easily expressed through
conversations, documentation, figures, and numbers.
 Codified explicit knowledge lacks context and is open to different interpretations.
Tacit Knowledge – knowledge that is more difficult to express or transfer to another person
because it is personal beliefs, values, knowledge gain from experience, and know-how when
doing a task.
 Tacit knowledge cannot be codified, however, creating an atmosphere of trust can
motivate people to share their tacit knowledge.
PM NOTEBOOK
CHAPTER 4 – INTEGRATION MANAGEMENT | KNOWLEDGE
MANAGEMENT TECHNIQUES
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
13
Knowledge Management Techniques
Communities of Practice and Special Interest Groups
Creativity and Ideas Management Techniques / Group Creativity Techniques – Like brainstorming,
affinity diagrams, mind mapping, etc.
Discussing Forums and Focus Groups
Knowledge Fairs and Cafes – Participants move between tents to learn fast lessons.
Meetings
Networking with Colleagues
Reverse Shadowing – The expert follows you; the expert offers coaching.
Storytelling – To explain tacit knowledge.
Training Events
Work Shadowing – To follow, or shadow, an expert.
 Passive – Following and observing without any engagement.
 Active – Following, observing and engaging.
Configuration Management
The process for applying technical and administrative direction and surveillance of the project
implementation. Involves a thorough change control system to ensure the project produces the
desired results.
Configuration Identification – The process of identifying attributes of products and labeling them
with unique identifiers.
Configuration Status Accounting (CSA) – Recording and reporting of information needed to
manage configuration items effectively, including a record of the approved configuration
documentation and identification numbers.
Configuration Control (Verification and Auditing) – Verification that the configuration identification
for a configuration item is accurate, complete, and will meet specified program needs.
PM NOTEBOOK
CHAPTER 4 – INTEGRATION MANAGEMENT | PROGRAM/PROJECT
EVALUATION AND REVIEW TECHNIQUE (PERT)
DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION
GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY
OF THE AUTHOR.
14
Program/Project Evaluation and Review Technique (PERT)
Program Evaluation and Review Technique (PERT) is a technique adopted by organizations to
analyze and represent the activity in a project, and to illustrate the flow of events in a project. PERT
serves as a management tool to analyze, define and integrate events. PERT also illustrates the
activities and interdependencies in a project. The main goal of PERT is to reduce the cost and time
needed to complete a project.
PERT Planning
PERT planning usually involves the following steps –
1. Identifying Tasks and Milestones – Every project involves a series of required tasks. These tasks
are listed in a table allowing additional information on sequence and timing to be added
later.
2. Placing the Tasks in a Proper Sequence – The tasks are analyzed and placed in a sequence
to get the desired results.
3. Network Diagramming – A network diagram is drawn using the activity sequence data
showing the sequence of serial and parallel activities.
4. Time Estimating – This is the time required to carry out each activity, in three parts –
 Optimistic timing – The shortest time to complete an activity
 Most likely timing – The completion time having the highest probability
 Pessimistic timing – The longest time to complete an activity
5. Critical Path Estimating – This determines the total time required to complete a project.
Additional Terms
Performance Measurement Baselines (PMB) – A snapshot of your project’s scope, schedule and
cost.
 Scope Baseline
 Schedule Baseline
 Cost Baseline
Process Capability Baseline (PCB) – specifies what results to expect when a process is followed.
Using PCB, a project manager can predict, at the gross level, effort required at various stages,
defect densities, overall quality, and productivity.
Tailoring Processes – determining which processes are appropriate, and the appropriate degree
of rigor for each process. You need to measure tailoring needs for each project by considering
EEFs.

Contenu connexe

Tendances

Cassidy.jim
Cassidy.jimCassidy.jim
Cassidy.jimNASAPMC
 
Modern management techniques
Modern management techniquesModern management techniques
Modern management techniquesdrravimr
 
Law.richard
Law.richardLaw.richard
Law.richardNASAPMC
 
Terry.conroy
Terry.conroyTerry.conroy
Terry.conroyNASAPMC
 
John.rigoli
John.rigoliJohn.rigoli
John.rigoliNASAPMC
 
Project Management Notes 1
Project Management Notes 1Project Management Notes 1
Project Management Notes 1Golam Bitonsir
 
Nine Best Practices
Nine Best PracticesNine Best Practices
Nine Best PracticesGlen Alleman
 
David,florian dlr kn-david_implementing a pmo_nasa pm challenge_20120223
David,florian dlr kn-david_implementing a pmo_nasa pm challenge_20120223David,florian dlr kn-david_implementing a pmo_nasa pm challenge_20120223
David,florian dlr kn-david_implementing a pmo_nasa pm challenge_20120223NASAPMC
 
Brownfields agile draft v11
Brownfields agile draft v11Brownfields agile draft v11
Brownfields agile draft v11tony1234
 
Heliotropic Abundance
Heliotropic AbundanceHeliotropic Abundance
Heliotropic AbundanceGlen Alleman
 
SPM Resource Management
SPM Resource ManagementSPM Resource Management
SPM Resource ManagementSaqib Raza
 
Narrated Version Dallas MPUG
Narrated Version Dallas MPUGNarrated Version Dallas MPUG
Narrated Version Dallas MPUGGlen Alleman
 
Sally.godfrey
Sally.godfrey Sally.godfrey
Sally.godfrey NASAPMC
 
John marinaro pm_process
John marinaro pm_processJohn marinaro pm_process
John marinaro pm_processNASAPMC
 
Integrated Master Plan and Integrated Master Schedule
Integrated Master Plan and Integrated Master ScheduleIntegrated Master Plan and Integrated Master Schedule
Integrated Master Plan and Integrated Master ScheduleGlen Alleman
 
NAVAIR Integrated Master Schedule Guide guide
NAVAIR Integrated Master Schedule Guide guideNAVAIR Integrated Master Schedule Guide guide
NAVAIR Integrated Master Schedule Guide guideGlen Alleman
 

Tendances (20)

Cassidy.jim
Cassidy.jimCassidy.jim
Cassidy.jim
 
Modern management techniques
Modern management techniquesModern management techniques
Modern management techniques
 
Law.richard
Law.richardLaw.richard
Law.richard
 
Terry.conroy
Terry.conroyTerry.conroy
Terry.conroy
 
John.rigoli
John.rigoliJohn.rigoli
John.rigoli
 
Project Management Notes 1
Project Management Notes 1Project Management Notes 1
Project Management Notes 1
 
Nine Best Practices
Nine Best PracticesNine Best Practices
Nine Best Practices
 
David,florian dlr kn-david_implementing a pmo_nasa pm challenge_20120223
David,florian dlr kn-david_implementing a pmo_nasa pm challenge_20120223David,florian dlr kn-david_implementing a pmo_nasa pm challenge_20120223
David,florian dlr kn-david_implementing a pmo_nasa pm challenge_20120223
 
Brownfields agile draft v11
Brownfields agile draft v11Brownfields agile draft v11
Brownfields agile draft v11
 
Heliotropic Abundance
Heliotropic AbundanceHeliotropic Abundance
Heliotropic Abundance
 
SPM Resource Management
SPM Resource ManagementSPM Resource Management
SPM Resource Management
 
Forensic schedule analysis acesss
Forensic schedule analysis acesssForensic schedule analysis acesss
Forensic schedule analysis acesss
 
Narrated Version Dallas MPUG
Narrated Version Dallas MPUGNarrated Version Dallas MPUG
Narrated Version Dallas MPUG
 
Sally.godfrey
Sally.godfrey Sally.godfrey
Sally.godfrey
 
John marinaro pm_process
John marinaro pm_processJohn marinaro pm_process
John marinaro pm_process
 
Integrated Master Plan and Integrated Master Schedule
Integrated Master Plan and Integrated Master ScheduleIntegrated Master Plan and Integrated Master Schedule
Integrated Master Plan and Integrated Master Schedule
 
Stages of Project Development
Stages of Project DevelopmentStages of Project Development
Stages of Project Development
 
Rita's Process Chart
Rita's Process ChartRita's Process Chart
Rita's Process Chart
 
Plan Implementation
Plan ImplementationPlan Implementation
Plan Implementation
 
NAVAIR Integrated Master Schedule Guide guide
NAVAIR Integrated Master Schedule Guide guideNAVAIR Integrated Master Schedule Guide guide
NAVAIR Integrated Master Schedule Guide guide
 

Similaire à PM Notebook - Chapter 4: Integration Management

The funkiest PRINCE2 Processes revision guide on the internet
The funkiest PRINCE2 Processes revision guide on the internetThe funkiest PRINCE2 Processes revision guide on the internet
The funkiest PRINCE2 Processes revision guide on the internetKnowledge Train
 
04.integration management updated
04.integration management updated04.integration management updated
04.integration management updatedShraddha PMP
 
PM Notebook - Chapter 1: Introduction
PM Notebook - Chapter 1: IntroductionPM Notebook - Chapter 1: Introduction
PM Notebook - Chapter 1: IntroductionMohammad Elsheimy
 
MODULE II - M.ARCH.pptx
MODULE II - M.ARCH.pptxMODULE II - M.ARCH.pptx
MODULE II - M.ARCH.pptxMdAliMujawar1
 
The Art Of Project Management
The Art Of Project ManagementThe Art Of Project Management
The Art Of Project Managementhatemk
 
Topic 6 - Project Integration Management.pdf
Topic 6 - Project Integration Management.pdfTopic 6 - Project Integration Management.pdf
Topic 6 - Project Integration Management.pdfHuyNguyen657394
 
Project Management Methodology_rFmAt0BhU0dwihA.pdf
Project Management Methodology_rFmAt0BhU0dwihA.pdfProject Management Methodology_rFmAt0BhU0dwihA.pdf
Project Management Methodology_rFmAt0BhU0dwihA.pdfFaisalAziz831398
 
13.0 Project Stakeholder Management Overview
13.0 Project Stakeholder Management Overview13.0 Project Stakeholder Management Overview
13.0 Project Stakeholder Management OverviewDavidMcLachlan1
 
Graded application of project management req
Graded application of project management reqGraded application of project management req
Graded application of project management reqGlen Alleman
 
Online PMP Prep Material for PMP Exam - Project management process groups
Online PMP Prep Material for PMP Exam - Project management process groupsOnline PMP Prep Material for PMP Exam - Project management process groups
Online PMP Prep Material for PMP Exam - Project management process groupsGlobalSkillup
 
04 projectintegrationmanagement
04 projectintegrationmanagement04 projectintegrationmanagement
04 projectintegrationmanagementDhamo daran
 
Project and project management
Project and project managementProject and project management
Project and project managementwodato
 

Similaire à PM Notebook - Chapter 4: Integration Management (20)

Pmp study-notes
Pmp study-notesPmp study-notes
Pmp study-notes
 
1. project integration management
1. project integration management1. project integration management
1. project integration management
 
The funkiest PRINCE2 Processes revision guide on the internet
The funkiest PRINCE2 Processes revision guide on the internetThe funkiest PRINCE2 Processes revision guide on the internet
The funkiest PRINCE2 Processes revision guide on the internet
 
04.integration management updated
04.integration management updated04.integration management updated
04.integration management updated
 
#Pmp in a3 edition_1
#Pmp in a3 edition_1#Pmp in a3 edition_1
#Pmp in a3 edition_1
 
PM Notebook - Chapter 1: Introduction
PM Notebook - Chapter 1: IntroductionPM Notebook - Chapter 1: Introduction
PM Notebook - Chapter 1: Introduction
 
MODULE II - M.ARCH.pptx
MODULE II - M.ARCH.pptxMODULE II - M.ARCH.pptx
MODULE II - M.ARCH.pptx
 
4 integration
4 integration4 integration
4 integration
 
The Art Of Project Management
The Art Of Project ManagementThe Art Of Project Management
The Art Of Project Management
 
Topic 6 - Project Integration Management.pdf
Topic 6 - Project Integration Management.pdfTopic 6 - Project Integration Management.pdf
Topic 6 - Project Integration Management.pdf
 
ATCO-BaasKaar Roadmap to SAP Quality Award 2014
ATCO-BaasKaar Roadmap to SAP Quality Award 2014ATCO-BaasKaar Roadmap to SAP Quality Award 2014
ATCO-BaasKaar Roadmap to SAP Quality Award 2014
 
Project Management Methodology_rFmAt0BhU0dwihA.pdf
Project Management Methodology_rFmAt0BhU0dwihA.pdfProject Management Methodology_rFmAt0BhU0dwihA.pdf
Project Management Methodology_rFmAt0BhU0dwihA.pdf
 
Entra lecture6 PM1.pdf
Entra lecture6 PM1.pdfEntra lecture6 PM1.pdf
Entra lecture6 PM1.pdf
 
Pm training 1 18
Pm training 1 18Pm training 1 18
Pm training 1 18
 
13.0 Project Stakeholder Management Overview
13.0 Project Stakeholder Management Overview13.0 Project Stakeholder Management Overview
13.0 Project Stakeholder Management Overview
 
Graded application of project management req
Graded application of project management reqGraded application of project management req
Graded application of project management req
 
Online PMP Prep Material for PMP Exam - Project management process groups
Online PMP Prep Material for PMP Exam - Project management process groupsOnline PMP Prep Material for PMP Exam - Project management process groups
Online PMP Prep Material for PMP Exam - Project management process groups
 
2_Project Scope Management
2_Project Scope Management2_Project Scope Management
2_Project Scope Management
 
04 projectintegrationmanagement
04 projectintegrationmanagement04 projectintegrationmanagement
04 projectintegrationmanagement
 
Project and project management
Project and project managementProject and project management
Project and project management
 

Plus de Mohammad Elsheimy

Mohammad Elsheimy - Solution Developer (CV)
Mohammad Elsheimy - Solution Developer (CV)Mohammad Elsheimy - Solution Developer (CV)
Mohammad Elsheimy - Solution Developer (CV)Mohammad Elsheimy
 
PM Notebook - Appendix H - Formula Sheet
PM Notebook - Appendix H - Formula SheetPM Notebook - Appendix H - Formula Sheet
PM Notebook - Appendix H - Formula SheetMohammad Elsheimy
 
PM Notebook - Appendix G - Interpersonal/Team/Soft Skills
PM Notebook - Appendix G - Interpersonal/Team/Soft SkillsPM Notebook - Appendix G - Interpersonal/Team/Soft Skills
PM Notebook - Appendix G - Interpersonal/Team/Soft SkillsMohammad Elsheimy
 
PM Notebook - Appendix F - Forecasting Methods
PM Notebook - Appendix F - Forecasting MethodsPM Notebook - Appendix F - Forecasting Methods
PM Notebook - Appendix F - Forecasting MethodsMohammad Elsheimy
 
PM Notebook - Appendix E - Estimating Techniques
PM Notebook - Appendix E - Estimating TechniquesPM Notebook - Appendix E - Estimating Techniques
PM Notebook - Appendix E - Estimating TechniquesMohammad Elsheimy
 
PM Notebook - Appendix D - Decision-Making Techniques
PM Notebook - Appendix D - Decision-Making TechniquesPM Notebook - Appendix D - Decision-Making Techniques
PM Notebook - Appendix D - Decision-Making TechniquesMohammad Elsheimy
 
PM Notebook - Appendix C - Data Representation Tools
PM Notebook - Appendix C - Data Representation ToolsPM Notebook - Appendix C - Data Representation Tools
PM Notebook - Appendix C - Data Representation ToolsMohammad Elsheimy
 
PM Notebook - Appendix B - Data Gathering Techniques
PM Notebook - Appendix B - Data Gathering TechniquesPM Notebook - Appendix B - Data Gathering Techniques
PM Notebook - Appendix B - Data Gathering TechniquesMohammad Elsheimy
 
PM Notebook - Chapter 14 - Professional and Social Responsibility
PM Notebook - Chapter 14 - Professional and Social ResponsibilityPM Notebook - Chapter 14 - Professional and Social Responsibility
PM Notebook - Chapter 14 - Professional and Social ResponsibilityMohammad Elsheimy
 
PM Notebook - Chapter 13 - Stakeholder Management
PM Notebook - Chapter 13 - Stakeholder ManagementPM Notebook - Chapter 13 - Stakeholder Management
PM Notebook - Chapter 13 - Stakeholder ManagementMohammad Elsheimy
 
PM Notebook - Chapter 12 - Procurement Management
PM Notebook - Chapter 12 - Procurement ManagementPM Notebook - Chapter 12 - Procurement Management
PM Notebook - Chapter 12 - Procurement ManagementMohammad Elsheimy
 
PM Notebook - Chapter 11: Risk Management
PM Notebook - Chapter 11: Risk ManagementPM Notebook - Chapter 11: Risk Management
PM Notebook - Chapter 11: Risk ManagementMohammad Elsheimy
 
PM Notebook - Chapter 2: Organizations
PM Notebook - Chapter 2: OrganizationsPM Notebook - Chapter 2: Organizations
PM Notebook - Chapter 2: OrganizationsMohammad Elsheimy
 
Microsoft Silverlight - An Introduction
Microsoft Silverlight - An IntroductionMicrosoft Silverlight - An Introduction
Microsoft Silverlight - An IntroductionMohammad Elsheimy
 
Marshaling with C# Pocket Reference
Marshaling with C# Pocket ReferenceMarshaling with C# Pocket Reference
Marshaling with C# Pocket ReferenceMohammad Elsheimy
 

Plus de Mohammad Elsheimy (17)

Mohammad Elsheimy - Solution Developer (CV)
Mohammad Elsheimy - Solution Developer (CV)Mohammad Elsheimy - Solution Developer (CV)
Mohammad Elsheimy - Solution Developer (CV)
 
PM Notebook
PM NotebookPM Notebook
PM Notebook
 
PM Notebook - Appendix H - Formula Sheet
PM Notebook - Appendix H - Formula SheetPM Notebook - Appendix H - Formula Sheet
PM Notebook - Appendix H - Formula Sheet
 
PM Notebook - Appendix G - Interpersonal/Team/Soft Skills
PM Notebook - Appendix G - Interpersonal/Team/Soft SkillsPM Notebook - Appendix G - Interpersonal/Team/Soft Skills
PM Notebook - Appendix G - Interpersonal/Team/Soft Skills
 
PM Notebook - Appendix F - Forecasting Methods
PM Notebook - Appendix F - Forecasting MethodsPM Notebook - Appendix F - Forecasting Methods
PM Notebook - Appendix F - Forecasting Methods
 
PM Notebook - Appendix E - Estimating Techniques
PM Notebook - Appendix E - Estimating TechniquesPM Notebook - Appendix E - Estimating Techniques
PM Notebook - Appendix E - Estimating Techniques
 
PM Notebook - Appendix D - Decision-Making Techniques
PM Notebook - Appendix D - Decision-Making TechniquesPM Notebook - Appendix D - Decision-Making Techniques
PM Notebook - Appendix D - Decision-Making Techniques
 
PM Notebook - Appendix C - Data Representation Tools
PM Notebook - Appendix C - Data Representation ToolsPM Notebook - Appendix C - Data Representation Tools
PM Notebook - Appendix C - Data Representation Tools
 
PM Notebook - Appendix B - Data Gathering Techniques
PM Notebook - Appendix B - Data Gathering TechniquesPM Notebook - Appendix B - Data Gathering Techniques
PM Notebook - Appendix B - Data Gathering Techniques
 
PM Notebook - Chapter 14 - Professional and Social Responsibility
PM Notebook - Chapter 14 - Professional and Social ResponsibilityPM Notebook - Chapter 14 - Professional and Social Responsibility
PM Notebook - Chapter 14 - Professional and Social Responsibility
 
PM Notebook - Chapter 13 - Stakeholder Management
PM Notebook - Chapter 13 - Stakeholder ManagementPM Notebook - Chapter 13 - Stakeholder Management
PM Notebook - Chapter 13 - Stakeholder Management
 
PM Notebook - Chapter 12 - Procurement Management
PM Notebook - Chapter 12 - Procurement ManagementPM Notebook - Chapter 12 - Procurement Management
PM Notebook - Chapter 12 - Procurement Management
 
PM Notebook - Chapter 11: Risk Management
PM Notebook - Chapter 11: Risk ManagementPM Notebook - Chapter 11: Risk Management
PM Notebook - Chapter 11: Risk Management
 
PM Notebook - Chapter 2: Organizations
PM Notebook - Chapter 2: OrganizationsPM Notebook - Chapter 2: Organizations
PM Notebook - Chapter 2: Organizations
 
What's New in Silverlight 5
What's New in Silverlight 5What's New in Silverlight 5
What's New in Silverlight 5
 
Microsoft Silverlight - An Introduction
Microsoft Silverlight - An IntroductionMicrosoft Silverlight - An Introduction
Microsoft Silverlight - An Introduction
 
Marshaling with C# Pocket Reference
Marshaling with C# Pocket ReferenceMarshaling with C# Pocket Reference
Marshaling with C# Pocket Reference
 

Dernier

The Role of Fishbone Diagram in Analyzing Cause and Effect
The Role of Fishbone Diagram in Analyzing Cause and EffectThe Role of Fishbone Diagram in Analyzing Cause and Effect
The Role of Fishbone Diagram in Analyzing Cause and EffectCIToolkit
 
Performance Management Notes for MBA Students
Performance Management Notes for MBA StudentsPerformance Management Notes for MBA Students
Performance Management Notes for MBA StudentsManickam Gajapathy
 
Value Stream Map: A Visual Approach to Process Optimization
Value Stream Map: A Visual Approach to Process OptimizationValue Stream Map: A Visual Approach to Process Optimization
Value Stream Map: A Visual Approach to Process OptimizationCIToolkit
 
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...AgileNetwork
 
An Important Step Toward Process Improvement
An Important Step Toward Process ImprovementAn Important Step Toward Process Improvement
An Important Step Toward Process ImprovementCIToolkit
 
A3 Thinking: A Structured Approach to Problem Solving
A3 Thinking: A Structured Approach to Problem SolvingA3 Thinking: A Structured Approach to Problem Solving
A3 Thinking: A Structured Approach to Problem SolvingCIToolkit
 
Tackling Fake Agility w/ Johanna Rothman
Tackling Fake Agility w/ Johanna RothmanTackling Fake Agility w/ Johanna Rothman
Tackling Fake Agility w/ Johanna RothmanStefan Wolpers
 
Organizations in a Future with Generative AI
Organizations in a Future with Generative AIOrganizations in a Future with Generative AI
Organizations in a Future with Generative AIKye Andersson
 
Empowering Resilience & Strategic Growth: Insights for Emerging Leaders
Empowering Resilience & Strategic Growth: Insights for Emerging LeadersEmpowering Resilience & Strategic Growth: Insights for Emerging Leaders
Empowering Resilience & Strategic Growth: Insights for Emerging LeadersMahmoud Rabie
 
Growing a Thriving and Engaged Remote Team
Growing a Thriving and Engaged Remote TeamGrowing a Thriving and Engaged Remote Team
Growing a Thriving and Engaged Remote TeamJulie Cameron
 
Analyzing and Monitoring Processes through Time Value Mapping
Analyzing and Monitoring Processes through Time Value MappingAnalyzing and Monitoring Processes through Time Value Mapping
Analyzing and Monitoring Processes through Time Value MappingCIToolkit
 
Forget Fiverr : Fractional Employment the ins and outs
Forget Fiverr : Fractional Employment the ins and outsForget Fiverr : Fractional Employment the ins and outs
Forget Fiverr : Fractional Employment the ins and outsStephan Koning
 
From Command Line to Reporting Line: The Diary of a First-Time EM
From Command Line to Reporting Line: The Diary of a First-Time EMFrom Command Line to Reporting Line: The Diary of a First-Time EM
From Command Line to Reporting Line: The Diary of a First-Time EMGloria Chow
 
What is 5S principles of trainers for training institutions.pdf
What is 5S principles of trainers for training institutions.pdfWhat is 5S principles of trainers for training institutions.pdf
What is 5S principles of trainers for training institutions.pdfBALASUNDARESAN M
 
Roadway to GDSC- Session 1 Powerpoint Presentation
Roadway to GDSC- Session 1 Powerpoint PresentationRoadway to GDSC- Session 1 Powerpoint Presentation
Roadway to GDSC- Session 1 Powerpoint Presentationgdscghrcem
 
Unlocking Insights and Driving Solutions Using the 5 Whys Approach
Unlocking Insights and Driving Solutions Using the 5 Whys ApproachUnlocking Insights and Driving Solutions Using the 5 Whys Approach
Unlocking Insights and Driving Solutions Using the 5 Whys ApproachCIToolkit
 
How the Heck do you Teach Level Design? Educating in the Studio
How the Heck do you Teach Level Design? Educating in the StudioHow the Heck do you Teach Level Design? Educating in the Studio
How the Heck do you Teach Level Design? Educating in the StudioChristopher Totten
 
Making Sense of Multiple Ideas with Affinity Diagrams
Making Sense of Multiple Ideas with Affinity DiagramsMaking Sense of Multiple Ideas with Affinity Diagrams
Making Sense of Multiple Ideas with Affinity DiagramsCIToolkit
 
Applying the PDCA Cycle: A Blueprint for Continuous Improvement
Applying the PDCA Cycle: A Blueprint for Continuous ImprovementApplying the PDCA Cycle: A Blueprint for Continuous Improvement
Applying the PDCA Cycle: A Blueprint for Continuous ImprovementCIToolkit
 

Dernier (20)

The Role of Fishbone Diagram in Analyzing Cause and Effect
The Role of Fishbone Diagram in Analyzing Cause and EffectThe Role of Fishbone Diagram in Analyzing Cause and Effect
The Role of Fishbone Diagram in Analyzing Cause and Effect
 
Performance Management Notes for MBA Students
Performance Management Notes for MBA StudentsPerformance Management Notes for MBA Students
Performance Management Notes for MBA Students
 
Value Stream Map: A Visual Approach to Process Optimization
Value Stream Map: A Visual Approach to Process OptimizationValue Stream Map: A Visual Approach to Process Optimization
Value Stream Map: A Visual Approach to Process Optimization
 
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...
ANIn Coimbatore March 2024 | Agile & AI in Project Management by Dhilipkumar ...
 
An Important Step Toward Process Improvement
An Important Step Toward Process ImprovementAn Important Step Toward Process Improvement
An Important Step Toward Process Improvement
 
A3 Thinking: A Structured Approach to Problem Solving
A3 Thinking: A Structured Approach to Problem SolvingA3 Thinking: A Structured Approach to Problem Solving
A3 Thinking: A Structured Approach to Problem Solving
 
Tackling Fake Agility w/ Johanna Rothman
Tackling Fake Agility w/ Johanna RothmanTackling Fake Agility w/ Johanna Rothman
Tackling Fake Agility w/ Johanna Rothman
 
Organizations in a Future with Generative AI
Organizations in a Future with Generative AIOrganizations in a Future with Generative AI
Organizations in a Future with Generative AI
 
Empowering Resilience & Strategic Growth: Insights for Emerging Leaders
Empowering Resilience & Strategic Growth: Insights for Emerging LeadersEmpowering Resilience & Strategic Growth: Insights for Emerging Leaders
Empowering Resilience & Strategic Growth: Insights for Emerging Leaders
 
Growing a Thriving and Engaged Remote Team
Growing a Thriving and Engaged Remote TeamGrowing a Thriving and Engaged Remote Team
Growing a Thriving and Engaged Remote Team
 
Capacity2 - Briefing and Facilitation training slides
Capacity2 - Briefing and Facilitation training slidesCapacity2 - Briefing and Facilitation training slides
Capacity2 - Briefing and Facilitation training slides
 
Analyzing and Monitoring Processes through Time Value Mapping
Analyzing and Monitoring Processes through Time Value MappingAnalyzing and Monitoring Processes through Time Value Mapping
Analyzing and Monitoring Processes through Time Value Mapping
 
Forget Fiverr : Fractional Employment the ins and outs
Forget Fiverr : Fractional Employment the ins and outsForget Fiverr : Fractional Employment the ins and outs
Forget Fiverr : Fractional Employment the ins and outs
 
From Command Line to Reporting Line: The Diary of a First-Time EM
From Command Line to Reporting Line: The Diary of a First-Time EMFrom Command Line to Reporting Line: The Diary of a First-Time EM
From Command Line to Reporting Line: The Diary of a First-Time EM
 
What is 5S principles of trainers for training institutions.pdf
What is 5S principles of trainers for training institutions.pdfWhat is 5S principles of trainers for training institutions.pdf
What is 5S principles of trainers for training institutions.pdf
 
Roadway to GDSC- Session 1 Powerpoint Presentation
Roadway to GDSC- Session 1 Powerpoint PresentationRoadway to GDSC- Session 1 Powerpoint Presentation
Roadway to GDSC- Session 1 Powerpoint Presentation
 
Unlocking Insights and Driving Solutions Using the 5 Whys Approach
Unlocking Insights and Driving Solutions Using the 5 Whys ApproachUnlocking Insights and Driving Solutions Using the 5 Whys Approach
Unlocking Insights and Driving Solutions Using the 5 Whys Approach
 
How the Heck do you Teach Level Design? Educating in the Studio
How the Heck do you Teach Level Design? Educating in the StudioHow the Heck do you Teach Level Design? Educating in the Studio
How the Heck do you Teach Level Design? Educating in the Studio
 
Making Sense of Multiple Ideas with Affinity Diagrams
Making Sense of Multiple Ideas with Affinity DiagramsMaking Sense of Multiple Ideas with Affinity Diagrams
Making Sense of Multiple Ideas with Affinity Diagrams
 
Applying the PDCA Cycle: A Blueprint for Continuous Improvement
Applying the PDCA Cycle: A Blueprint for Continuous ImprovementApplying the PDCA Cycle: A Blueprint for Continuous Improvement
Applying the PDCA Cycle: A Blueprint for Continuous Improvement
 

PM Notebook - Chapter 4: Integration Management

  • 1. PM Notebook Summarizing Project Management Concepts for the PMP Exam Mohammad Elsheimy Road to PMP
  • 2. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | KEY TERMS DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 1 DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA/INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA/INFORMATION IS A PROPERTY OF THE AUTHOR. NONE IS INTENDED TO MAKE A PROFIT IN ANY WAY. THIS IS FOR PERSONAL USE ONLY.
  • 3. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | KEY TERMS DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 2 No great man ever complains of want of opportunity. Ralph Waldo Emerson
  • 4. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | KEY TERMS DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 3 Table of Contents Chapter 4 – Integration Management................................................................................................................ 4 Key Terms ............................................................................................................................................................... 4 Integration Types .............................................................................................................................................. 4 Changes, Defects, and Corrections............................................................................................................. 4 Processes................................................................................................................................................................ 4 1 – Develop Project Charter (Initiating) ....................................................................................................... 4 2 – Develop Project Management Plan (Planning)................................................................................... 5 3 – Direct and Manage Project Work (Executing)..................................................................................... 6 4 – Manage Project Knowledge (Executing).............................................................................................. 7 5 – Monitoring and Controlling Project Work (Monitoring & Controlling) .............................................. 8 6 – Perform Integrated Change Control (Monitoring & Controlling) ..................................................... 8 7 – Closing Project or Phase (Closing) .......................................................................................................... 9 Statement of Work (SOW) / Scope of Services ............................................................................................ 11 Product Analysis.................................................................................................................................................. 12 Knowledge Types ............................................................................................................................................... 12 Knowledge Management Techniques.......................................................................................................... 13 Configuration Management ........................................................................................................................... 13 Program/Project Evaluation and Review Technique (PERT)...................................................................... 14 PERT Planning .................................................................................................................................................. 14 Additional Terms ................................................................................................................................................. 14
  • 5. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | KEY TERMS DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 4 Key Terms Integration – Keeping everybody working towards the same goals and dealing with changes. Integration Types Process-Level Integration – pre-defined actions will bring pre-defined results and that process areas are integrated, meaning that what you do in one knowledge area affects other knowledge areas. Cognitive-Level Integration – Experience and maturity, leadership, and mastery of PM. Context-Level Integration – the idea that the ways projects are managed have changed or evolved as times have changed, with technology being a prime example. Changes, Defects, and Corrections Defect – Something faulty or erroneous in an item, procedure, component, or deliverable. In other words, any deliverable that is not meeting its requirements. Defect Repair (Rework) – When a component of the project does not meet specifications. Corrective Action – Any action taken to bring expected future project performance in line with the project management plan. Preventive Action – Steps that you take to avoid anticipated or potential problems or deviations. Processes 1 – Develop Project Charter (Initiating)  A statement of objectives and milestones of a project.  Usually it is the responsibility of project initiator, sponsor, or even portfolio steering committee. Sometimes, the project manager creates it, and the sponsor approves it.  Must be developed for all projects and for each phase.  Must be broad enough so it does not need to change as the project progresses.  Any change to the project charter should call into question whether project should continue.  If the project is in progress and no project charter has been developed, you must continue on the project without developing the charter as the project is already existed.  It sets out –  High-level goals and requirements  Main stakeholders and sponsors
  • 6. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 5  Level of authorization of PM  Links the project to the strategic plan and ongoing work of the organization.  Summary milestone schedule  Overall project risk  Responsibilities  Measurable project objectives  Success criteria  Preapproved financial resources  Pre-assigned resources  Approval requirements  High-level assumptions and constraints  Exit criteria Inputs 1. Contracts/Agreements – What you agreed to do like SLAs and vendor contracts. 2. Business Documents  Business Case  Benefits Management Plan 3. Statement of Work (SOW) 4. Enterprise Environmental Factors (EEFs) 5. Organizational Process Assets (OPAs)  Monitoring and Reporting Methods Tools 1. Expert Judgment 2. Data Gathering Techniques  Facilitation Techniques 3. Interpersonal/Team/Soft Skills 4. Meetings Outputs 1. Project Charter 2. Assumptions Log – List of constraints and things that you believe to be true or false. Assumptions that prove wrong can become risks for the project.  All identified assumptions must be recorded, analyzed, and tested.  High-level strategic and operational assumptions are documents in business case. 2 – Develop Project Management Plan (Planning)  A formal approved document used to manage project execution.  It defines how the project is executed, monitored and controlled. It also defines baselines.  Broken into subsidiary plans each dedicated to a knowledge area.  After baseline, change control is required to update the plan.  Participants in creating the management plan are project manager, team members, customers, and management.  Requires formal approval from sponsor or key stakeholders.
  • 7. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 6  Contents of project management plan is primarily influenced by the application area and complexity of project.  Kick-off meeting – o Happens after the plan is approved, and at the beginning of each phase. o Establishes working relationships and standard format for global communication. o Reviewing project plans. o Establishing individual and group responsibilities and accountabilities. Inputs 1. Project Charter 2. Outputs of the other planning processes 3. Enterprise Environmental Factors (EEFs) 4. Organizational Process Assets (OPAs) Tools 1. Expert Judgment 2. Data Gathering Techniques 3. Interpersonal/Team/Soft Skills 4. Meetings Outputs 1. Project Management Plan  Project management processes that will be used on the project and the details degree.  Knowledge area management plans – Scope, Schedule, Cost, Quality, Resources, Communications, Risk, Procurements, and Stakeholder.  Performance Measurement Baselines (PMB) – integrated scope-cost-schedule plan for the project to measure and manage performance.  Change Management Plan  Configuration Management Plan  Benefits Management Plan  Project Lifecycle (Phases) 3 – Direct and Manage Project Work (Executing)  Provide overall management of the project work.  Implement approved changes.  Lead and perform activities in the project management plan.  Perform activities to accomplish project objectives. Inputs 1. Approved Change Requests 2. Project Documents 3. Project Management Plan 4. Enterprise Environmental Factors (EEFs) 5. Organizational Process Assets (OPAs)
  • 8. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 7 Tools 1. Expert Judgment 2. Project Management Information System (PMIS) 3. Meetings Outputs 1. Work Performance Data – Created by measuring how well the processes from each knowledge area are being performed. 2. Deliverables – Products, services, documents, plans, schedules, budget, blueprints, and everything gets made along the way. 3. Issue Log – a documentation that contains a list of ongoing and closed issues of the project. It lists issue type, who and when the issue raised, priority, status, and so on. 4. Implemented Change Requests 5. Project Document Updates – Used to manage information which is not part of the plan. Prepared by PM for his own needs. 6. Project Management Plan Updates 7. OPA Updates 4 – Manage Project Knowledge (Executing) A way of using existing knowledge within the organization to achieve the project’s objectives and then using new knowledge gained on the project to contribute to the organizations body of knowledge. Inputs 1. Project Management Plan 2. Project Documents 3. Deliverables 4. EEFs 5. OPAs Tools 1. Expert Judgment 2. Knowledge Management Techniques 3. Information Management 4. Interpersonal/Team/Soft Skills Outputs 1. Lessons Learned Register 2. Project Management Plan Updates 3. OPA Updates
  • 9. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 8 5 – Monitoring and Controlling Project Work (Monitoring & Controlling)  Iterative activity  Happens throughout the project  Comparing actual project performance against project management plan. Inputs 1. Project Management Plan 2. Project Documents 3. Work Performance Data 4. Agreements 5. Enterprise Environmental Factors (EEFs) 6. Organizational Process Assets (OPAs) Tools 1. Expert Judgment 2. Data Analysis Techniques 3. Meetings 4. Decision Making Outputs 1. Work Performance Information 2. Forecasts 3. Recommended Corrective Actions 4. Product Document Update 5. Project Management Plan Updates 6. Change Requests 6 – Perform Integrated Change Control (Monitoring & Controlling)  How changes are managed and approved.  Happens throughout the project after a baseline established.  Responsibility of project manager.  Verbal changes happen, but should be documented.  Any change to project documents must be documented first in the change log and through configuration control.  When creating the outputs of processes in initiating and planning changes can be made without a formal change request, however, once something lie the charter has been issued, any requested changes would need to go through integrated change control.  A change in one of the constraints should be evaluated for impacts on all of the other constraints.  You should consider terminating projects with excessive changes and starting new ones with a more complete set of requirements.  It is necessary to analyze and approve change requests promptly because slow decision time may negatively affect time, cost or the feasibility of change.
  • 10. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 9 Steps Whenever there is a change, the following steps must be followed – 1. Logging the change request in change log. 2. Analyzing the impact of proposed change on all project constraints. 3. Sending all data to CCB for approval/postponing/rejection. 4. If approved, where there are variances, plans and baselines must be updated with new work, and new work should be implemented by direct and manage work. 5. If postponed or rejected, the results must be communicated to requestor/stakeholder. 6. Logging the request status in change log. Inputs 1. Change Requests 2. Work Performance Information 3. Project Management Plan 4. Enterprise Environmental Factors (EEFs) 5. Organizational Process Assets (OPAs) Tools 1. Expert Judgment 2. Change Control Board (CCB) Meetings 3. Change Control Tools – Software, forms, etc. 4. Decision Making Techniques 5. Data Analysis Techniques Outputs 1. Change Request Status Updates 2. Product Document Update 3. Project Management Plan Updates 4. Change Log 7 – Closing Project or Phase (Closing) Steps 1. Validate Scope – Confirm all requirements have been met. Happens after Control Quality. 2. Get Formal Acceptance 3. Create Project Closure Documents  Write Lessons Learned 4. Handover Deliverables 5. Close Contract 6. Release project team.
  • 11. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROCESSES DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 10 Stages 1. Work Closure  Finalizing formal acceptance of work.  Updating records to reflect results.  Sign-off on work completed. 2. Contract Closure  Finalizing open claims.  Updating records to reflect results.  Sign-off on work completed.  Certificate of contract closure. 3. Administrative Closure – An internal process. The confirmation that all of your documents and deliverables are correct.  Closing project accounts  Analyze project success or failure.  Archive project information.  Dealing with excess project material.  Starting any warranty/guarantee work.  Transferring product, service, or result to next phase.  Reallocating project facilities, equipment, and other resources.  Creating final project reports.  Releasing project team.  Measuring customer satisfaction. Characteristics  Closing Activities – o Finalize project or phase records o Audit project for success or failure o Transfer project’s results to next phase, production, or operations o Measure stakeholder satisfaction  Early project closure implies full closure.  All stakeholders must be involved in the creation of lessons learned.  Success of the project is measured primarily by customer satisfaction.  A project/phase is considered to be closed if the archives are completed.  Risk is the lowest at this stage.  Should not be delayed until project completion because useful information may be lost.  At the end of each phases you should review your business case, project charter, and benefits management plan. Termination  Sometimes there will be a termination manager who will carry out the closing procedures except personnel performance evaluations (which is a core function of PM or whoever supervising the work.)  Causes of termination - o Behavior-oriented reasons – account for the top causes of termination because it is much more difficult to manage people than things.
  • 12. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | STATEMENT OF WORK (SOW) / SCOPE OF SERVICES DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 11 o Excessive Changes – consider terminating projects with excessive changes and starting new ones with a more complete set of requirements. o Starvation – When the project no longer receives the resources needed to continue. Inputs 1. Project Charter 2. Project Management Plan 3. Accepted Deliveries 4. Acceptance Criteria 5. Project Documents  Procurement Documentation 6. Business Documents  Business Case Tools 1. Expert Judgment 2. Meetings –  To confirm that deliverables have been accepted. To validate that the exit criteria have been met.  To formalize completion of contracts.  To evaluate the satisfaction of the stakeholders.  To gather lessons learned.  To transfer knowledge.  To celebrate success. 3. Data Analysis Techniques Outputs 1. Final Product, Service, or Result 2. Final Report – should include recommendations for changing current practices. 3. Project Document Updates 4. Organizational Process Assets (OPAs)  Lesson Learned  Historical Information Statement of Work (SOW) / Scope of Services Created by customer or sponsor. No formal signs required. Defines the following –  Purpose  Project-specific activities and deliverables.  Project durations and milestones.  Resource hours.  Billing rates.  Service fees.  Payment schedule and terms.
  • 13. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PRODUCT ANALYSIS DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 12  Listing of representatives. Product Analysis Product Breakdown Requirements Analysis System Analysis System Engineering Value Analysis (VA) –  Concerned with existing products.  Involves a current product being analyzed and evaluated by a team, to reduce costs, improve product function or both.  Value Analysis exercises use a plan which step-by-step, methodically evaluates the product in a range of areas. These include costs, function, alternative components and design aspects such as ease of manufacture and assembly.  A significant part of VA is a technique called Functional Analysis, where the product is broken down and reviewed as a number of assemblies. Here, the function is identified and defined for each product assembly. Costs are also assigned to each one. Value Engineering (VE) –  Concerned with new products.  It is applied during product development.  The focus is on reducing costs, improving function or both, by way of teamwork-based product evaluation and analysis.  This takes place before any capital is invested in tooling, plant or equipment. Knowledge Types Formal/Explicit Knowledge – knowledge that can be quickly and easily expressed through conversations, documentation, figures, and numbers.  Codified explicit knowledge lacks context and is open to different interpretations. Tacit Knowledge – knowledge that is more difficult to express or transfer to another person because it is personal beliefs, values, knowledge gain from experience, and know-how when doing a task.  Tacit knowledge cannot be codified, however, creating an atmosphere of trust can motivate people to share their tacit knowledge.
  • 14. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | KNOWLEDGE MANAGEMENT TECHNIQUES DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 13 Knowledge Management Techniques Communities of Practice and Special Interest Groups Creativity and Ideas Management Techniques / Group Creativity Techniques – Like brainstorming, affinity diagrams, mind mapping, etc. Discussing Forums and Focus Groups Knowledge Fairs and Cafes – Participants move between tents to learn fast lessons. Meetings Networking with Colleagues Reverse Shadowing – The expert follows you; the expert offers coaching. Storytelling – To explain tacit knowledge. Training Events Work Shadowing – To follow, or shadow, an expert.  Passive – Following and observing without any engagement.  Active – Following, observing and engaging. Configuration Management The process for applying technical and administrative direction and surveillance of the project implementation. Involves a thorough change control system to ensure the project produces the desired results. Configuration Identification – The process of identifying attributes of products and labeling them with unique identifiers. Configuration Status Accounting (CSA) – Recording and reporting of information needed to manage configuration items effectively, including a record of the approved configuration documentation and identification numbers. Configuration Control (Verification and Auditing) – Verification that the configuration identification for a configuration item is accurate, complete, and will meet specified program needs.
  • 15. PM NOTEBOOK CHAPTER 4 – INTEGRATION MANAGEMENT | PROGRAM/PROJECT EVALUATION AND REVIEW TECHNIQUE (PERT) DISCLAIMER: THE MATERIAL INCLUDED IN THIS DOCUMENT IS BASED ON DATA / INFORMATION GATHERED FROM VARIOUS RELIABLE SOURCES. NONE OF THIS DATA / INFORMATION IS A PROPERTY OF THE AUTHOR. 14 Program/Project Evaluation and Review Technique (PERT) Program Evaluation and Review Technique (PERT) is a technique adopted by organizations to analyze and represent the activity in a project, and to illustrate the flow of events in a project. PERT serves as a management tool to analyze, define and integrate events. PERT also illustrates the activities and interdependencies in a project. The main goal of PERT is to reduce the cost and time needed to complete a project. PERT Planning PERT planning usually involves the following steps – 1. Identifying Tasks and Milestones – Every project involves a series of required tasks. These tasks are listed in a table allowing additional information on sequence and timing to be added later. 2. Placing the Tasks in a Proper Sequence – The tasks are analyzed and placed in a sequence to get the desired results. 3. Network Diagramming – A network diagram is drawn using the activity sequence data showing the sequence of serial and parallel activities. 4. Time Estimating – This is the time required to carry out each activity, in three parts –  Optimistic timing – The shortest time to complete an activity  Most likely timing – The completion time having the highest probability  Pessimistic timing – The longest time to complete an activity 5. Critical Path Estimating – This determines the total time required to complete a project. Additional Terms Performance Measurement Baselines (PMB) – A snapshot of your project’s scope, schedule and cost.  Scope Baseline  Schedule Baseline  Cost Baseline Process Capability Baseline (PCB) – specifies what results to expect when a process is followed. Using PCB, a project manager can predict, at the gross level, effort required at various stages, defect densities, overall quality, and productivity. Tailoring Processes – determining which processes are appropriate, and the appropriate degree of rigor for each process. You need to measure tailoring needs for each project by considering EEFs.