Free CAPM Practice Test Questions and Answers (2026)

Portfolio management is the centralized management of one or more portfolios to achieve strategic objectives. The primary responsibility of a portfolio manager is to ensure the collection of projects, programs, and operational work aligns with the organization's overall strategy. This involves selecting, prioritizing, and balancing the portfolio components to maximize business value and meet strategic goals. Therefore, the ability to manage and align various initiatives with the organization's strategic objectives is the most critical qualification for a portfolio manager.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute. Section 1.2.3

Portfolios

states

"A portfolio is a collection of projects

programs

subsidiary portfolios

and operations managed as a group to achieve strategic objectives."

2. Project Management Institute. (2017). The Standard for Portfolio Management (4th ed.). Project Management Institute. Section 1.3

Relationship Among Portfolios

Programs

and Projects

explains that portfolio management focuses on "doing the right work" to align with organizational strategy

while project and program management focus on "doing the work right."

3. Aubry

M.

& Lavoie-Tremblay

M. (2018). The art of managing a portfolio of projects in a complex and uncertain world. Project Management Journal

49(1)

5-10. This article emphasizes that portfolio management's core is the strategic alignment of projects with organizational goals. DOI: https://doi.org/10.1177/8756972818754298

Administer Procurements (known as Control Procurements in the PMBOK® Guide – Sixth Edition) is the process of managing the relationship with the seller, monitoring contract performance, and making changes or corrections as needed. A key function of this process is to ensure that both the buyer's and the seller's performance meet the contractual requirements. This involves actively managing the contract to ensure all obligations are met and that the legal rights of both parties are protected throughout the life of the agreement. This process continues from contract signing until contract closure.

1. Project Management Institute. (2013). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Fifth Edition. Section 12.3

Administer Procurements

p. 379. The guide states

"Administer Procurements is the process of managing procurement relationships

monitoring contract performance

and making changes and corrections as needed... The buyer and seller both administer the procurement contract for similar purposes. Each party ensures that both it and the other party meet their contractual obligations..."

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Section 12.3

Control Procurements

p. 492. This section defines the process as

"Control Procurements is the process of managing procurement relationships

monitoring contract performance

making changes and corrections to contracts as appropriate

and closing out contracts."

3. Vargas

R. V. (2015). Practical Guide to Project Planning: The Standard for Project Management. PMI® Global Congress 2015

London

England. Newtown Square

PA: Project Management Institute. This publication

aligned with PMI standards

discusses the procurement management processes

reinforcing that contract administration involves ensuring compliance with the terms and conditions of the contract.

The Plan Procurement Management process involves making decisions about acquiring goods and services for the project. To do this effectively, the project team needs a clear understanding of the project's budget and the estimated costs of the work. Activity cost estimates, which are a type of project document, provide the necessary financial data to determine what can be procured versus what might be developed in-house (informing make-or-buy analysis) and to establish budgets for planned procurements. This cost information is a crucial input, often contained within the project management plan and other project documents that feed into this process.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute.

For the correct answer (B): Section 12.1.1.4

Project Documents. This section lists inputs like "Resource requirements

" which are directly linked to cost estimates. The overall "Project Management Plan" (Section 12.1.1.3)

which includes the cost baseline derived from activity cost estimates

is also a primary input.

For incorrect option (A) and (D): Section 12.1.3

Outputs. This section explicitly lists "Make-or-Buy Decisions" and "Procurement Documents" as outputs of this process.

For incorrect option (C): Section 12.2.1.3

Inputs. "Seller proposals" are listed as an input to the Conduct Procurements process.

2. MIT OpenCourseWare. (2012). 16.852J / ESD.342J Integrating the Lean Enterprise

Fall 2005. Lecture 15: Sourcing and Procurement. Massachusetts Institute of Technology.

The lecture materials emphasize that understanding project requirements and associated costs is a prerequisite for developing a sourcing and procurement strategy

reinforcing that cost estimates are an essential input to the planning phase. (Available at: ocw.mit.edu)

The Risk Management Plan is a subsidiary plan of the overall project management plan that details how risk management activities will be structured and performed. It establishes the framework for risk management throughout the project. Key components defined within this plan include the methodology, roles, budget, timing, risk categories, definitions of risk probability and impact, the probability and impact matrix, stakeholder risk tolerances, and formats for reporting and tracking risk activities. The elements mentioned in the question are all fundamental to this plan.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 11.1.3.1

Risk Management Plan. Newtown Square

PA: Project Management Institute.

This section explicitly lists the components of the Risk Management Plan

stating it can include "Definitions of risk probability and impact

" "Revised stakeholder tolerances

" and "Tracking

" which describes how risk activities will be documented and audited.

2. Kerzner

H. (2017). Project Management: A Systems Approach to Planning

Scheduling

and Controlling (12th ed.). Chapter 18

Risk Management. John Wiley & Sons.

This academic text

widely used in university project management courses

describes the risk management plan as the document that defines the scales for probability and impact

establishes risk thresholds (tolerances)

and sets up the process for risk monitoring and control (tracking).

The risk rating, also known as the risk score or exposure, is a fundamental concept in project risk management. It is calculated by multiplying the probability of a risk event occurring by its potential impact on project objectives. The formula is:

Risk Rating = Probability × Impact

Given the values:

Risk Rating = 0.56

Impact = 0.80

We can rearrange the formula to solve for Probability:

Probability = Risk Rating / Impact

Probability = 0.56 / 0.80

Probability = 0.70

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 11.4.2.2

Decision Tree Analysis. This section explains the calculation of Expected Monetary Value (EMV) as the product of probability and impact

which is the quantitative application of the principle used in the question.

2. University of Maryland

Project Management Center for Excellence. (n.d.). ENCE424/724: Project Management Fundamentals

Lecture 7: Project Risk Management. The course materials define risk exposure as the product of the probability of a risk event and its consequences (impact). This foundational formula (Risk = P × I) is used for both qualitative and quantitative risk analysis.

3. Chapman

C.

& Ward

S. (2003). Project Risk Management: Processes

Techniques and Insights (2nd ed.). John Wiley & Sons. Chapter 6

"Estimate Step

" details the process of estimating probability and impact to determine risk levels

establishing the multiplicative relationship as a core principle.

Project Integration Management is the specific Knowledge Area responsible for identifying, defining, combining, unifying, and coordinating the various processes and activities within the Project Management Process Groups. The process groups (e.g., Planning, Executing, Monitoring & Controlling) are not discrete, one-time phases; they overlap and are repeated. This iterative and interactive nature necessitates a central coordinating function to manage interdependencies, resolve issues, and ensure all parts of the project work together cohesively toward the project objectives. This unification is the core purpose of Project Integration Management.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 4: Project Integration Management

Introduction

p. 70. The text states

"Project Integration Management... is the specific responsibility of the project manager... The need for integration is also created by the iterative nature of project management."

2. Schwalbe

K. (2015). Information Technology Project Management (8th ed.). Cengage Learning. Chapter 4

"Project Integration Management

" discusses how this knowledge area coordinates all other knowledge areas throughout the project life cycle

emphasizing its importance in managing the complex interactions between processes. (This textbook is widely used in university project management courses).

3. MIT OpenCourseWare. (2012). 16.852J / ESD.352J Project Management

Fall 2012. Lecture 2: The Project Management Framework. The lecture notes describe Project Integration Management as the overarching function that ties together the other nine knowledge areas across the five process groups

essential for managing the project as a whole.

The human resource management plan, a component of the overall project management plan, is the central document that establishes the framework for managing the project team. It explicitly defines the project roles and responsibilities, creates project organization charts to visualize reporting relationships, and includes the staffing management plan. The staffing management plan outlines the timeline and methods for team member acquisition, development, management, and eventual release from the project. Therefore, this plan comprehensively addresses how team structure and staffing will be managed.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Newtown Square

PA: Project Management Institute. Section 9.1.3.1

Human Resource Management Plan

pp. 318–319.

2. Meredith

J. R.

Shafer

S. M.

Mantel

Jr.

S. J.

& Sutton

M. M. (2017). Project Management: A Managerial Approach (10th ed.). Wiley. Chapter 5

"Project Organization

" discusses the structuring of project teams

roles

and reporting relationships as a key planning function.

3. MIT OpenCourseWare. (2012). 16.852J / ESD.342J System Architecture

Lecture 10: Organizations and System Architecture. Massachusetts Institute of Technology. This lecture discusses how organizational structure

including roles and reporting lines

is a critical component of project and system planning. Available at https://ocw.mit.edu.

An activity network diagram is a graphical representation of the logical relationships and dependencies among project schedule activities. One of the methods used to create these diagrams is the Arrow Diagramming Method (ADM). In ADM, activities are represented by arrows, and the nodes or circles at each end of the arrow represent the start and end events (milestones). Due to this graphical convention, the ADM technique and the resulting diagrams are commonly referred to as arrow diagrams.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute.

Glossary

p. 703: "Arrow Diagramming Method (ADM). A schedule network diagramming technique in which schedule activities are represented by arrows. See also precedence diagramming method (PDM)."

Section 8.1.2.4

Data Representation: Lists "Activity network diagrams" as a tool for Plan Quality Management

alongside Affinity diagrams

Tree diagrams

and Matrix diagrams.

2. Mubashir

M. (2021). Project Management Key to Success: A Practical Guide. CRC Press.

Chapter 5

Project Time Management

Section 5.3.2.1: "The activity network diagram is also known as the arrow diagram or PERT (program evaluation and review technique) chart."

3. Kerzner

H. (2017). Project Management: A Systems Approach to Planning

Scheduling

and Controlling (12th ed.). Wiley.

Chapter 12

Scheduling Techniques

p. 468: "The two most common techniques for network construction and analysis are the program evaluation and review technique (PERT)

which is an event-oriented network

and the critical path method (CPM)

which is an activity-oriented network... PERT networks are also called arrow diagrams."

In project management, a risk is defined as an uncertain event or condition that, if it occurs, has a positive or negative effect on project objectives. The actual materialization or occurrence of that uncertain condition is called a risk event. The possibility of a delay from the permitting agency was the risk; the agency actually taking longer than planned is the risk event itself. This event triggers consequences (impacts) and may require the execution of a risk response plan.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute. Section 2.8

Uncertainty Performance Domain

p. 103. This section discusses how uncertainty gives rise to risks

which are "events or conditions" that can occur.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute. Glossary

p. 720. Defines risk as "An uncertain event or condition..." The actual occurrence is therefore the event.

3. MIT OpenCourseWare. (2012). 16.852J / ESD.352J System Project Management

Lecture 11: Risk Management. Massachusetts Institute of Technology. Slide 6. This lecture defines risk as a triplet {scenario

probability

consequence}

where the "scenario" is the adverse event

such as a permit delay.

To gain insight into past stakeholder management strategies, a project manager must consult organizational knowledge repositories. Historical information from previous projects provides the actual stakeholder management plans that were used. The lessons-learned database contains the analysis of those plans, detailing what strategies were effective, which were not, and why. Evaluating both provides a comprehensive foundation for developing a new, more effective plan by leveraging past successes and avoiding previous failures.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute.

Page 512

Section 13.2.1.4

Organizational Process Assets: This section lists OPAs as an input to the "Plan Stakeholder Engagement" process. It explicitly states that these assets include the "lessons learned repository" and "historical information from previous projects

" which contain information on effective stakeholder management strategies.

2. Project Management Institute. (2021). The Standard for Project Management and A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.

Page 107

Section 2.8.5

Working with Information: This section emphasizes the importance of using explicit knowledge

which is "readily shared through...documentation." This includes historical databases and lessons learned

which are critical for planning and improving project work

including stakeholder engagement.

3. Kerzner

H. (2017). Project Management: A Systems Approach to Planning

Scheduling

and Controlling (12th ed.). Wiley.

Chapter 5.10

The Project Office: This chapter discusses the role of the Project Management Office (PMO) in maintaining a historical database of project information

including lessons learned. This repository is identified as a primary source for project managers to consult to avoid "reinventing the wheel" and to learn from the successes and failures of past projects.

The Manage Communications process is focused on the execution of the communications management plan. Its primary purpose is to ensure that the right information reaches the right stakeholders at the right time and in the right format. This execution enables a continuous, efficient, and effective flow of information among all project participants, which is crucial for project integration, stakeholder engagement, and decision-making. This process transforms the communication plan into tangible communication activities and artifacts.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute. Section 10.2

Page 375. The text explicitly states

"The key benefit of this process is that it enables an efficient and effective communication flow between project stakeholders."

2. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute. Section 2.4

Project Work Performance Domain

Page 73. This section emphasizes that managing project communications and engagement leads to "shared understanding" through "effective and efficient" communication processes.

3. Vliet

H. van. (2010). Software Engineering: Principles and Practice (3rd ed.). Wiley. While a software engineering text

it aligns with PMI principles in its project management sections

noting that the execution of a communication plan is to facilitate an "effective flow of information" to prevent project failures. (Referenced in various university software project management courses).

A product lifecycle encompasses all stages a product goes through, from conception to withdrawal from the market. This is a long-term view. A project lifecycle is a temporary endeavor with a defined beginning and end, undertaken to create a unique product, service, or result. Throughout a product's existence, multiple projects may be initiated. For example, an initial project creates the product, a subsequent project adds a major feature, and a final project manages its decommissioning. Each of these projects has its own lifecycle, all of which are contained within the single, overarching product lifecycle.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Project Management Institute

Inc. Section 2.2.4

Product Life Cycles

p. 46. The guide states

"Within a product life cycle

there are one or more project life cycles."

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Project Management Institute

Inc. Section 1.2.4.1

Project and Development Lifecycles

p. 19. Figure 1-5 illustrates the relationship

showing multiple projects occurring within the phases of a product lifecycle.

3. Shenhar

A. J.

& Dvir

D. (2007). Reinventing Project Management: The Diamond Approach to Successful Growth and Innovation. Harvard Business School Press. Chapter 2

"From the Iron Triangle to the Diamond

" discusses how projects are temporary efforts that create business value within the longer-term context of a product or business lifecycle.

A Pareto chart is a fundamental tool used in Project Quality Management. It is a type of bar chart that visually represents the frequency of defects or causes of problems in descending order of occurrence. Based on the Pareto principle (the 80/20 rule), it helps project teams identify the "vital few" causes that are responsible for the majority of issues. By prioritizing these significant few, teams can focus their corrective actions and improvement efforts more effectively, which is a core objective of quality control and quality assurance processes.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Newtown Square

PA: Project Management Institute. p. 305. In the "Control Quality" process

the Pareto chart is listed as a key data analysis technique used to "identify the vital few sources that are responsible for causing most of a problem’s effects."

2. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Newtown Square

PA: Project Management Institute. p. 158. The section on "Data and Analysis" describes the Pareto chart as a method used to display the causes of problems in a hierarchical format to help prioritize actions.

3. Heagney

J. (2016). Fundamentals of Project Management (5th ed.). AMACOM. p. 151. This text explicitly categorizes the Pareto chart as one of the "seven basic tools of quality" and explains its use for prioritizing problems within the quality management domain.

The process described is Perform Quality Assurance. This process involves auditing the quality requirements and the results from quality control measurements to ensure that the project utilizes appropriate quality standards and operational definitions. The core function of quality assurance is to analyze and evaluate the processes and systems that produce the deliverables, rather than the deliverables themselves. It is a process-oriented activity focused on continuous process improvement and confirming that quality activities comply with organizational policies, thereby increasing stakeholder confidence.

1. Project Management Institute. (2013). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (5th ed.). Project Management Institute.

Section 8.2

Page 242: "Perform Quality Assurance is the process of auditing the quality requirements and the results from quality control measurements to ensure that appropriate quality standards and operational definitions are used." This definition directly matches the question's wording.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Project Management Institute.

Section 8.2

Page 288: The process was renamed to "Manage Quality." Its purpose is described as translating the quality management plan into executable quality activities.

Section 8.2.2.3

Page 294: Under Tools and Techniques

"Audits" are defined as a "structured

independent process used to determine if project activities comply with organizational and project policies

processes

and procedures." This confirms the auditing function is central to this process.

The tools listed—Control charts, flowcharting, histograms, Pareto charts, and scatter diagrams—are primarily used for analyzing and controlling the quality of project outputs and processes. The Control Quality process specifically involves monitoring and recording the results of executing quality activities to assess performance and recommend necessary changes. Control charts are a key tool exclusive to this process for determining if a process is stable. Histograms, Pareto charts, and scatter diagrams are also used extensively in Control Quality to identify the causes of poor quality and analyze variance.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 8.3.2.5 Data Representation

pp. 305-306. The guide explicitly lists Control Charts

Histograms

and Scatter Diagrams as data representation tools for the Control Quality process.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 8.2.2.4 Data Representation

p. 294. This section lists Flowcharts

Histograms

and Scatter Diagrams as tools for the Manage Quality (Perform Quality Assurance) process

but notably omits Control Charts.

3. Kerzner

H. (2017). Project Management: A Systems Approach to Planning

Scheduling

and Controlling (12th ed.). John Wiley & Sons. Chapter 23

"Quality Management

" discusses the seven tools of quality control

noting that tools like control charts and Pareto diagrams are used for "controlling the process." This aligns with the Control Quality process.

Total float, also known as total slack, is a critical concept in project schedule network analysis. It represents the amount of time a specific schedule activity can be delayed from its early start date without delaying the overall project finish date or violating a schedule constraint. It is calculated as the difference between the late finish and early finish dates (LF - EF) or the late start and early start dates (LS - ES). Activities on the critical path have zero total float, meaning any delay in these activities will directly delay the project's completion.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Project Management Institute

Inc. Glossary

p. 242. "Float (Slack). The amount of time a schedule activity can be delayed or extended from its early start date without delaying the project finish date or violating a schedule constraint."

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Project Management Institute

Inc. Section 6.5.2.2

p. 210. "Total float is the amount of time that a schedule activity can be delayed or extended from its early start date without delaying the project finish date or violating a schedule constraint."

3. Vanhoucke

M. (2013). Project Management with Dynamic Scheduling: Baseline Scheduling

Risk Analysis and Project Control. Springer Berlin

Heidelberg. p. 23. https://doi.org/10.1007/978-3-642-40438-2. "The total float (TF) of an activity is the time span in which the completion of an activity may occur without delaying the total project."

Trend analysis is a data analysis technique used to examine project performance over time. It involves analyzing historical data to identify patterns or "trends," which helps project managers determine if performance is improving or deteriorating. By plotting data points such as cost variance (CV), schedule variance (SV), or defect counts over a timeline, a project manager can forecast future outcomes and take proactive corrective actions if the trend is unfavorable. This method is fundamental to the Monitor and Control Project Work process.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Project Management Institute

Inc. Section 4.2

"Data Analysis

" describes Trend Analysis as a technique used to examine project performance over time to see if it is improving or deteriorating.

2. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition. Project Management Institute

Inc. Section 4.5.2.2

"Data Analysis

" states

"Trend analysis is used to forecast future performance based on past results. It looks at project performance over time to determine if performance is improving or deteriorating."

3. Kerzner

H. (2017). Project Management: A Systems Approach to Planning

Scheduling

and Controlling (12th ed.). John Wiley & Sons. Chapter 13

"Project Control

" discusses trend analysis as a key controlling technique to monitor deviations from the plan over the project's life cycle. (Note: While a textbook

Kerzner is a foundational academic text in project management education and widely cited in peer-reviewed literature).

Risk appetite is the high-level, strategic degree of uncertainty an organization is willing to accept in pursuit of its objectives and in anticipation of a reward. It sets the overall tone for risk-taking within the entity. This concept addresses the fundamental question of how much risk is acceptable to achieve strategic goals. The question's phrasing, "degree of uncertainty an entity is willing to take on," directly corresponds to the official definition of risk appetite.

1. Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition. Project Management Institute

Inc.

Page 251

Glossary: Defines Risk Appetite as "The degree of uncertainty an organization or individual is willing to accept in anticipation of a reward."

Page 252

Glossary: Defines Risk Tolerance as "The specified range of acceptable variation an organization is willing to accept for a project or project objective."

2. Committee of Sponsoring Organizations of the Treadway Commission (COSO). (2017). Enterprise Risk Management—Integrating with Strategy and Performance.

Page 6

Executive Summary: Defines Risk Appetite as "The types and amount of risk

on a broad level

an organization is willing to accept in its pursuit of value." This foundational document in risk management reinforces the PMI definition.

Marketplace conditions and industry standards are beyond the organization’s control and thus fall under external EEFs. Policies and procedures are internal rules that shape organizational functioning, making them internal EEFs. Knowledge bases and lessons learned represent non-updated OPAs, as they are existing historical organizational process assets that guide current work. Resource skills and availability reflect updated capabilities and adjustments to assets, so they belong to updated OPAs. This classification aligns with PMI’s PMBOK® Guide framework for differentiating environmental factors from organizational process assets.

Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, Section 2.2.4 (Enterprise Environmental Factors), pp. 38–40.

Project Management Institute. PMBOK® Guide – Sixth Edition, Section 2.2.5 (Organizational Process Assets), pp. 41–43.

Crawford, L. H. (2005). Senior management perceptions of project management competence. International Journal of Project Management, 23(1), 7–16. https://doi.org/10.1016/j.ijproman.2004.06.005

MIT OpenCourseWare. Project Management (Course 15.965), Lecture on “Organizational Processes and Environmental Influences,” Massachusetts Institute of Technology, 2018.

Decision making is a structured technique used while developing the cost management plan, so it belongs to Plan Cost Management. The To-Complete Performance Index (TCPI) is an earned value management tool for forecasting cost efficiency, used under Control Costs. Meetings are necessary to align stakeholders, review funding limits, and finalize project budgets, thus applied in Determine Budget. Historical information review supports analogous estimating and other estimating methods, making it a key technique in Estimate Costs.

Project Management Institute (PMI). A Guide to the Project Management Body of Knowledge (PMBOK® Guide), 6th Edition.

Section 7.1.2.2 “Data Analysis – Decision Making” (p. 240) → Plan Cost Management.

Section 7.4.2.2 “Data Analysis – To-Complete Performance Index (TCPI)” (p. 263) → Control Costs.

Section 7.3.2.5 “Meetings” (p. 254) → Determine Budget.

Section 7.2.2.2 “Historical Information Review” (p. 246) → Estimate Costs.

Kerzner, H. Project Management: A Systems Approach to Planning, Scheduling, and Controlling, 12th Edition, Wiley.

Chapter 15, Cost Management Tools, confirms the mapping of TCPI to cost control (pp. 642–644).

Massachusetts Institute of Technology (MIT) OpenCourseWare – Project Management (Course 1.040/1.401).

Lecture on Cost Estimation and Budgeting: emphasizes historical data for estimates and decision-making frameworks in cost planning.

Stanford University – Civil and Environmental Engineering 268: Project Management.

Module “Cost Estimation and Control” → explains the linkage of meetings to budget approval and TCPI to control processes.