PMP Glossary

Key terms and acronyms for the PMP exam, explained in plain language.

By Abu Anns · Last updated 20 November 2026Exam version: July 2026 ECO (current since 9 July 2026)

Acceptance criteria
The conditions that a deliverable must meet to be formally accepted by the customer or sponsor.
Agile
An iterative, incremental approach to delivering work in short cycles, with frequent feedback and adaptation. About 60% of the current PMP exam reflects agile, adaptive, or hybrid approaches.
Baseline
The approved version of a plan (scope, schedule, or cost) against which performance is measured. Baselines change only through formal change control.
Benefits management plan
The document describing the expected benefits of a project, how they will be measured, who owns them, and when they are expected. Owned by the sponsor.
Burndown chart
An agile chart showing remaining work over time against an ideal line. A line above the ideal means the team is behind.
Business case
The documented justification for a project in financial and strategic terms — why this project, why now, and what return is expected. Owned by the sponsor.
Change control board (CCB)
The group (or person) with authority to approve or reject change requests, as defined in the change management plan.
Communication channels
The paths along which information flows between people. The number of channels for n people is n(n-1)/2.
Contingency reserve
Budget (or schedule allowance) held for known risks that may occur. It is part of the cost baseline and is managed by the project manager.
Cost performance index (CPI)
EV / AC. Above 1.0 means under budget; below 1.0 means over budget.
Crashing
A schedule compression technique that adds resources to critical path activities. It costs more money but does not add risk to the sequence of work.
Critical path
The longest sequence of activities through the project network. It determines the shortest possible project duration, and its activities have zero float.
Earned value (EV)
The budgeted cost of the work actually completed by a given point. One of the three core values in earned value management, with planned value (PV) and actual cost (AC).
Earned value management (EVM)
A method for measuring project performance by comparing planned value, earned value, and actual cost, and forecasting the final outcome.
Estimate at completion (EAC)
The forecast total cost of the project at completion. Calculated as AC + (BAC - EV), BAC / CPI, or AC + [(BAC - EV) / (CPI x SPI)], depending on the situation.
Expected monetary value (EMV)
Probability multiplied by impact in money terms. Used to quantify risks and to compare options in decision trees.
Fast tracking
A schedule compression technique that overlaps sequential activities on the critical path. It costs little but adds risk, because work starts before its predecessor is complete.
Float (slack)
The amount of time an activity can be delayed without delaying the project. Activities on the critical path have zero float.
Gold plating
Adding extra features that were not requested, because the team thinks the customer will like them. It consumes time and budget and is always wrong on the exam.
Governance
The framework of rules, roles, and decision-making processes that controls how a project is run: who decides what, and how the project is overseen.
Issue
A problem that has already occurred (or is currently occurring) and needs to be resolved. Tracked in the issue log. Distinct from a risk, which is a future uncertainty.
Issue log
The record of project issues, including each issue's owner, priority, status, and resolution.
Lessons learned register
The record of what went well, what went badly, and what the organization should do differently, captured throughout the project.
Management reserve
Budget held outside the cost baseline for unforeseen work. Controlled by the sponsor, not the project manager.
Minimum viable product (MVP)
The smallest version of a product that delivers enough value to be released and to generate learning from real users.
Monte Carlo simulation
A quantitative risk technique that runs thousands of random scenarios to produce a probability distribution of possible project outcomes.
PERT
Program Evaluation and Review Technique. Expected duration = (O + 4M + P) / 6; standard deviation = (P - O) / 6, where O, M, and P are the optimistic, most likely, and pessimistic estimates.
Phase gate
A decision point at the end of a project phase, where the governance body decides whether to continue, change, or stop the project.
Planned value (PV)
The budgeted cost of the work scheduled to be done by a given point. One of the three core values in earned value management.
Product backlog
The prioritized list of work for an agile product, owned by the product owner. Changes are managed by adding items to the backlog and prioritizing them.
Project charter
The document that formally authorizes the project and gives the project manager the authority to apply resources. Issued by the sponsor.
Project management plan
The integrated plan for the project, combining subsidiary plans (scope, schedule, cost, quality, resources, communications, risk, procurement, stakeholders) and the three baselines.
RACI chart
A responsibility assignment matrix showing who is Responsible, Accountable (exactly one person), Consulted, and Informed for each activity.
Risk
An uncertain event that, if it occurs, has a positive or negative effect on project objectives. Negative risks are threats; positive risks are opportunities.
Risk register
The record of identified risks, including each risk's cause, probability, impact, owner, and planned response.
Schedule performance index (SPI)
EV / PV. Above 1.0 means ahead of schedule; below 1.0 means behind schedule.
Scope creep
The uncontrolled expansion of project scope without changes to time, cost, or resources. Always a failure of scope management.
Servant leadership
A leadership style in which the leader serves the team — removing obstacles, coaching, and helping people grow — rather than commanding them. The leadership model the PMP exam rewards.
Sprint
A short, fixed-length iteration (typically 1-4 weeks) in Scrum, during which the team delivers a working increment of the product.
Stakeholder
Anyone who can affect, or is affected by, the project — including the sponsor, customer, team, users, regulators, and the wider organization.
To-complete performance index (TCPI)
(BAC - EV) / (BAC - AC). The efficiency the remaining work must achieve to finish on budget. Above 1.0 means the team must perform better than planned.
Work breakdown structure (WBS)
A hierarchical, deliverable-oriented decomposition of the total project scope into work packages. It follows the 100% rule: it covers all of the scope, nothing more and nothing less.
Work package
The lowest level of the work breakdown structure, where work can be reliably estimated, assigned, and controlled.
Advertisement