Top Banner
CH4: Project Integration Management ABDULLAH ALKHADRAWY, PMP
84

PMP PMBOK5 Ch4 integration management

May 08, 2015

Download

Business

Abdullah Ahmed
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: PMP PMBOK5 Ch4 integration management

CH4: ProjectIntegration Management

ABDULLAH ALKHADRAWY, PMP

Page 2: PMP PMBOK5 Ch4 integration management

Course Instructor: Abdullah Ahmed Al-Khadrawy.

BSc. Civil Engineering 2006 (V.Good HD).

Graduation Project (Project Management)

2006.(Excellent graded)

Certified from Primavera Inc. ® : Advanced user for

Primavera P6 (2008).

Certified from Primavera Inc. ® : Advanced user for

primavera Contract Manager 12 (2009).

Attended courses (PMP, CCE, FIDIC, Project

Management, Arbitration for Engineering Contracts)

[2007-2013]

Certified from PMI ® as PMP ® [email protected]

Page 3: PMP PMBOK5 Ch4 integration management

ProjectIntegrationManagement

4-Integration

5-Scope

6-Time

7-Cost

8-Quality

9-HumanResource

10-Communications

11-Risk

12-Procurement

13-Stakeholder

Executing

Monitoring&Controlling

Closing

Page 4: PMP PMBOK5 Ch4 integration management

4.1 Develop 4.2 DevelopProject

4.4 Monitor andControl ProjectWork

Project Charter ManagementPlan

4.5 PerformIntegratedChange Control

4.3 Direct andManage ProjectWork

4.6 C loseProject or Phase

unification, consolidation, communication, and integrative actionsthat are crucial to controlled project execution through

completion, successfully managing stakeholder expectations, andmeeting requirements.

Initiating Planning ExecutingMonitoring andControlling

Closing

4ProjectIntegrationManagement

4.1 Develop 4.2 DevelopProject

4.4 Monitor andControl ProjectWork

Project Charter ManagementPlan

4.5 PerformIntegratedChange Control

4.3 Direct andManage ProjectWork

4.6 C loseProject or Phase

unification, consolidation, communication, and integrative actionsthat are crucial to controlled project execution through

completion, successfully managing stakeholder expectations, andmeeting requirements.

Initiating Planning ExecutingMonitoring andControlling

ClosingProjectIntegrationManagement

4

Page 5: PMP PMBOK5 Ch4 integration management

4.1 Develop Project Charter

Page 6: PMP PMBOK5 Ch4 integration management

4.1 Develop Project Charter Initiating

1. Project statement of work2. Business case3. Agreements4. Enterprise environmental factors

5. Organizational process assets

1. Expert judgment2. Facilitation techniques

1. Project charter

developing a document that formally authorizes the existence of a project andprovides the project manager with the authority to apply organizational

resources to project activities.

Page 7: PMP PMBOK5 Ch4 integration management

4.1 Develop Project Charter:-

1. Project statement of work

2. Business case

3. Agreements

4. Enterprise environmental factors

5. Organizational process assets

Inputs

Page 8: PMP PMBOK5 Ch4 integration management

4.1 Develop Project Charter:- Inputs

1. Project statement of work: (SOT)

narrative description of products, services, or results to be delivered by a project.

- For internal projects, the project initiator or sponsor provides the statement of work based on business needs, product, orservice requirements.

- For external projects, be received from the customer as part of a bid document, (e.g., a request for proposal, request forinformation, or request for bid) or as part of a contract.

- The SOW references the following:

Business need. Based on: market demand, technological advance, legal requirement, government regulation,or environmental consideration.

Typically, the business need and the cost-benefit analysis are contained in the business case to justify the project.

Product scope description. documents the characteristics of the product, service, or results . & the relationshipbetween the products, services, or results being created and the business need that the project will address.

Strategic plan: the organization’s strategic vision, goals, and objectives and may contain a high-level missionstatement. All projects should be aligned with their organization’s strategic plan. Strategic plan alignment ensuresthat each project contributes to the overall objections of the organization.

Page 9: PMP PMBOK5 Ch4 integration management

4.1 Develop Project Charter:- Inputs

2. Business casedescribes the necessary information from a business standpoint to determine whether or not theproject is worth the required investment.- It is commonly used for decision making by managers or executives above the project level.- Typically, the business need and the cost-benefit analysis are contained in the business case- The sponsor should agree to the scope and limitations of the business case.- In the case of multiphase projects, periodically reviewed to ensure that the project is on track to

deliver the business benefits.

- In the early stages of the project life cycle, periodic review of the business case by the sponsor alsohelps to confirm that the project is still aligned with the business case.- The project manager is responsible for ensuring that the project effectively and efficiently meets the

goals of the organization and those requirements of a broad set of stakeholders, as defined in thebusiness case.

Page 10: PMP PMBOK5 Ch4 integration management

4.1 Develop Project Charter:- Inputs

3. AgreementsAgreements are used to define initial intentions for a project. eg•contracts,•memorandums of understanding (MOUs),• service level agreements (SLA),•letter of agreements,•letters of intent,•verbal agreements,•email,•or other written agreements.•Typically, a contract is used when a project is being performed for an external customer.

verbal agreements

Page 11: PMP PMBOK5 Ch4 integration management

4.1 Develop Project Charter:- Inputs

4. Enterprise environmental factors• Governmental standards, industry standards, or regulations(e.g. codes of conduct, quality standards, or worker protection standards),• Organizational culture and structure, and• Marketplace conditions.

5. Organizational process assets• Organizational standard processes, policies, and process definitions,• Templates (e.g., project charter template), and• Historical information and lessons learned knowledge base.

Page 12: PMP PMBOK5 Ch4 integration management

4.1 Develop Project Charter:- Tools and Techniques:-

1. Expert jugement

2. Facilitation techniques

Page 13: PMP PMBOK5 Ch4 integration management

4.1 Develop Project Charter:- Tools and Techniques:-

1. Expert jugement

• Other units within the organization,

• Consultants,

• Stakeholders, including customers or sponsors,

• Professional and technical associations,

• Industry groups,

• Subject matter experts (SME), and

• Project management office (PMO).

Page 14: PMP PMBOK5 Ch4 integration management

4.1 Develop Project Charter:- Tools and Techniques:-

2. Facilitation techniques

Brainstorming,

conflict resolution,

problem solving,

meeting management.

Page 15: PMP PMBOK5 Ch4 integration management

4.1 Develop Project Charter Outputs

Page 16: PMP PMBOK5 Ch4 integration management

Project charterprovides the PMwith authority

Q: Which project managementprocess should a project managerperform to get a formal authorizationfor a project or a project phase?

A. Develop Project Management planB. Develop Project CharterC. Perform Integrated Change ControlD. Direct and Manage Project Execution

B

Page 17: PMP PMBOK5 Ch4 integration management

4.2 Develop Project Management Plan

1. Project charter

2. Outputs from other processes3. Enterprise environmental factors4. Organizational process assets

1. Expert judgment2. Facilitation techniques

1. Project management plan

defining, preparing, and coordinating all subsidiary plans and integrating theminto a comprehensive project management plan

Planning

Page 18: PMP PMBOK5 Ch4 integration management

4.2 Develop Project Management Plan

1. Project charter

2. Outputs from other processes (Planning Processes)

3. Enterprise environmental factors

4. Organizational process assets

Inputs

Page 19: PMP PMBOK5 Ch4 integration management

4.2 Develop Project Management Plan Inputs

2. Outputs from other processes (Planning Processes)

}Changes for planning

documents

Project Management Plan

Page 20: PMP PMBOK5 Ch4 integration management

4.2 Develop Project Management Plan Inputs

3. Enterprise environmental factors• Governmental or industry standards;

• Project management body of knowledge

• Project management information system (e.g., an automated tool, such as a scheduling software tool, aconfiguration management system, an information collection and distribution system, or web interfaces to otheronline automated systems);

• Organizational structure, culture, management practices, and sustainability;

• Infrastructure (e.g., existing facilities and capital equipment); and

• Personnel administration (e.g., hiring and termination guidelines, employee performance reviews, and employeedevelopment and training records).

Page 21: PMP PMBOK5 Ch4 integration management

4.2 Develop Project Management Plan Inputs

4. Organizational process assets• Standardized guidelines, work instructions, proposal evaluation criteria, and performancemeasurement criteria;• Project management plan template, including:

○ Guidelines and criteria for tailoring the organization’s set of standard processes to satisfy the specificneeds of the project, and

○ Project closure guidelines or requirements such as the product validation and acceptance criteria;• Change control procedures, the steps by which any project documents will be modified and how anychanges will be approved and validated;• Project files from previous projects (e.g., scope, cost, schedule and performance measurementbaselines, project calendars, project schedule network diagrams, and risk registers,);• Historical information and lessons learned knowledge base;• Configuration management knowledge base containing the versions and baselines of all officialorganization standards, policies, procedures, and any project documents.

Page 22: PMP PMBOK5 Ch4 integration management

4.2 Develop Project Management Plan:- Tools and Techniques:-

1. Expert jugement

2. Facilitation techniques

Page 23: PMP PMBOK5 Ch4 integration management

4.2 Develop Project Management Plan:- Tools and Techniques:-

1. Expert jugement• Tailor the process to meet the project needs,

• Develop technical and management details to be included in the project management plan,

• Determine resources and skill levels needed to perform project work,

• Define the level of configuration management to apply on the project,

• Determine which project documents will be subject to the formal change control process, and

• Prioritize the work on the project to ensure the project resources are allocated to the appropriatework at the appropriate time.

Page 24: PMP PMBOK5 Ch4 integration management

4.2 Develop Project Management Plan:- Tools and Techniques:-

2. Facilitation techniques

Brainstorming,

Conflict resolution,

Problem solving,

Meeting management.

Page 25: PMP PMBOK5 Ch4 integration management

4.2 Develop Project Management Plan:- OutputsProject baselines include, but are not limited to:• Scope baseline (Section 5.4.3.1),• Schedule baseline (Section 6.6.3.1), and• Cost baseline (Section 7.3.3.1).Subsidiary plans include, but are not limited to:• Scope management plan (Section 5.1.3.1),• Requirements management plan (Section 5.1.3.2),• Schedule management plan (Section 6.1.3.1),• Cost management plan (Section 7.1.3.1),• Quality management plan (Section 8.1.3.1),• Process improvement plan (Section 8.1.3.2),• Human resource management plan (Section 9.1.3.1),• Communications management plan (Section 10.1.3.1),• Risk management plan (Section 11.1.3.1),• Procurement management plan (Section 12.1.3.1), and• Stakeholder management plan (Section 13.2.3.1).

Page 26: PMP PMBOK5 Ch4 integration management

4.2 Develop Project Management Plan:- Outputs, the project management plan may also include the following:• Life cycle selected for the project and the processes that will be applied to each phase;• Details of the tailoring decisions specified by the project management team as follows:

○ Project management processes selected by the project management team,○ Level of implementation for each selected process,○ Descriptions of the tools and techniques to be used for accomplishing those processes, and○ Description of how the selected processes will be used to manage the specific project, including the dependencies and

interactions among those processes and the essential inputs and outputs.• Description of how work will be executed to accomplish the project objectives;• Change management plan that documents how changes will be monitored and controlled;• Configuration management plan that documents how configuration management will be performed;• Description of how the integrity of the project baselines will be maintained;• Requirements and techniques for communication among stakeholders; and• Key management reviews for content, the extent of, and timing to address, open issues and pending decisions.

Page 27: PMP PMBOK5 Ch4 integration management

4.2 Develop Project Management Plan:- Outputs

Page 28: PMP PMBOK5 Ch4 integration management

PM needs theprojectmanagementplan to: Direct &Manage ProjectActivities

Q:The Project management plan enablesthe project manager to …………:

A. Monitor and control project workB. Develop a project scope statementC. Direct and manage project executionD. Implement integrated change controlC

Page 29: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work

.1 Project management plan

.2 Approved change requests

.3 Enterprise environmental factors

.4 Organizational process assets

.1 Expert judgment

.2 Project management informationsystem.3 Meetings

.1 Deliverables

.2 Work performance data

.3 Change requests

.4 Project management plan updates

.5 Project documents updates

leading and performing the work defined in the project management plan andimplementing approved changes to achieve the project’s objectives.

Excuting

Page 30: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work Perform activities to accomplish project objectives; Create project deliverables to meet the planned project work; Provide, train, and manage the team members assigned to the project; Obtain, manage, and use resources including materials, tools, equipment, and facilities; Implement the planned methods and standards; Establish and manage project communication channels, both external and internal to the project team;Generate work performance data, such as cost, schedule, technical and quality progress, and status tofacilitate forecasting; Issue change requests and implement approved changes into the project’s scope, plans, and environment;Manage risks and implement risk response activities;Manage sellers and suppliers;Manage stakeholders and their engagement; and Collect and document lessons learned and implement approved process improvement activities.

Page 31: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work Direct and Manage Project Work also requires review ofthe impact of all project changes and the implementation of approved changes: Corrective action —An intentional activity that realigns the performance of theproject work with the project management plan; Preventive action—An intentional activity that ensures the future performanceof the project work is aligned with the project management plan; and/or Defect repair—An intentional activity to modify a nonconforming product orproduct component.

Page 32: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work

1. Project management plan

2. Approved change requests

3. Enterprise environmental factors

4. Organizational process assets

Inputs

Page 33: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work Inputs

2. Approved change requests• Approved change requests are an output of the Perform Integrated Change Controlprocess,

• Include those requests reviewed and approved for implementation by the changecontrol board (CCB).

• The approved change request may be a corrective action, a preventative action, or adefect repair.

• Approved change requests are scheduled and implemented by the project team,• and can impact any area of the project or project management plan.•The approved change requests can also modify the policies, project management plan,procedures, costs, or budgets or revise the schedules.

• Approved change requests may require implementation of preventive or correctiveactions.

Page 34: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work Inputs

3. Enterprise environmental factors• Organizational, company, or customer culture and structure of the performing or sponsororganizations;

• Infrastructure (e.g., existing facilities and capital equipment);

• Personnel administration (e.g., hiring and firing guidelines, employee performance reviews, andtraining records);

• Stakeholder risk tolerances, for example allowable cost overrun percentage; and

• Project management information system (e.g., an automated tool suite, such as a scheduling softwaretool, a configuration management system, an information collection and distribution system, or webinterfaces to other online automated systems).

Page 35: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work Inputs

4. Organizational process assets• Standardized guidelines and work instructions;

• Communication requirements defining allowed communication media, record retention, and securityrequirements;

• Issue and defect management procedures defining issue and defect controls, issue and defectidentification and resolution, and action item tracking;

• Process measurement database used to collect and make available measurement data on processesand products;

• Project files from previous projects (e.g., scope, cost, schedule, performance measurement baselines,project calendars, project schedule, network diagrams, risk registers, planned response actions, definedrisk impact, and documented lessons learned); and

• Issue and defect management database(s) containing historical issue and defect status, controlinformation, issue and defect resolution, and action item results.

Page 36: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work:- Tools and Techniques:-

1. Expert judgment

2. Project management information system

3. Meetings

Page 37: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work:- Tools and Techniques:-

1. Expert jugement

•Other units within the organization;

•Consultants and other subject matter experts (internal and external);

• Stakeholders, including customers, suppliers, or sponsors;.

• Professional and technical associations.

Page 38: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work:- Tools and Techniques:-

2. Project management information system• The project management information system, which is part of the environmentalfactors,

• provides access to tools, such as a scheduling tool, a work authorization system, aconfiguration management system, an information collection and distributionsystem, or interfaces to other online automated systems.

• Automated gathering and reporting on key performance indicators (KPI) can be partof this system.

Page 39: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work:- Tools and Techniques:-

3. Meetings• Attendees at the meetings may include the project manager, the project team and appropriatestakeholders

•Each attendee should have a defined role to ensure appropriate participation• Meetings tend to be one of three types:

1- Information exchange;2- Brainstorming, option evaluation, or design;3- Decision making.

• Meeting types should not be mixed as a best practice.• Meetings should be prepared with a well-defined agenda, purpose, objective, and time frame andshould be appropriately documented with meeting minutes and action items.

• Meetings are most effective when all participants can be face-to-face in the same location.•Virtual meetings can be held using audio and/ or video conferencing tools, but generally requireadditional preparation and organization to achieve the same effectiveness of a face-to-face meeting.

Page 40: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work:- Outputs

1. Deliverables

2. Work performance data

3. Change requests

4. Project management plan updates

5. Project documents updates

Page 41: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work:- Outputs2. Work performance data (raw data)• Work performance data are the raw observations and measurements identified during activities beingperformed to carry out the project work

• Data is gathered through work execution and passed to the controlling processes of each process areafor further analysis.

• work completed,• key performance indicators (SPI, CPI, etc…),• technical performance measures,• start and finish dates of schedule activities,• number of change requests,• number of defects,• actual costs, and actual durations, etc.

Page 42: PMP PMBOK5 Ch4 integration management

4.3 Direct and Manage Project Work:- Outputs3. Change requests• Corrective action —An intentional activity that realigns the performance of theproject work with the project management plan;

•Preventive action —An intentional activity that ensures the future performance of theproject work is aligned with the project management plan;

•Defect repair —An intentional activity to modify a nonconforming product orproduct component; and/or

•Updates —Changes to formally controlled project documents, plans, etc., to reflectmodified or additional ideas or content.

Page 43: PMP PMBOK5 Ch4 integration management

PM needs theprojectmanagementplan to: Direct &Manage ProjectActivities

Q:The project management team has selectedthe project management processes that willbe used in an oil mining project. In whichdocument will a project sponsor be able tofind such information?

A. Project charterB. Project scope statementC. Project management planD. Project statement of workC

Page 44: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work

.1 Project management plan

.2 Schedule forecasts

.3 Cost forecasts

.4 Validated changes

.5 Work performance information

.6 Enterprise environmentalfactors

.7 Organizational process assets

.1 Expert judgment

.2 Analytical techniques

.3 Project management informationsystem

.4 Meetings

.1 Change requests

.2 Work performance reports

.3 Project management plan updates

.4 Project documents updates

tracking, reviewing, and reporting the progress to meet the performanceobjectives defined in the project management plan

Monitoring&Controlling

Page 45: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work Comparing actual project performance against the project management plan;

Assessing performance to determine whether any corrective or preventive actions are indicated, and thenrecommending those actions as necessary;

Identifying new risks and analyzing, tracking, and monitoring existing project risks to make sure the risksare identified, their status is reported, and that appropriate risk response plans are being executed;

Maintaining an accurate, timely information base (status reports) concerning the project’s product(s) andtheir associated documentation through project completion;

Providing information (not data) to support status reporting, progress measurement, and forecasting;Providing forecasts to update current cost and current schedule information;

Monitoring implementation of approved changes as they occur; and

Providing appropriate reporting on project progress and status to program management when the projectis part of an overall program.

Page 46: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work

1. Project management plan

2. Schedule forecasts

3. Cost forecasts

4. Validated changes

5. Work performance information

6. Enterprise environmental factors

7. Organizational process assets

Inputs

Page 47: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work Inputs

2. Schedule forecasts• Time estimate to complete (ETC).

• Schedule variance (SV) and

• Schedule performance index (SPI).

• For projects not using earned value management, variances against the plannedfinish dates and forecasted finish dates are provided

Page 48: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work Inputs

3. Cost forecasts• The cost forecasts are derived from progress against the cost baseline and computedestimates to complete (ETC).

• Cost variance (CV) and cost performance index (CPI).

• An estimate at completion (EAC) can be compared to the budget at completion (BAC)to see if the project is still within tolerance ranges or if a change request is required.

•For projects not using earned value management, variances against the plannedversus actual expenditures and forecasted final costs are provided.

Page 49: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work Inputs

3. Validated changes• A validated change provides the necessary data to confirm that the change wasappropriately executed.

• Approved changes that result from the Perform Integrated Change Control processrequire validation to ensure that the change was appropriately implemented

Page 50: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work Inputs

5.Work Performance Information• Work performance information is the performance data collected from variouscontrolling processes,

• Analyzed in context, and integrated based on relationships across areas.

• Thus work performance data has been transformed into work performanceinformation.

• Data in itself cannot be used in the decision-making process as it has only out-of-context meaning.

• Work performance information, however, is correlated and contextualized, andprovides a sound foundation for project decisions.

Page 51: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work Inputs

6. Enterprise environmental factors• Governmental or industry standards (e.g., regulatory agency regulations, codes of conduct, productstandards, quality standards, and workmanship standards),

• Organization work authorization systems,

• Stakeholder risk tolerances, and

• Project management information system (e.g., an automated tool suite, such as a scheduling softwaretool, a configuration management system, an information collection and distribution system, or webinterfaces to other online automated systems).

Page 52: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work Inputs

7. Organizational process assets• Organizational communication requirements;

• Financial controls procedures (e.g., time reporting, required expenditure and disbursement reviews,

accounting codes, and standard contract provisions);

• Issue and defect management procedures defining issue and defect controls, issue and defectidentification, and resolution and action item tracking;

• Change control procedures, including those for scope, schedule, cost, and quality variances;

• Risk control procedures including risk categories, probability definition and impact, and probabilityand impact matrix;

• Process measurement database used to make available measurement data on processes and products;

• Lessons learned database.

Page 53: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work:- Tools and Techniques:-

1. Expert judgment

2. Analytical techniques

3. Project management information system

4. Meetings

Page 54: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work:- Tools and Techniques:-

1. Expert jugement

•Expert judgment is used by the project management team to interpret the information provided by the

monitor and control processes.

• The project manager, in collaboration with the team, determines the actions required to ensure that

project performance matches expectations.

Page 55: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work:- Tools and Techniques:-

2. Analytical techniques• Regression analysis,• Grouping methods,• Causal analysis,• Root cause analysis,• Forecasting methods (e.g., time series, scenario building, simulation, etc.),• Failure mode and effect analysis (FMEA),• Fault tree analysis (FTA), Reserve analysis,• Trend analysis,• Earned value management,• Variance analysis.

Page 56: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work:- Tools and Techniques:-

3. Project management information system

• The project management information system, which is part of the

environmental factors,

• Provides access to tools, such as scheduling, cost, and resourcing tools,

performance indicators, databases, project records, and financials used

during the Monitor and Control Project Work process.

Page 57: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work:- Tools and Techniques:-

3. Meetings• Attendees at the meetings may include the project manager, the project team and appropriatestakeholders

•Each attendee should have a defined role to ensure appropriate participation• Meetings tend to be one of three types:

1- Information exchange;2- Brainstorming, option evaluation, or design;3- Decision making.

• Meeting types should not be mixed as a best practice.• Meetings should be prepared with a well-defined agenda, purpose, objective, and time frame andshould be appropriately documented with meeting minutes and action items.

• Meetings are most effective when all participants can be face-to-face in the same location.•Virtual meetings can be held using audio and/ or video conferencing tools, but generally requireadditional preparation and organization to achieve the same effectiveness of a face-to-face meeting.

Page 58: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work:- Outputs

1. Change requests

2. Work performance reports

3. Project management plan updates

4. Project documents updates

Page 59: PMP PMBOK5 Ch4 integration management

4.4 Monitor and Control Project Work:- Outputs2. Work performance reports

• Status reports,• Memos,• Justifications,• Information notes,.• Recommendations,• Updates.

Page 60: PMP PMBOK5 Ch4 integration management

Monitoring&ControllingProject Activitiesincludes collectionof the project data& forecasting suchcost & schedulemeasurements

Q:Collecting the project data and facilitatingthe forecasting of cost and schedule areactions performed by the project managerand the project management team duringwhich of the following project processgroups?

A. InitiatingB. PlanningC. ExecutingD. Monitoring and ControllingD

Page 61: PMP PMBOK5 Ch4 integration management

4.5 Perform Integrated change control

.1 Project management plan

.2 Work performancereports.3 Change requests.4 Enterprise environmentalfactors.5 Organizational process assets

.1 Expert judgment

.2 Meetings

.3 Change control tools

.1 Approved change requests

.2 Change log

.3 Project management planupdates.4 Project documents updates

reviewing all change requests; approving changes and managing changes todeliverables, organizational process assets, project documents, and the project

management plan; and communicating their disposition

Monitoring&Controlling

Page 62: PMP PMBOK5 Ch4 integration management

Change Control Board (CCB)a formally chartered group responsible for reviewing, evaluating,approving, delaying, or rejecting changes to the project, and forrecording and communicating such decisions.

* Customer or sponsor approval may be required for certain changerequests after CCB approval, unless they are part of the CCB.

Page 63: PMP PMBOK5 Ch4 integration management

Configuration control• Configuration identification. Identification and selection of a configuration item toprovide the basis for which the product configuration is defined and verified,products and documents are labeled, changes are managed, and accountability ismaintained.

• Configuration status accounting. Information is recorded and reported as towhen appropriate data about the configuration item should be provided. Thisinformation includes a listing of approved configuration identification, status ofproposed changes to the configuration, and the implementation status of approvedchanges.

• Configuration verification and audit. Configuration verification and configurationaudits ensure the composition of a project’s configuration items is correct and thatcorresponding changes are registered, assessed, approved, tracked, and correctlyimplemented. This ensures the functional requirements defined in the configurationdocumentation have been met.

Page 64: PMP PMBOK5 Ch4 integration management

4.5 Perform Integrated change control

1. Project management plan

2. Work performance reports

3. Change requests

4. Enterprise environmental factors

5. Organizational process assets

Inputs

Page 65: PMP PMBOK5 Ch4 integration management

4.5 Perform Integrated change control:- Tools and Techniques:-

1. Expert judgment

2. Meetings

3. Change control tools

Page 66: PMP PMBOK5 Ch4 integration management

4.5 Perform Integrated change control:- Tools and Techniques:-

1. Expert jugement

• Project management team’s expert judgment

• Consultants,

• Stakeholders, including customers or sponsors, Professional and technical associations, Industrygroups,

• Subject matter experts (SMEs),

• Project management office (PMO).

Page 67: PMP PMBOK5 Ch4 integration management

4.5 Perform Integrated change control Outputs

1. Approved change requests

2. Change log

3. Project management plan updates

4. Project documents updates

Page 68: PMP PMBOK5 Ch4 integration management

4.5 Perform Integrated change control Outputs1. Approved change requests

CCB

Page 69: PMP PMBOK5 Ch4 integration management

4.5 Perform Integrated change control Outputs2. Change log

Page 70: PMP PMBOK5 Ch4 integration management

Q:

Which input to the Direct and ManageProject Execution process contains thedocumented and authorized changes toadjust the scope of the project?

A. Approved corrective actionsB. Approved preventive actionsC. Approved change requestsD. Approved defect repairC

Page 71: PMP PMBOK5 Ch4 integration management

4.6 Close Project or Phase

.1 Project management plan

.2 Accepted deliverables

.3 Organizational process assets

.1 Expert judgment

.2 Analytical techniques

.3 Meetings

.1 Final product, service, or resulttransition.2 Organizational process assetsupdates

Finalizing all activities across all of the Project Management Process Groups toformally complete the project or phase.

Closing

Page 72: PMP PMBOK5 Ch4 integration management

4.6 Close Project or Phase

1. Project management plan

2. Accepted deliverables

3. Organizational process assets

Inputs

Page 73: PMP PMBOK5 Ch4 integration management

4.6 Close Project or Phase* The project manager reviews all prior information from the previousphase closures to ensure that all project work is completed and that theproject has met its objectives.* The project manager reviews the scope baseline to ensure completionbefore considering the project closed.* Establishes the procedures to investigate and document the reasons foractions taken if a project is terminated before completion* In order to successfully achieve this, the project manager needs toengage all the proper stakeholders in the process

Page 74: PMP PMBOK5 Ch4 integration management

4.6 Close Project or PhaseThis includes all planned activities necessary for administrative closure of theproject or phase, including step- by-step methodologies that address:

1. Actions and activities necessary to satisfy completion or exit criteria forthe phase or project;

2. Actions and activities necessary to transfer the project’s products, services,or results to the next phase or to production and/or operations; and

3. Activities needed to collect project or phase records, audit project successor failure, gather lessons learned and archive project information forfuture use by the organization.

Page 75: PMP PMBOK5 Ch4 integration management

4.6 Close Project or Phase

1. Project management plan

2. Accepted deliverables

3. Organizational process assets

Inputs

Page 76: PMP PMBOK5 Ch4 integration management

4.6 Close Project or Phase Inputs

3. Organizational process assets• Project or phase closure guidelines or requirements

(e.g., administrative procedures, project audits, project evaluations, and transition criteria); and

• Historical information and lessons learned knowledge base

(e.g., project records and documents, all project closure information and documentation, informationabout both the results of previous project selection decisions and previous project performanceinformation, and information from risk management activities).

Page 77: PMP PMBOK5 Ch4 integration management

4.6 Close Project or Phase:- Tools and Techniques:-

1. Expert judgment

2. Analytical techniques

3. Meetings

Page 78: PMP PMBOK5 Ch4 integration management

4.6 Close Project or Phase:- Tools and Techniques:-

1. Expert jugement

• Other project managers within the organization,

• Project management office (PMO),

• Professional and technical associations.

Page 79: PMP PMBOK5 Ch4 integration management

4.6 Close Project or Phase:- Tools and Techniques:-

2. Analytical techniques• Regression analysis,• Trend analysis

Page 80: PMP PMBOK5 Ch4 integration management

4.6 Close Project or Phase:- Tools and Techniques:-

3. Meetings• Described in Section 4.3.2.3. Meetings may be face-to-face, virtual, formal, orinformal.

• This may include project team members and other stakeholders, involved in oraffected by the project.

• Types of meetings include, but are not limited to lessons learned, closeout, usergroup, and review meetings.

Page 81: PMP PMBOK5 Ch4 integration management

4.5 Perform Integrated change control Outputs

1. Final product, service, or result transition

2. Organizational process assets updates

Page 82: PMP PMBOK5 Ch4 integration management

2. Organizational process assets updates

• Project files , e.g., project management plan; scope, cost, schedule, and project calendars; risk registers and otherregisters; change management documentation; planned risk response actions; and risk impact.

• Project or phase closure documents: formal documentation that indicates completion of the project or phaseand the transfer of the completed project or phase deliverables to others. PM reviews prior phase documentation,customer acceptance documentation, and the contract, to ensure that all project requirements are. If the projectwas terminated, the formal documentation indicates why the project was terminated and formalizes theprocedures for the transfer of the finished and unfinished deliverables of the cancelled project to others .

• Historical information : that has been recommended for use by future projects.

4.5 Perform Integrated change control Outputs

Page 83: PMP PMBOK5 Ch4 integration management

Q:Project managers need to performchange control from the start throughthe end of the project. Whichconfiguration management activity is notpart of the Perform Integrated ChangeControl process?

A. Configuration identificationB. Architecture configuration and controlC. Configuration status accountingD. Configuration verification and auditing

B

Configurationidentification, Configurationstatus accounting,&Configurationverification andauditing interactall with changecontrolmanagement

Page 84: PMP PMBOK5 Ch4 integration management