CAPM Project Integration Management — Questions and Answers

Question 1: What is Project Integration Management?

Managing the project team's integration into the organization
The process of identifying, defining, combining, unifying, and coordinating project management processes and activities within the project management process groups (Correct answer)
Integrating software systems on a project
Managing the integration of new team members onto the project

Correct answer: The process of identifying, defining, combining, unifying, and coordinating project management processes and activities within the project management process groups

Project Integration Management encompasses the processes and activities needed to identify, define, combine, unify, and coordinate all project management processes—it is the overarching 'glue' that holds all other knowledge areas together.

Integration Management is distinguished from other knowledge areas because it involves making trade-offs among competing objectives and alternatives. It is the project manager's primary domain. The processes—Develop Project Charter, Develop Project Management Plan, Direct and Manage Project Work, Manage Project Knowledge, Monitor and Control Project Work, Perform Integrated Change Control, and Close Project or Phase—span the entire project lifecycle and connect all other knowledge areas.

Question 2: What is the project charter and who typically authorizes it?

A detailed work plan created by the project manager
A document issued by a project sponsor or initiating entity that formally authorizes the existence of a project and provides the project manager with the authority to apply resources (Correct answer)
A contract with an external vendor
A financial authorization document approved by the CFO

Correct answer: A document issued by a project sponsor or initiating entity that formally authorizes the existence of a project and provides the project manager with the authority to apply resources

The project charter formally authorizes the project, names the project manager, defines the high-level scope and objectives, and is issued by the project sponsor or an entity with the authority to commit organizational resources.

The project charter serves several critical purposes: (1) formally authorizes the project's existence within the organization, (2) names the project manager and defines their authority level, (3) provides the initial scope boundaries, objectives, and success criteria, (4) identifies the sponsor and key initial stakeholders, (5) documents high-level assumptions and constraints, (6) provides the initial budget and milestone summary. It must be issued by someone external to the project who has organizational authority to commit resources.

Question 3: What is the primary output of the 'Develop Project Management Plan' process?

The work breakdown structure
The project management plan (Correct answer)
The project charter
The stakeholder register

Correct answer: The project management plan

The project management plan is the primary output of Develop Project Management Plan—a comprehensive document integrating all subsidiary plans and baselines that guides project execution, monitoring, and control.

The project management plan is not a single document but an integrated collection of: subsidiary management plans (scope, schedule, cost, quality, resource, communications, risk, procurement, stakeholder), performance measurement baselines (scope, schedule, cost), and additional components (change management plan, configuration management plan, development approach, project lifecycle description). All changes to any component require formal change requests through Integrated Change Control.

Question 4: What is the purpose of the 'Direct and Manage Project Work' process?

To review completed deliverables for quality
To lead and perform the work defined in the project management plan and implement approved changes (Correct answer)
To develop the project schedule
To identify and analyze project risks

Correct answer: To lead and perform the work defined in the project management plan and implement approved changes

Direct and Manage Project Work involves leading and performing the activities defined in the project management plan, implementing approved changes, and producing the project's deliverables.

Direct and Manage Project Work (Executing process group) is the primary execution process. Key activities include: executing planned project activities, creating project deliverables, managing and developing the project team, allocating budget, communicating project status, generating lessons learned, and implementing approved corrective and preventive actions. Key outputs include: deliverables, work performance data, change requests, and updates to the project management plan and project documents.

Question 5: What is 'work performance data' as generated in the Direct and Manage Project Work process?

Analyzed project performance reports ready for stakeholder distribution
The raw observations and measurements identified during activities being performed to carry out project work (Correct answer)
The approved change requests from Integrated Change Control
The completed project deliverables

Correct answer: The raw observations and measurements identified during activities being performed to carry out project work

Work performance data consists of raw, unanalyzed measurements and observations—such as actual start/finish dates, percent complete, costs incurred, and defect counts—gathered during project execution.

Work performance data is the foundation of the project's performance reporting chain: (1) Raw Data (Direct and Manage Project Work) → (2) Work Performance Information (monitoring processes analyze data against plan) → (3) Work Performance Reports (Control Communications packages information for stakeholders). Examples of work performance data: '47% of Schedule Activity A is complete,' '$23,450 has been spent on work package B.'

Question 6: What is 'Perform Integrated Change Control' and why is it important?

A technical process for integrating software change requests
The process of reviewing, approving, and managing all change requests across the entire project to ensure changes are controlled and their impacts are understood before approval (Correct answer)
A process for documenting completed project work
A process that only applies to changes in project scope

Correct answer: The process of reviewing, approving, and managing all change requests across the entire project to ensure changes are controlled and their impacts are understood before approval

Perform Integrated Change Control reviews all change requests, approves or rejects them after impact analysis, and manages the implementation of approved changes—ensuring no unauthorized changes occur and impacts are understood.

Integrated Change Control is 'integrated' because changes to any aspect of the project (scope, schedule, cost, quality, resources, risk) affect all other aspects and must be evaluated holistically. The process: (1) receives change requests, (2) analyzes the impact on all affected areas, (3) presents to the Change Control Board (CCB) for approval/rejection, (4) documents the decision, (5) updates all affected documents if approved, and (6) communicates the decision.

Question 7: What is the Change Control Board (CCB)?

A committee of external auditors reviewing project finances
A formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project baseline (Correct answer)
A regulatory body that approves all project changes
A team of technical experts who implement approved changes

Correct answer: A formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project baseline

The Change Control Board (CCB) is a formally chartered group with defined authority to review, approve, reject, or defer proposed changes to the project baseline.

CCB composition varies by project and organization but typically includes: the project manager, project sponsor, key functional managers, and subject matter experts. The CCB reviews change requests along with their impact assessments, makes approval decisions, and documents rationale. Not all projects have a formal CCB—on smaller projects, the project manager or sponsor may have sole authority. The CCB's decisions are documented and implemented through the project management plan updates.

Question 8: What is the 'configuration management plan' and how does it relate to Integration Management?

A plan for managing the project team's organizational structure
A component of the project management plan describing how configuration items will be identified, tracked, and controlled throughout the project (Correct answer)
A plan for configuring project management software tools
A plan for managing vendor configurations in procurement

Correct answer: A component of the project management plan describing how configuration items will be identified, tracked, and controlled throughout the project

The configuration management plan describes how project artifacts (deliverables, documentation, technical specifications) will be identified, tracked, version-controlled, and changed—ensuring the integrity of the project's technical and management documents.

Configuration management addresses version control and change authority for project documents and deliverables. It defines: what items require configuration management (configuration items), how they are uniquely identified, how versions are tracked, who has authority to approve changes to each item, how changes are implemented and verified, and how the configuration library is maintained.

Question 9: In the 'Close Project or Phase' process, what does the project manager verify before officially closing?

That all invoices have been submitted to accounting
That all project or phase work is completed according to plan, all deliverables are accepted, lessons learned are documented, and all administrative closure activities are finished (Correct answer)
That the project team has been reassigned to new projects
That all risk registers are archived

Correct answer: That all project or phase work is completed according to plan, all deliverables are accepted, lessons learned are documented, and all administrative closure activities are finished

Close Project or Phase verifies that all work is complete, deliverables are formally accepted, contracts are closed, lessons learned are documented, final performance reports are produced, and all project records are archived.

Closing activities include: (1) obtaining final acceptance of deliverables from the customer/sponsor, (2) completing financial closure, (3) completing contract closure with vendors, (4) documenting lessons learned, (5) archiving all project records, (6) releasing project resources, (7) updating organizational process assets with templates and final estimates, and (8) issuing the final project report.

Question 10: What is a 'lessons learned register' and when should it be updated?

A document updated only at project close
A project document used to record knowledge gained during a project that can be used to improve performance on future projects, updated throughout the project, not just at close (Correct answer)
A register of all risks that materialized during the project
A report submitted to executive management after project completion

Correct answer: A project document used to record knowledge gained during a project that can be used to improve performance on future projects, updated throughout the project, not just at close

The lessons learned register captures insights—successes, failures, and improvement recommendations—throughout the project lifecycle, not just at closure, so that knowledge is captured while it is fresh.

The lessons learned register should be updated at: project kickoff (transfer of lessons from similar projects), after each major phase or milestone, when significant issues or risks materialize, and at project close. Topics captured include: scope management effectiveness, stakeholder communication successes/failures, risk events that occurred, estimation accuracy, and process improvements. Lessons learned become part of the organization's OPA library.

Question 11: What is the 'assumption log' and how does it relate to Integration Management?

A document recording project budget assumptions only
A project document used to record all assumptions and constraints identified during the project—created at initiation and updated throughout (Correct answer)
A log of team member time entries
A record of risk events that have been assumed to be low probability

Correct answer: A project document used to record all assumptions and constraints identified during the project—created at initiation and updated throughout

The assumption log records all assumptions and constraints identified during the project, providing a reference for decisions made based on those assumptions and a trigger for risk assessment when assumptions change.

Assumptions are statements treated as true for planning purposes in the absence of verified information. Constraints are factors that limit project options. The assumption log: captures the assumption, the date it was identified, its potential impact if wrong, and its current status. When an assumption changes or is found to be false, a risk or issue is typically raised, often triggering a change request.

Question 12: Which document provides the project manager with the formal authority to begin project work and access organizational resources?

Work Breakdown Structure
Scope Statement
Project Charter (Correct answer)
Project Management Plan

Correct answer: Project Charter

The project charter formally authorizes the project and grants the project manager authority to apply resources—without a signed charter, the project manager has no official organizational authority to commit resources.

The project charter is signed by the sponsor (an entity external to the project but within the organization). This signature transfers authority to the project manager to plan and execute the project using organizational resources. Without this authority, the project manager cannot formally direct team members, commit budget, or make binding decisions on behalf of the organization. The charter is particularly important in matrix organizations.

Question 13: What is the purpose of 'Monitor and Control Project Work'?

To execute project activities according to the project management plan
To track, review, and report overall progress against performance objectives defined in the project management plan (Correct answer)
To close the project
To develop the project management plan

Correct answer: To track, review, and report overall progress against performance objectives defined in the project management plan

Monitor and Control Project Work tracks, reviews, and reports on overall project performance—comparing actual performance to the project management plan and identifying areas needing corrective or preventive action.

Monitor and Control Project Work (Monitoring and Controlling process group) collects work performance data from Direct and Manage Project Work, analyzes it against the project management plan and baselines, identifies variances, and generates work performance reports. When variances are identified, the process triggers corrective or preventive actions (as change requests) through Integrated Change Control.

Question 14: What is the relationship between 'corrective action,' 'preventive action,' and 'defect repair' in Integration Management?

They are all the same type of change request
Corrective action fixes current deviations; preventive action prevents future deviations; defect repair fixes identified defects in deliverables—all are change request types processed through Integrated Change Control (Correct answer)
Corrective and preventive actions are approved by the project manager alone; defect repair requires CCB approval
Only defect repair requires a formal change request

Correct answer: Corrective action fixes current deviations; preventive action prevents future deviations; defect repair fixes identified defects in deliverables—all are change request types processed through Integrated Change Control

Corrective actions realign current performance with the plan; preventive actions reduce the probability of future negative events; defect repairs fix identified nonconformances—all are processed as change requests through Integrated Change Control.

Corrective action: addresses a deviation that has already occurred. Preventive action: addresses a potential future deviation before it occurs. Defect repair: corrects a specific nonconformance in a deliverable. All three types are change requests because they modify project documents, baselines, or execution activities that were formally approved in the project management plan.

Question 15: What are organizational process assets (OPAs) and how do they support Integration Management?

Physical assets owned by the organization like buildings and equipment
Plans, processes, policies, procedures, knowledge bases, and historical information from the organization that can influence project success (Correct answer)
The organization's financial accounts
IT hardware and software owned by the organization

Correct answer: Plans, processes, policies, procedures, knowledge bases, and historical information from the organization that can influence project success

Organizational process assets (OPAs) are the accumulated plans, processes, policies, procedures, lessons learned, historical information, and templates from the organization that project managers leverage to execute projects more effectively.

OPAs fall into two categories: (1) Processes and Procedures (standards, templates, guidelines, change control procedures, communication templates, risk checklists), and (2) Corporate Knowledge Base (historical project information, lessons learned repositories, benchmarking data, financial databases). Project managers use OPAs throughout all project management processes and continuously update them through and after projects.

Question 16: What is the 'Manage Project Knowledge' process, and what process group does it belong to?

Identifying project risks; Risk Management process group
Using existing knowledge and creating new knowledge to achieve project objectives and contribute to organizational learning; Executing process group (Correct answer)
Documenting lessons learned; Monitoring and Controlling process group
Creating the knowledge management plan; Planning process group

Correct answer: Using existing knowledge and creating new knowledge to achieve project objectives and contribute to organizational learning; Executing process group

Manage Project Knowledge (Executing process group) leverages existing organizational knowledge to support project work while capturing new knowledge generated by the project for future organizational benefit.

Manage Project Knowledge was added in PMBOK 6th edition to address the importance of knowledge management. It covers: leveraging prior knowledge (lessons learned, historical information, expert judgment) to improve current project performance, and creating/capturing new knowledge for the organization's benefit. Key tools include: knowledge management systems, collaboration tools, expert interviews, and communities of practice (CoPs).

Question 17: How does Integration Management relate to the other PMBOK knowledge areas?

Integration Management is separate from other knowledge areas and does not interact with them
Integration Management connects and aligns all other knowledge areas—decisions in one area affect others, and integration management provides the framework for resolving trade-offs and coordinating all processes (Correct answer)
Integration Management only connects scope and schedule management
Integration Management replaces the need for individual knowledge area plans

Correct answer: Integration Management connects and aligns all other knowledge areas—decisions in one area affect others, and integration management provides the framework for resolving trade-offs and coordinating all processes

Integration Management is the connective tissue linking all 9 other PMBOK knowledge areas—a change in scope affects schedule, cost, and risk, and Integration Management provides the framework (Integrated Change Control, project management plan) for managing these interconnections.

Without Integration Management, the other knowledge areas would be independent silos. Integration provides: the project charter (authorizing the project), the project management plan (integrating all subsidiary plans), Direct and Manage Project Work (coordinating execution across all areas), Monitor and Control Project Work (watching all areas simultaneously), Perform Integrated Change Control (managing changes to all areas holistically), and Close Project (bringing all areas to formal conclusion).

Question 18: What is a 'project management information system' (PMIS) and how is it used in Integration Management?

A human resources system for managing project team members
A set of tools—software applications, data repositories, and reporting systems—used to gather, integrate, store, and distribute project management information (Correct answer)
A financial accounting system used to track project costs
A document management system for storing project contracts

Correct answer: A set of tools—software applications, data repositories, and reporting systems—used to gather, integrate, store, and distribute project management information

PMIS is the integrated set of tools used to gather, analyze, store, and communicate project information across all knowledge areas—supporting Integration Management by providing a single environment for managing all project data.

PMIS tools may include: project scheduling software (MS Project, Primavera), cost management systems, configuration management tools, document management platforms (SharePoint), collaboration tools (Teams, Slack), dashboards (Power BI, Tableau), and issue/risk tracking tools (Jira). In Integration Management, PMIS supports: schedule development and tracking, cost performance measurement (EVM), change request documentation and tracking, performance reporting, and knowledge management.

Question 19: What is the significance of the 'project management plan' being an integrated document?

It is significant only because it saves paper by combining multiple documents
Integration means all subsidiary plans are aligned with each other and with the project baselines—changes in one plan trigger updates in related plans through Integrated Change Control (Correct answer)
Integration refers to the plan being shared digitally across the organization
Integration means the plan has been approved by the entire project team

Correct answer: Integration means all subsidiary plans are aligned with each other and with the project baselines—changes in one plan trigger updates in related plans through Integrated Change Control

An integrated project management plan means all subsidiary plans (scope, schedule, cost, etc.) are consistent with each other and with the baselines—when one area changes, Integrated Change Control ensures all affected plans are updated together.

The project management plan is integrated in two dimensions: (1) Horizontal integration—all subsidiary plans are consistent with each other (the schedule is based on the WBS, the cost baseline matches the schedule, the quality plan aligns with scope requirements), and (2) Vertical integration—all plans align with the project charter and organizational strategy.

Question 20: What does 'management reserve' refer to in Integration Management, and how does it differ from 'contingency reserve'?

Management reserve is for known risks; contingency reserve is for unknown risks
Contingency reserve is for known risks (identified risks with response plans); management reserve is for unknown unknown risks (unforeseeable events) and is held by management, not the project manager (Correct answer)
They are the same concept with different names
Contingency reserve is approved by the project manager; management reserve requires board approval

Correct answer: Contingency reserve is for known risks (identified risks with response plans); management reserve is for unknown unknown risks (unforeseeable events) and is held by management, not the project manager

Contingency reserve addresses identified risks (known-unknowns) and is part of the cost baseline controlled by the project manager; management reserve covers unidentified risks (unknown-unknowns) and is held outside the cost baseline by management.

The budget structure in PMBOK is: Work Package Estimates + Contingency Reserves = Cost Baseline; Cost Baseline + Management Reserve = Project Budget. Contingency reserve is pre-approved for the project manager to use as identified risk events materialize. Management reserve is held by senior management for truly unforeseen events and requires management approval and typically a formal change request to the project management plan.

Question 21: What is 'tailoring' in the context of Integration Management?

Adjusting the project team's clothing budget
Adapting the project management processes, tools, and techniques to be appropriate for the specific project context, constraints, and environment (Correct answer)
Reducing the project scope to fit the budget
Customizing the project deliverables to meet individual customer preferences

Correct answer: Adapting the project management processes, tools, and techniques to be appropriate for the specific project context, constraints, and environment

Tailoring is the deliberate, justified adaptation of project management processes, lifecycle, tools, and techniques to fit the specific needs of the project—because no single approach works for all projects.

The PMBOK Guide explicitly encourages tailoring because applying all processes at full rigor to a small, simple project would create unnecessary overhead. Tailoring decisions include: which processes to include or skip, which documents to combine or simplify, whether to use predictive, adaptive, or hybrid life cycles. Tailoring is documented and should be a conscious, reasoned decision. The project manager is responsible for appropriate tailoring.

Question 22: During project execution, a team member implements an improvement to the product that was not in the approved project management plan. What type of issue does this represent?

A positive risk response
An unauthorized change—a violation of Integrated Change Control requiring immediate corrective action (Correct answer)
An example of progressive elaboration
A valid use of project reserves

Correct answer: An unauthorized change—a violation of Integrated Change Control requiring immediate corrective action

Implementing an unapproved change—even a beneficial one—is an unauthorized change that violates Integrated Change Control and requires a retroactive change request to document and evaluate the change's impact.

This scenario illustrates gold plating combined with an Integrated Change Control violation. Even if the improvement is genuinely beneficial, the team member bypassed the formal change process that exists to: assess impacts on other project areas, maintain documentation accuracy, keep the project management plan as the authoritative reference, and preserve the audit trail. Corrective action: document the change retroactively as a change request and assess its impact on the plan.

Question 23: What should a project manager do when a project sponsor requests a major scope change?

Immediately implement the change since the sponsor has authority
Reject the change and explain that scope is fixed
Document the change as a formal change request and submit it through the Integrated Change Control process for impact assessment and approval (Correct answer)
Update the project scope statement to include the new work

Correct answer: Document the change as a formal change request and submit it through the Integrated Change Control process for impact assessment and approval

Any scope change—regardless of its source or apparent importance—must first be documented as a formal change request and processed through Integrated Change Control before any implementation work begins.

Even sponsor requests must go through Integrated Change Control. The project manager's first response to any change request is to document it formally (on a change request form or in the PMIS), acknowledge receipt to the requester, and begin the impact assessment process. The sponsor's authority does not bypass change control—it means the sponsor is typically on the CCB and their vote carries significant weight.

Question 24: What is the purpose of a 'project kickoff meeting' from an Integration Management perspective?

To finalize the project schedule
To formally mark the beginning of project execution, align all stakeholders on objectives and roles, communicate the project management approach, and build team commitment (Correct answer)
To approve the final project budget
To conduct risk identification for the project

Correct answer: To formally mark the beginning of project execution, align all stakeholders on objectives and roles, communicate the project management approach, and build team commitment

From an Integration Management perspective, the kickoff meeting formally launches execution, integrates team and stakeholder understanding of the project's direction, and establishes the shared framework for project management activities.

The kickoff meeting serves as an integration event: it brings together all key parties who will be involved in executing the project management plan, aligns them on objectives and success criteria (scope integration), introduces the project management approach and tools (process integration), establishes communication norms (communications integration), and creates a shared social contract among team members. A well-run kickoff significantly reduces integration failures during execution.

Question 25: What is 'enterprise environmental factors' (EEFs) and how do they influence Integration Management?

Internal project budget constraints only
Conditions not under the control of the project team—organizational culture, market conditions, government regulations, infrastructure—that influence, constrain, or direct the project (Correct answer)
The physical environment where the project takes place
Only external government regulations affecting the project

Correct answer: Conditions not under the control of the project team—organizational culture, market conditions, government regulations, infrastructure—that influence, constrain, or direct the project

Enterprise environmental factors (EEFs) are internal and external conditions outside the project team's control that influence project options, performance, and outcomes—they must be considered in Integration Management planning.

EEFs include: organizational culture and structure, existing personnel capabilities, marketplace conditions, stakeholder risk tolerances, industry standards, legal and regulatory requirements, and available infrastructure. In Integration Management, EEFs affect decisions in every process—from what governance structure is appropriate for the project charter, to which communication technologies are available (PMIS), to what change control formality is expected by the organization. Unlike OPAs (which can be updated by the project), EEFs are inputs the team must adapt to, not change.

CAPM Project Integration Management

What is Project Integration Management?

🃏 CAPM Flashcards — Study This Quiz as Flip Cards →

📚 Want to go deeper? Read the Full CAPM Study Guide →