These are original plain-language study explanations. Consult the official glossary in your licensed copy for PMI’s authoritative wording.
Acceptance criteria
Conditions a deliverable must satisfy before an authorized party accepts it.
Plain language: The agreed tests for saying a result is acceptable.
Example: A portal must pass accessibility checks and process a test application without data loss.
Related terms: Definition of done · Validation · Scope baseline
Study in: Introduction · Project Management Principles · Project Life Cycles · Scope Performance Domain · Stakeholders Performance Domain · Tools and Techniques · Procurement
Accountability
The obligation to own decisions, actions, consequences, and corrective follow-through.
Plain language: Being answerable for what you decide and do.
Example: The sponsor records the funding decision and follows up when its assumptions fail.
Related terms: Governance · Leadership · Decision rights
Study in: Introduction · A System for Value Delivery · Project Management Principles · Introduction · Governance Performance Domain · Finance Performance Domain · Resources Performance Domain · Tailoring · Project Management Offices · Artificial Intelligence
Adaptive approach
A delivery approach that uses short learning cycles and reprioritization when needs or solutions are uncertain.
Plain language: Build, learn, and adjust in small steps.
Example: A service team releases a small workflow, studies user behavior, and reshapes the backlog.
Related terms: Iteration · Increment · Backlog · Predictive approach
Study in: Project Life Cycles · Introduction · Tailoring
AI
Technology that performs or supports tasks such as prediction, generation, classification, or pattern recognition.
Plain language: Software that can assist with work requiring learned patterns.
Example: A model flags likely schedule slippage, but a manager validates the data before acting.
Related terms: Automation · Human oversight · Data quality
Study in: A System for Value Delivery · Project Management Principles · Governance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Tools and Techniques · Artificial Intelligence
Analogous estimating
An estimating method that starts from comparable past work and adjusts for relevant differences.
Plain language: Estimate this job by carefully comparing it with a similar one.
Example: A team adjusts the duration of a prior clinic rollout for twice as many sites.
Related terms: Parametric estimating · Three-point estimating · Estimate
Study in: Tools and Techniques
Artifact
A document, model, record, or other item created to support project work and communication.
Plain language: A useful project work product, not necessarily the final deliverable.
Example: The team maintains a decision log to show why a design option was chosen.
Related terms: Deliverable · Output · Register
Study in: Introduction · Introduction · Stakeholders Performance Domain · Inputs and Outputs · Evolution of the PMBOK Guide
Assumption
A planning belief treated as true until evidence confirms or disproves it.
Plain language: Something the plan currently relies on without certainty.
Example: The schedule assumes a security reviewer will be available in June.
Related terms: Constraint · Risk · Assumption log
Study in: A System for Value Delivery · Project Management Principles · Governance Performance Domain · Stakeholders Performance Domain · Risk Performance Domain
Assumption log
A living record of planning assumptions, constraints, owners, and validation status.
Plain language: The list of what the plan is counting on and how it will be checked.
Example: The manager records the assumed permit turnaround and assigns someone to verify it.
Related terms: Assumption · Constraint · Risk register
Study in: Governance Performance Domain · Risk Performance Domain
Assurance
Independent or objective confidence-building work that evaluates whether governance and controls are adequate.
Plain language: A separate check that the project is being directed and controlled properly.
Example: An assurance reviewer tests whether privacy risks are being escalated as required.
Related terms: Control · Audit · Governance
Study in: Project Management Principles · Introduction · Governance Performance Domain · Scope Performance Domain · Stakeholders Performance Domain · Tailoring · Project Management Offices
Audit
A structured, evidence-based examination of compliance, process effectiveness, or records.
Plain language: A formal check against stated rules or expectations.
Example: A procurement audit samples approvals and verifies that selection criteria were applied.
Related terms: Assurance · Compliance · Quality
Study in: Project Life Cycles · Governance Performance Domain · Risk Performance Domain · Tailoring · Artificial Intelligence · Procurement
Automation
Use of technology to execute repeatable work with limited human intervention.
Plain language: Letting a system perform a bounded routine task.
Example: A workflow automatically routes approved invoices while exceptions go to a reviewer.
Related terms: AI · Human oversight · Workflow
Study in: A System for Value Delivery · Project Life Cycles · Scope Performance Domain · Resources Performance Domain · Artificial Intelligence
Backlog
An ordered, revisable list of work items that may be selected for future delivery.
Plain language: The ranked queue of work still under consideration.
Example: After a pilot, the product owner moves an accessibility fix above a cosmetic feature.
Related terms: Adaptive approach · Prioritization · Work breakdown structure
Study in: Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Risk Performance Domain · Tools and Techniques
Baseline
An approved reference used to compare actual or forecast performance and control change.
Plain language: The agreed version used as the comparison point.
Example: The board compares the revised completion forecast with the approved schedule baseline.
Related terms: Change control · Forecast · Variance
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Resources Performance Domain · Inputs and Outputs · Tools and Techniques · Project Management Offices
Benefit
A favorable effect produced when an output is adopted or used successfully.
Plain language: A useful gain created by the project result.
Example: Shorter patient waiting time is a benefit of a well-adopted scheduling service.
Related terms: Outcome · Value · Disbenefit
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Project Management Offices
Benefit realization
The coordinated work of assigning, enabling, measuring, and sustaining intended benefits.
Plain language: Making sure promised gains actually happen and last.
Example: Operations owns adoption metrics for six months after the project hands over the service.
Related terms: Benefit · Benefits management plan · Outcome
Study in: A System for Value Delivery · Stakeholders Performance Domain
Benefits management plan
The plan that identifies intended benefits, measures, timing, dependencies, and accountable owners.
Plain language: The plan for making promised gains happen and checking them.
Example: The plan names the clinic director as owner of the no-show reduction target.
Related terms: Benefit realization · Benefit · Business case
Study in: Governance Performance Domain · Finance Performance Domain · Inputs and Outputs
Bottom-up estimating
An estimating method that develops detailed component estimates and combines them into a total.
Plain language: Estimate the pieces first, then add them up.
Example: Trade leads estimate each work package before the scheduler rolls them into the project duration.
Related terms: Estimate · Work package · Analogous estimating
Study in: Tools and Techniques
Budget
The authorized funding plan against which project costs are managed.
Plain language: The approved money available for the work.
Example: The steering group approves a budget that includes implementation and contingency funding.
Related terms: Cost baseline · Funding · Forecast
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Resources Performance Domain · Risk Performance Domain · Inputs and Outputs · Procurement
Business acumen
The ability to connect project choices with strategy, operations, finance, customers, and the operating environment.
Plain language: Understanding how the organization works well enough to make sound project choices.
Example: A manager recognizes that a cheap component would increase long-term maintenance cost.
Related terms: Strategy · Value · Competence
Study in: A System for Value Delivery
Business case
The decision rationale that compares a proposed investment with expected value, cost, risk, and alternatives.
Plain language: Why the initiative is worth doing.
Example: A transit business case links mobile ticketing costs to adoption and boarding-time benefits.
Related terms: Value proposition · Benefit · Investment
Study in: Project Management Principles · Governance Performance Domain · Scope Performance Domain · Finance Performance Domain · Inputs and Outputs · Procurement
Cadence
The regular timing pattern for delivery, review, planning, or feedback events.
Plain language: How often meaningful work or information arrives.
Example: The team demonstrates a usable increment every two weeks and reviews risks monthly.
Related terms: Iteration · Feedback · Release
Study in: A System for Value Delivery · Project Life Cycles · Introduction · Governance Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs
Change control
The governed process for evaluating, deciding, recording, and communicating proposed changes.
Plain language: The route for deciding whether an approved plan should change.
Example: A requested capacity increase is assessed for cost and schedule impact before approval.
Related terms: Change request · Baseline · Configuration management
Study in: Governance Performance Domain · Schedule Performance Domain · Finance Performance Domain · Inputs and Outputs
Change log
A record of proposed changes and their analysis, decisions, status, and implementation.
Plain language: The history of requested changes and what happened to them.
Example: The log shows that a design revision was approved with extra testing.
Related terms: Change request · Decision log · Change control
Study in: Governance Performance Domain · Scope Performance Domain · Stakeholders Performance Domain · Inputs and Outputs · Procurement
Change request
A documented proposal to alter a controlled deliverable, plan, baseline, or project component.
Plain language: A formal request to change something under control.
Example: The vendor submits a request to replace the specified sensor with a new model.
Related terms: Change control · Change log · Baseline
Study in: Scope Performance Domain · Schedule Performance Domain · Stakeholders Performance Domain · Inputs and Outputs
Closing
The deliberate completion of a project or phase, including acceptance, transition, records, and unresolved matters.
Plain language: Finishing responsibly rather than simply stopping work.
Example: Before closure, the team transfers support ownership and archives the final decision records.
Related terms: Handover · Acceptance · Lessons learned
Study in: A System for Value Delivery · Project Life Cycles · Governance Performance Domain · Inputs and Outputs · Procurement · Evolution of the PMBOK Guide
Communications management plan
The plan for what project information will be shared, with whom, when, how, and by whom.
Plain language: The rules for getting the right information to the right people.
Example: The plan gives regulators monthly evidence packs and crews daily safety updates.
Related terms: Communications planning · Stakeholder engagement · Project management plan
Study in: Stakeholders Performance Domain
Communications planning
The design of information flows to meet stakeholder decisions, understanding, and feedback needs.
Plain language: Planning who needs which message and when.
Example: Residents receive closure notices before construction while executives receive exception reports.
Related terms: Communications management plan · Feedback · Stakeholder analysis
Study in: Stakeholders Performance Domain
Compliance
Conformance with applicable laws, regulations, standards, contracts, and organizational obligations.
Plain language: Following the rules the project cannot legitimately ignore.
Example: The design is reviewed against accessibility law before procurement begins.
Related terms: Governance · Audit · Constraint
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Finance Performance Domain · Resources Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Project Management Offices · Procurement · Evolution of the PMBOK Guide
Configuration control
The discipline of maintaining the integrity of controlled items through identified versions and authorized changes.
Plain language: Keeping controlled versions consistent and traceable.
Example: The team links each released specification to its approved change history.
Related terms: Change control · Version control · Baseline
Study in: Governance Performance Domain
Constraint
A condition that limits the project's choices, such as a deadline, budget, law, or scarce resource.
Plain language: A boundary the team must work within.
Example: A fixed school opening date limits the available commissioning window.
Related terms: Assumption · Risk · Trade-off
Study in: Schedule Performance Domain · Resources Performance Domain · Risk Performance Domain · Tools and Techniques
Contingency reserve
Time or money set aside within the baseline for identified uncertainty and planned responses.
Plain language: Allowance for known risks that may occur.
Example: The budget includes funds for the documented risk of extra soil treatment.
Related terms: Management reserve · Risk response · Cost baseline
Study in: Finance Performance Domain · Risk Performance Domain
Contract
A binding agreement that defines exchanged obligations, terms, remedies, and allocation of risk.
Plain language: The enforceable deal between buyer and seller.
Example: The contract ties payment to accepted equipment and stated service levels.
Related terms: Procurement · Contract type · Claim
Study in: Project Management Principles · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Finance Performance Domain · Tailoring · Project Management Offices · Procurement · Evolution of the PMBOK Guide
Contract type
The commercial structure that assigns cost, performance, and uncertainty exposure between parties.
Plain language: How the deal divides financial risk and incentives.
Example: A fixed-price arrangement places more cost overrun exposure on the seller when scope is stable.
Related terms: Contract · Fixed-price contract · Cost-reimbursable contract
Study in: Procurement
Control
Action that compares evidence with expectations and directs correction when needed.
Plain language: Checking performance and acting on meaningful differences.
Example: The manager investigates a growing defect trend and changes the test workflow.
Related terms: Monitoring · Variance · Corrective action
Study in: A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Tools and Techniques · Project Management Offices · Artificial Intelligence · Procurement · Evolution of the PMBOK Guide
Corrective action
A directed change intended to bring future performance back toward an approved expectation.
Plain language: An action taken to fix a performance deviation.
Example: The team adds a second review step after repeated drawing errors.
Related terms: Preventive action · Control · Variance
Study in: Project Management Principles · Project Life Cycles · Governance Performance Domain · Finance Performance Domain · Resources Performance Domain
Cost baseline
The time-phased approved cost reference used for performance comparison, excluding management reserve.
Plain language: The approved spending plan over time.
Example: Monthly actual cost is compared with the authorized cost baseline.
Related terms: Budget · Baseline · Contingency reserve
Study in: Finance Performance Domain · Resources Performance Domain · Inputs and Outputs
Cost estimate
A reasoned approximation of the resources and money needed to complete work.
Plain language: The best supported prediction of what the work will cost.
Example: The estimator combines labor hours, supplier quotes, and uncertainty ranges.
Related terms: Estimate · Budget · Basis of estimates
Study in: Finance Performance Domain
Cost of quality
The combined cost of preventing, assessing, and dealing with failures in quality.
Plain language: What the project spends to get quality and what poor quality costs.
Example: Early prototype testing costs less than repairing hundreds of installed units.
Related terms: Quality · Prevention · Rework
Study in: Finance Performance Domain
Crashing
Schedule compression by adding resources or cost to shorten selected activities where feasible.
Plain language: Spend more or add capacity to finish critical work sooner.
Example: A second qualified crew is added to a critical installation activity.
Related terms: Fast tracking · Critical path · Schedule compression
Study in: Schedule Performance Domain · Tools and Techniques
Critical path
The sequence of activities that determines the earliest project finish under the current schedule model.
Plain language: The chain of work currently controlling the finish date.
Example: A delay in final inspection moves the project end because that activity has no usable float.
Related terms: Float · Dependency · Network diagram
Study in: Schedule Performance Domain · Tools and Techniques
Data quality
The degree to which data is accurate, complete, timely, relevant, and fit for its intended decision.
Plain language: Whether the information is good enough to trust for this use.
Example: The team checks missing and outdated records before using an AI forecast.
Related terms: AI · Measurement · Human oversight
Study in: A System for Value Delivery · Finance Performance Domain · Risk Performance Domain · Tools and Techniques · Artificial Intelligence
Decision log
A record of significant decisions, their owners, dates, rationale, and consequences.
Plain language: A trace of what was decided and why.
Example: The log explains why the team selected phased rollout over a big-bang launch.
Related terms: Change log · Artifact · Governance
Study in: Introduction
Decision rights
Explicit authority boundaries that state who may decide, approve, recommend, or escalate particular matters.
Plain language: Clarity about who gets to make which call.
Example: The product owner may reorder features, but only the sponsor may increase funding.
Related terms: Governance · Accountability · Escalation
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Governance Performance Domain · Tailoring
Decomposition
The progressive division of a large deliverable or body of work into manageable components.
Plain language: Breaking big work into useful smaller pieces.
Example: A building handover is divided into systems, areas, and testable work packages.
Related terms: Work breakdown structure · Work package · Scope
Study in: Scope Performance Domain · Schedule Performance Domain · Inputs and Outputs · Tools and Techniques
Definition of done
A shared quality threshold that a work item must meet to be considered complete by the team.
Plain language: The team's common checklist for truly finishing an item.
Example: A feature is done only after review, automated tests, documentation, and integration.
Related terms: Acceptance criteria · Quality · Increment
Study in: Project Management Principles · Scope Performance Domain
Deliverable
A verifiable product, service, result, or capability produced for the project.
Plain language: A concrete result the project is expected to provide.
Example: The approved emergency response procedure is a project deliverable.
Related terms: Output · Acceptance · Artifact
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Inputs and Outputs
Dependency
A relationship in which one activity, decision, or result relies on another.
Plain language: One piece cannot proceed or succeed independently of another.
Example: Training cannot start until the stable interface is available.
Related terms: Critical path · Network diagram · Lead and lag
Study in: A System for Value Delivery · Project Management Principles · Schedule Performance Domain · Inputs and Outputs · Tools and Techniques · Project Management Offices
Disbenefit
A negative consequence created by an output or the change surrounding it.
Plain language: A harmful effect of the project result.
Example: A faster road layout creates more noise for nearby residents.
Related terms: Benefit · Outcome · Externality
Study in: Introduction
Earned value
The budgeted value assigned to work actually completed at a stated point in time.
Plain language: The planned-budget value of the work finished so far.
Example: Completed foundation work represents $80,000 of earned value even though $90,000 was spent.
Related terms: Planned value · Actual cost · Performance measurement baseline
Study in: Schedule Performance Domain · Finance Performance Domain · Tools and Techniques
Engagement
Purposeful interaction that builds understanding, participation, influence, and commitment with stakeholders.
Plain language: Working with people, not merely sending them updates.
Example: Nurses test the workflow and help decide how it should fit daily practice.
Related terms: Stakeholder engagement · Feedback · Communications planning
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Tailoring · Tools and Techniques · Artificial Intelligence · Evolution of the PMBOK Guide
Enterprise environmental factors
Conditions outside the project team's direct control that enable, constrain, or influence the work.
Plain language: The surrounding realities the team must account for.
Example: Privacy law and limited specialist availability shape the delivery approach.
Related terms: Organizational process assets · Constraint · Project environment
Study in: A System for Value Delivery
Escalation
Referral of an issue or decision beyond current authority or capability to an appropriate higher level.
Plain language: Moving a decision to someone empowered to resolve it.
Example: The manager escalates a cross-program resource conflict to the portfolio board.
Related terms: Decision rights · Issue · Governance
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Governance Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Tailoring · Tools and Techniques · Artificial Intelligence · Procurement
Estimate
A quantified approximation based on available evidence, assumptions, and uncertainty.
Plain language: A supported prediction, not a promise.
Example: The team estimates installation at ten to fourteen days and records the drivers of the range.
Related terms: Forecast · Basis of estimates · Uncertainty
Study in: A System for Value Delivery · Schedule Performance Domain · Finance Performance Domain · Resources Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Tools and Techniques
Fast tracking
Schedule compression by overlapping work that was originally planned in sequence, increasing coordination and rework risk.
Plain language: Start later work early and accept more overlap risk.
Example: Training materials are drafted before the interface design is fully finalized.
Related terms: Crashing · Schedule compression · Dependency
Study in: Schedule Performance Domain
Feedback
Information about needs, performance, effects, or experience that can inform a decision or adaptation.
Plain language: Evidence returned to help the team improve its next choice.
Example: Pilot users report that appointment reminders matter more than a dashboard.
Related terms: Cadence · Learning · Stakeholder engagement
Study in: A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Tailoring · Inputs and Outputs · Tools and Techniques · Project Management Offices · Evolution of the PMBOK Guide
Fixed-price contract
A contract with an agreed price for defined work, placing greater cost risk on the seller when requirements are stable.
Plain language: The seller commits to deliver defined work for a set price.
Example: A supplier provides standard equipment for a fixed amount and delivery date.
Related terms: Contract type · Cost-reimbursable contract · Procurement
Study in: Procurement
Float
The scheduling flexibility available before an activity delays a linked milestone or project finish.
Plain language: How long work can move without causing a specified delay.
Example: A review has three days of float before it affects commissioning.
Related terms: Critical path · Schedule · Dependency
Study in: Schedule Performance Domain
Forecast
A current prediction of future performance based on actual results, trends, risks, and remaining work.
Plain language: Where the project now appears to be heading.
Example: After supplier delay, the team forecasts completion two weeks beyond the baseline.
Related terms: Estimate · Baseline · Variance
Study in: Governance Performance Domain · Schedule Performance Domain · Finance Performance Domain · Resources Performance Domain · Risk Performance Domain · Inputs and Outputs · Tools and Techniques · Artificial Intelligence · Procurement
Funding
Money made available in authorized amounts and at times needed to support project work.
Plain language: When approved money is actually available to spend.
Example: The portfolio releases construction funds only after the design gate is passed.
Related terms: Budget · Finance · Governance
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Risk Performance Domain · Inputs and Outputs · Tools and Techniques · Project Management Offices
Governance
The framework of authority, oversight, accountability, controls, and escalation used to direct a project.
Plain language: How important project decisions are made and checked.
Example: A steering group sets thresholds for scope and budget decisions.
Related terms: Decision rights · Assurance · Oversight
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Project Management Offices · Artificial Intelligence · Evolution of the PMBOK Guide
Handover
The controlled transfer of a deliverable, knowledge, ownership, and support responsibility to its receiving party.
Plain language: Passing the result to those who will operate or own it.
Example: Operations accepts the service only after training, support access, and documentation are ready.
Related terms: Transition · Operational readiness · Closing
Study in: Introduction · A System for Value Delivery · Project Life Cycles · Governance Performance Domain · Inputs and Outputs
Human oversight
Accountable human review of automated or AI-supported outputs, assumptions, limits, and consequences.
Plain language: A responsible person checks and owns technology-assisted decisions.
Example: A planner investigates an AI risk alert instead of automatically rebaselining.
Related terms: AI · Automation · Data quality
Study in: A System for Value Delivery · Artificial Intelligence
Hybrid approach
A delivery approach that intentionally combines predictive and adaptive practices for different parts of the work.
Plain language: Use plan-driven and learning-driven methods where each fits.
Example: Civil works follow approved drawings while the user interface evolves through short iterations.
Related terms: Adaptive approach · Predictive approach · Tailoring
Study in: Tailoring
Increment
A usable addition to a product or result that builds on what already exists.
Plain language: A working slice added to the solution.
Example: The first increment lets residents submit a basic permit application online.
Related terms: Iteration · Release · Adaptive approach
Study in: Project Life Cycles
Influence
The ability to affect choices, behavior, or outcomes without relying only on formal authority.
Plain language: Helping shape a decision even when you are not the approver.
Example: A safety specialist changes the design by presenting clear consequence evidence.
Related terms: Power skills · Stakeholder · Leadership
Study in: A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Tools and Techniques · Project Management Offices
Issue
A current condition or event that requires attention because it is already affecting or could immediately affect the project.
Plain language: A problem or decision need that exists now.
Example: The promised test environment is unavailable, so the team logs and assigns the issue.
Related terms: Risk · Issue log · Escalation
Study in: Introduction · A System for Value Delivery · Project Management Principles · Governance Performance Domain · Scope Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Procurement
Issue log
A living record of issues, owners, priorities, decisions, actions, and status.
Plain language: The tracked list of current problems needing resolution.
Example: The log assigns the missing permit evidence to the compliance lead with a due date.
Related terms: Issue · Action item · Register
Study in: Governance Performance Domain · Scope Performance Domain · Stakeholders Performance Domain · Risk Performance Domain · Inputs and Outputs
Iteration
A bounded cycle in which a team selects work, produces results, obtains feedback, and learns.
Plain language: A short repeatable loop for making and improving something.
Example: During a two-week iteration, the team tests a new booking flow with users.
Related terms: Increment · Cadence · Adaptive approach
Study in: A System for Value Delivery · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Stakeholders Performance Domain · Risk Performance Domain
Knowledge repositories
Organized stores of reusable project records, lessons, metrics, and contextual information.
Plain language: Places where teams can find useful experience from earlier work.
Example: The estimator checks prior permit delays and the reasons behind them.
Related terms: Lessons learned · Organizational process assets · Historical information
Study in: A System for Value Delivery
Lagging indicator
A measure that confirms results after performance or outcomes have occurred.
Plain language: Evidence that tells you what already happened.
Example: Actual defect escape rate shows the quality achieved after release.
Related terms: Leading indicator · Key performance indicator · Measurement
Study in: Governance Performance Domain
Leadership
Behavior that creates direction, commitment, ethical ownership, and coordinated action.
Plain language: Helping people move responsibly toward a shared objective.
Example: A team member surfaces a safety concern and organizes the right experts to resolve it.
Related terms: Accountability · Team leadership · Influence
Study in: A System for Value Delivery · Project Management Principles · Resources Performance Domain · Evolution of the PMBOK Guide
Leading indicator
A measure that signals conditions likely to influence future performance or outcomes.
Plain language: An early warning or predictor.
Example: Falling prototype-test participation warns that adoption may later be weak.
Related terms: Lagging indicator · Key performance indicator · Forecast
Study in: Governance Performance Domain
Lessons learned
Validated knowledge captured from experience to improve current or future decisions.
Plain language: What the team discovered and can reuse.
Example: The team records why a permit estimate failed, not just that it was late.
Related terms: Knowledge repository · Retrospective · Organizational process assets
Study in: A System for Value Delivery · Governance Performance Domain · Scope Performance Domain · Risk Performance Domain · Inputs and Outputs
Life cycle
The ordered set of phases through which a project progresses from authorization to completion.
Plain language: The broad stages the project passes through.
Example: A facility project moves through concept, design, construction, commissioning, and closeout.
Related terms: Phase · Phase gate · Development approach
Study in: A System for Value Delivery · Project Management Principles · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Tailoring · Inputs and Outputs · Procurement · Evolution of the PMBOK Guide
Make-or-buy analysis
Evaluation of whether work should be performed internally or obtained from an external source.
Plain language: Deciding whether to build it yourself or purchase it.
Example: The agency compares internal capability, time, risk, and total ownership cost before outsourcing support.
Related terms: Procurement · Sourcing · Market analysis
Study in: Finance Performance Domain · Procurement
Management reserve
Budget or time held outside the performance baseline for unforeseen work within project scope.
Plain language: An allowance for uncertainty that was not specifically identified.
Example: The sponsor authorizes management reserve after an unexpected regulatory interpretation adds work.
Related terms: Contingency reserve · Budget · Uncertainty
Study in: Finance Performance Domain · Risk Performance Domain · Inputs and Outputs
Milestone
A significant zero-duration point marking an event, decision, achievement, or boundary in the schedule.
Plain language: An important scheduled checkpoint.
Example: Regulatory approval is a milestone that permits site work to begin.
Related terms: Schedule · Phase gate · Dependency
Study in: A System for Value Delivery · Project Management Principles · Schedule Performance Domain · Risk Performance Domain · Inputs and Outputs · Procurement
Monitoring
Ongoing collection and interpretation of evidence to understand performance, change, and emerging conditions.
Plain language: Watching the right signals and making sense of them.
Example: The team monitors defect trends and supplier lead times each week.
Related terms: Control · Measurement · Forecast
Study in: Introduction · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Risk Performance Domain · Tools and Techniques · Artificial Intelligence · Procurement · Evolution of the PMBOK Guide
Multipoint estimating
An estimating method that uses several plausible values to represent uncertainty rather than relying on one prediction.
Plain language: Estimate with a realistic range of cases instead of one number.
Example: A task is assessed at five, eight, and fourteen days before calculating a planning estimate.
Related terms: Estimate · Analogous estimating · Uncertainty
Study in: Schedule Performance Domain · Finance Performance Domain
Network diagram
A visual model of schedule activities and the dependencies that connect them.
Plain language: A map showing the order and relationships of scheduled work.
Example: The diagram shows that testing depends on both installation and data migration.
Related terms: Dependency · Critical path · Schedule model
Study in: Schedule Performance Domain
Opportunity
An uncertain event or condition that could improve project objectives or value if it occurs.
Plain language: A possible upside worth managing.
Example: A new shared platform may cut both cost and deployment time.
Related terms: Threat · Risk · Risk response
Study in: Project Management Principles · Project Life Cycles · Risk Performance Domain
Organizational process assets
Internal policies, procedures, templates, records, and knowledge that a project can use and improve.
Plain language: Reusable organizational know-how and guidance.
Example: The team adapts a prior commissioning checklist for new equipment.
Related terms: Enterprise environmental factors · Knowledge repository · Tailoring
Study in: A System for Value Delivery · Inputs and Outputs
Outcome
A consequence that occurs when project outputs are used or when change takes effect.
Plain language: What happens because people use the result.
Example: Residents complete permit applications faster after adopting the portal.
Related terms: Output · Benefit · Value
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Tools and Techniques · Project Management Offices · Procurement · Evolution of the PMBOK Guide
Output
A product, service, result, or intermediate item produced by project activity.
Plain language: What the work directly produces.
Example: The installed scheduling system is an output; shorter waits are a later outcome.
Related terms: Deliverable · Outcome · Artifact
Study in: Introduction · A System for Value Delivery · Project Management Principles · Introduction · Governance Performance Domain · Scope Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Inputs and Outputs · Tools and Techniques · Artificial Intelligence
Oversight
Review and direction that keep work aligned with objectives, obligations, and authorized boundaries.
Plain language: The checks that keep the project responsibly on course.
Example: The committee reviews exception evidence rather than supervising every task.
Related terms: Governance · Assurance · Control
Study in: Introduction · A System for Value Delivery · Project Life Cycles · Governance Performance Domain · Tailoring · Artificial Intelligence
Parametric
An estimating method that applies a validated relationship between measurable units and cost or duration.
Plain language: Estimate by multiplying a reliable rate by the amount of work.
Example: A paving estimate uses cost per square meter adjusted for site conditions.
Related terms: Analogous estimating · Estimate · Multipoint estimating
Study in: Schedule Performance Domain · Finance Performance Domain · Resources Performance Domain · Tools and Techniques
Performance measurement baseline
The integrated approved scope, schedule, and cost reference used to assess execution performance.
Plain language: The combined plan used to measure how delivery is performing.
Example: The controller compares earned value and actual cost with the approved integrated baseline.
Related terms: Earned value · Cost baseline · Schedule baseline
Study in: Inputs and Outputs
Phase
A related group of project activities organized to improve management, learning, or control.
Plain language: A meaningful stage of the project.
Example: The design phase ends when approved documents are ready for procurement.
Related terms: Life cycle · Phase gate · Closing
Study in: Introduction · Project Life Cycles · Governance Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Procurement · Evolution of the PMBOK Guide
Phase gate
A decision point at a phase boundary where evidence supports continuation, change, pause, or termination.
Plain language: A checkpoint for deciding whether the project should move forward.
Example: The board authorizes construction only after design and funding evidence are complete.
Related terms: Phase · Governance · Decision rights
Study in: Project Life Cycles
Planned value
The authorized budget assigned to work scheduled for completion by a stated date.
Plain language: The budgeted value of work that should be done by now.
Example: By month three, the baseline shows $120,000 of planned value.
Related terms: Earned value · Actual cost · Performance measurement baseline
Study in: Schedule Performance Domain · Tools and Techniques
Portfolio
A managed collection of investments selected and balanced to advance strategic objectives.
Plain language: The organization's group of chosen investments.
Example: A safety portfolio funds the combination of initiatives that best reduces transport harm.
Related terms: Program · Project · Strategy
Study in: Introduction · A System for Value Delivery · Project Management Principles · Governance Performance Domain · Tailoring · Project Management Offices · Artificial Intelligence
Power skills
Interpersonal capabilities used to lead, communicate, negotiate, collaborate, and navigate conflict.
Plain language: The people skills that make technical project work effective.
Example: The manager resolves a resource conflict through listening, negotiation, and a clear decision.
Related terms: Leadership · Influence · Competence
Study in: A System for Value Delivery
Predictive approach
A delivery approach that plans scope and major work in advance when requirements and methods are sufficiently stable.
Plain language: Plan most of the work first, then execute against that plan.
Example: A standard warehouse build follows approved design packages and a sequenced construction schedule.
Related terms: Adaptive approach · Hybrid approach · Baseline
Study in: Project Life Cycles
Prioritization
Deliberate ordering of work or decisions using value, urgency, risk, dependency, and feasibility.
Plain language: Choosing what deserves attention first.
Example: The team moves a safety fix ahead of a low-value interface enhancement.
Related terms: Backlog · Value · Trade-off
Study in: Introduction · A System for Value Delivery · Project Management Principles · Governance Performance Domain · Scope Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Risk Performance Domain · Artificial Intelligence
Procurement
The coordinated work of obtaining products, services, or results from outside the performing organization.
Plain language: Buying or contracting for external help or supply.
Example: The agency sources specialist testing that it cannot perform internally.
Related terms: Contract · Sourcing · Make-or-buy analysis
Study in: A System for Value Delivery · Project Management Principles · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Finance Performance Domain · Resources Performance Domain · Risk Performance Domain · Inputs and Outputs · Tools and Techniques · Artificial Intelligence · Procurement
Product life cycle
The span of a product from concept and introduction through growth, operation, evolution, and retirement.
Plain language: The whole useful life of a product, often longer than any one project.
Example: Several projects enhance a transit app before the product is eventually retired.
Related terms: Life cycle · Product management · Project
Study in: A System for Value Delivery · Project Life Cycles
Product management
Ongoing coordination of product vision, priorities, evidence, and evolution across its useful life.
Plain language: Guiding a product beyond the boundaries of one project.
Example: The product team uses rider data to prioritize improvements after launch.
Related terms: Product life cycle · Product owner · Roadmap
Study in: A System for Value Delivery
Product owner
A role accountable for ordering product work and clarifying value priorities within defined authority.
Plain language: The person who decides what product work matters next.
Example: The product owner ranks an accessibility improvement above a reporting feature.
Related terms: Backlog · Prioritization · Sponsor
Study in: A System for Value Delivery · Project Life Cycles
Product scope
The features, functions, performance, and quality characteristics of the result being created.
Plain language: What the finished product itself must be and do.
Example: The product scope requires the portal to support accessible appointment booking and secure records.
Related terms: Project scope · Requirements · Scope
Study in: Scope Performance Domain
Program
A coordinated group of related work managed together to gain benefits not available through separate management.
Plain language: Related initiatives managed as a connected whole.
Example: A rider-access program coordinates mobile ticketing, station upgrades, and public education.
Related terms: Portfolio · Project · Benefits realization
Study in: Introduction · A System for Value Delivery · Project Management Principles · Governance Performance Domain · Schedule Performance Domain · Tailoring
Progressive elaboration
Increasing the detail and accuracy of plans as information and certainty improve.
Plain language: Plan more precisely as you learn more.
Example: Early estimates use ranges; later plans use supplier quotes and completed design details.
Related terms: Rolling-wave planning · Estimate · Uncertainty
Study in: Project Life Cycles · Schedule Performance Domain
Project
A temporary initiative undertaken in a distinct context to create change and intended value.
Plain language: Time-bounded work that creates a particular result or change.
Example: A hospital runs a project to replace its appointment system and transition support to operations.
Related terms: Program · Portfolio · Operations
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Tools and Techniques · Project Management Offices · Artificial Intelligence · Procurement · Evolution of the PMBOK Guide
Project charter
The authorization that establishes the project's purpose, high-level boundaries, key authority, and sponsor commitment.
Plain language: The document that formally starts and frames the project.
Example: The charter names the sponsor, intended outcome, major risks, and manager's authority.
Related terms: Business case · Governance · Project management plan
Study in: Governance Performance Domain
Project environment
The internal and external conditions, relationships, and systems that shape project choices.
Plain language: The setting in which the project has to work.
Example: Culture, regulation, infrastructure, and market volatility affect the rollout strategy.
Related terms: Enterprise environmental factors · Organizational process assets · Tailoring
Study in: A System for Value Delivery · Schedule Performance Domain · Stakeholders Performance Domain
Project governance
Governance tailored to a specific initiative, including decision authority, oversight, escalation, and controls.
Plain language: The project's own decision and accountability framework.
Example: The governance map states which changes the team, sponsor, and board may approve.
Related terms: Governance · Organizational governance · Decision rights
Study in: Introduction · A System for Value Delivery
Project management office
An organizational function that supports, governs, coordinates, or directly manages projects according to its mandate.
Plain language: A group that helps the organization manage projects consistently and usefully.
Example: A supportive PMO provides templates and coaching while a directive PMO assigns project managers.
Related terms: Governance · Portfolio · Organizational process assets
Study in: Governance Performance Domain
Project management plan
The integrated set of approved approaches and subsidiary plans used to execute, monitor, control, and close the project.
Plain language: The main guide for how the project will be managed.
Example: The plan integrates scope, schedule, cost, risk, quality, and communication arrangements.
Related terms: Baseline · Communications management plan · Risk management plan
Study in: Project Life Cycles · Introduction · Governance Performance Domain · Risk Performance Domain · Inputs and Outputs
Prototype
An early representation built to test assumptions, usability, design, or feasibility before full commitment.
Plain language: A trial version used to learn cheaply.
Example: Residents test a clickable permit screen before developers build the service.
Related terms: Minimum viable product · Feedback · Validation
Study in: A System for Value Delivery · Project Life Cycles · Finance Performance Domain
Quality
The degree to which a result and the process producing it meet relevant needs, objectives, and requirements.
Plain language: How well the work and result are fit for their intended use.
Example: A reliable portal is accessible, secure, accurate, and usable under expected demand.
Related terms: Acceptance criteria · Cost of quality · Quality assurance
Study in: A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Tools and Techniques · Artificial Intelligence · Procurement · Evolution of the PMBOK Guide
Quality assurance
Planned evaluation and improvement of processes to provide confidence that quality objectives can be met.
Plain language: Checking whether the way work is done can reliably produce good results.
Example: The quality lead reviews the testing process and corrects gaps before release.
Related terms: Quality control · Assurance · Audit
Study in: Governance Performance Domain
Quality control
Inspection, testing, and analysis of results to determine whether they meet specified criteria.
Plain language: Checking the actual result for defects or nonconformance.
Example: A load test confirms whether the portal meets its response-time criterion.
Related terms: Quality assurance · Acceptance criteria · Verification
Study in: Governance Performance Domain · Scope Performance Domain
Register
A structured, regularly updated record used to track a class of project information.
Plain language: A living tracking list for one kind of information.
Example: The risk register records threats, owners, responses, and review dates.
Related terms: Log · Artifact · Risk register
Study in: Introduction · A System for Value Delivery · Project Management Principles · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Risk Performance Domain · Inputs and Outputs · Artificial Intelligence · Procurement
Release
A version of a product or capability made available for use.
Plain language: A usable version delivered to users or operations.
Example: The first release supports appointment booking before later reporting features are added.
Related terms: Increment · Cadence · Deployment
Study in: A System for Value Delivery · Project Management Principles · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Resources Performance Domain · Tools and Techniques
Requirements
Documented needs, conditions, or capabilities that a result must satisfy.
Plain language: What the solution or project must provide.
Example: The service must protect patient data and support screen-reader navigation.
Related terms: Scope · Acceptance criteria · Traceability
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Tailoring · Inputs and Outputs · Tools and Techniques · Project Management Offices · Procurement
Resource plan
The plan for identifying, obtaining, developing, using, and releasing people and physical resources.
Plain language: How the project will get and manage what the work needs.
Example: The plan reserves inspectors for commissioning and defines when contractors roll off.
Related terms: Resource utilization · Capacity · Project management plan
Study in: Resources Performance Domain
Resource utilization
The degree and pattern by which available resource capacity is assigned and consumed.
Plain language: How much of a person's or asset's capacity is being used.
Example: The team avoids scheduling a shared engineer at full capacity across two projects.
Related terms: Resource plan · Capacity · Schedule
Study in: Resources Performance Domain
Retrospective
A recurring reflection in which a team identifies what to continue, change, or test next.
Plain language: A team review aimed at improving the next cycle.
Example: After the pilot, the team agrees to involve support staff earlier in design reviews.
Related terms: Lessons learned · Continuous improvement · Iteration
Study in: Tailoring
Risk
An uncertain event or condition that could affect one or more project objectives.
Plain language: Something uncertain that may help or harm the project.
Example: A supplier may miss the delivery window, threatening commissioning.
Related terms: Threat · Opportunity · Issue
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Tools and Techniques · Project Management Offices · Artificial Intelligence · Procurement · Evolution of the PMBOK Guide
Risk appetite
The amount and type of uncertainty an organization is generally willing to pursue or retain for value.
Plain language: The organization's broad willingness to take risk.
Example: A hospital has little appetite for patient-safety uncertainty but accepts controlled pilot uncertainty.
Related terms: Risk threshold · Risk tolerance · Governance
Study in: Risk Performance Domain
Risk register
A living record of identified risks, analysis, owners, responses, triggers, and status.
Plain language: The main tracking list for project uncertainty.
Example: The register names the supplier-delay trigger and the owner of the backup response.
Related terms: Risk · Register · Risk response
Study in: Introduction · Project Management Principles · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Risk Performance Domain · Inputs and Outputs · Artificial Intelligence
Risk response
A chosen action or strategy to change exposure to a threat or opportunity.
Plain language: What the team plans to do about uncertainty.
Example: The team reserves an alternate supplier to reduce the impact of a delivery threat.
Related terms: Risk · Threat · Opportunity
Study in: Schedule Performance Domain · Risk Performance Domain
Rolling-wave planning
Detailed planning for near-term work while keeping later work at a higher level until more is known.
Plain language: Plan the next work closely and future work more broadly.
Example: The team details the next release while retaining rough estimates for later features.
Related terms: Progressive elaboration · Wave · Uncertainty
Study in: Schedule Performance Domain · Tools and Techniques
Schedule
A time-based model of planned activities, dependencies, milestones, and resource-informed dates.
Plain language: The organized timing of the project work.
Example: The schedule links design approval, procurement, installation, and testing.
Related terms: Schedule baseline · Milestone · Dependency
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Inputs and Outputs · Tools and Techniques · Artificial Intelligence · Procurement · Evolution of the PMBOK Guide
Schedule baseline
The approved schedule model used to compare actual and forecast timing and control changes.
Plain language: The agreed timeline used as the reference.
Example: The team measures forecast completion against the approved schedule baseline.
Related terms: Baseline · Schedule · Variance
Study in: Scope Performance Domain · Schedule Performance Domain · Inputs and Outputs
Schedule compression
Methods for shortening planned duration without reducing intended scope, usually by adding cost or risk.
Plain language: Finishing sooner by changing how work is sequenced or resourced.
Example: The team evaluates crashing and fast tracking on critical-path activities.
Related terms: Crashing · Fast tracking · Critical path
Study in: Schedule Performance Domain · Tools and Techniques
Scope
The boundaries of the product and project work needed to achieve agreed objectives and value.
Plain language: What is included in the result and the work—and what is not.
Example: The scope includes data migration and training but excludes replacement of clinic hardware.
Related terms: Product scope · Project scope · Requirements
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Inputs and Outputs · Tools and Techniques · Procurement · Evolution of the PMBOK Guide
Scope baseline
The approved scope statement, work breakdown structure, and associated details used for control.
Plain language: The agreed reference for what work and deliverables are included.
Example: A change request is required before adding another building to the rollout.
Related terms: Baseline · Work breakdown structure · Change control
Study in: Scope Performance Domain · Inputs and Outputs
Sourcing
The strategic choice and management of where needed products, services, or capabilities will come from.
Plain language: Deciding how and from whom the project will obtain what it needs.
Example: The agency combines internal design with external specialist testing.
Related terms: Procurement · Make-or-buy analysis · Supplier
Study in: Project Management Principles · Governance Performance Domain · Resources Performance Domain · Procurement
Stakeholder
A person, group, or organization that can affect, be affected by, or perceive effects from the project.
Plain language: Anyone with influence on or consequences from the work.
Example: Residents, regulators, operators, and the funding agency are stakeholders in a road project.
Related terms: Stakeholder analysis · Engagement · Influence
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Tools and Techniques · Project Management Offices · Artificial Intelligence · Procurement · Evolution of the PMBOK Guide
Stakeholder analysis
Systematic assessment of stakeholders' interests, influence, needs, relationships, and potential responses.
Plain language: Understanding who matters, what they care about, and how they may affect the work.
Example: The team identifies low-power residents who face high disruption and designs accessible engagement.
Related terms: Stakeholder · Engagement · Stakeholder register
Study in: Stakeholders Performance Domain · Tools and Techniques
Stakeholder engagement
Planned, two-way involvement of stakeholders to understand concerns, shape decisions, and support outcomes.
Plain language: Working with affected people throughout the project.
Example: Operators review prototypes and help define acceptance conditions before rollout.
Related terms: Engagement · Feedback · Communications planning
Study in: A System for Value Delivery · Project Management Principles · Introduction · Governance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Evolution of the PMBOK Guide
Stakeholder register
A maintained record of identified stakeholders and relevant information for engagement planning.
Plain language: The project's working list of stakeholders and what is known about them.
Example: The register notes each regulator's authority, interests, and contact owner.
Related terms: Stakeholder · Register · Stakeholder analysis
Study in: Introduction · Stakeholders Performance Domain
Strategy
The set of choices that directs how an organization pursues objectives and allocates resources.
Plain language: The organization's chosen path toward its goals.
Example: The portfolio stops a sound project after strategy shifts toward remote service access.
Related terms: Portfolio · Business case · Value
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Tailoring · Inputs and Outputs · Project Management Offices · Procurement
Sustainability
Consideration of economic, environmental, and social effects across the work and the life of its outcomes.
Plain language: Creating value without ignoring long-term effects on people, planet, and prosperity.
Example: Option analysis includes energy use, accessibility, labor conditions, and operating cost.
Related terms: Externality · Life cycle · Value
Study in: Project Management Principles · Introduction · Governance Performance Domain · Scope Performance Domain · Resources Performance Domain · Tailoring · Artificial Intelligence · Procurement
Tailoring
Deliberate adaptation of approach, governance, methods, and artifacts to fit context while preserving necessary controls.
Plain language: Choosing a fit-for-purpose way to manage the project.
Example: A small low-risk pilot uses lighter reporting but retains mandatory privacy review.
Related terms: Hybrid approach · Project environment · Governance
Study in: Introduction · A System for Value Delivery · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Stakeholders Performance Domain · Resources Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Evolution of the PMBOK Guide
Team leadership
The work of enabling shared direction, healthy collaboration, decisions, growth, and accountable performance.
Plain language: Helping a team work well and deliver responsibly.
Example: A leader creates clear decision boundaries and invites early reporting of mistakes.
Related terms: Leadership · Psychological safety · Team charter
Study in: Resources Performance Domain
Threat
An uncertain event or condition that could harm project objectives or value.
Plain language: A possible downside worth managing.
Example: A permit delay could push installation into winter and increase cost.
Related terms: Opportunity · Risk · Risk response
Study in: Risk Performance Domain
Time and materials
A commercial arrangement that pays agreed labor rates and material costs for the resources actually used.
Plain language: Pay for the time worked and materials consumed.
Example: Commissioning support uses hourly specialist rates because the exact effort is uncertain.
Related terms: Contract type · Fixed-price contract · Procurement
Study in: Finance Performance Domain
Traceability
The ability to follow a requirement, decision, change, or result through its origin, implementation, and evidence.
Plain language: A visible chain showing where something came from and how it was handled.
Example: The team links a privacy requirement to design controls, an approved change, and its security test.
Related terms: Requirements · Validation · Verification
Study in: A System for Value Delivery · Governance Performance Domain · Scope Performance Domain · Finance Performance Domain · Tailoring · Inputs and Outputs · Artificial Intelligence
Trade-off
A decision that accepts less of one desirable result to gain more of another under constraints.
Plain language: Choosing between competing benefits or costs.
Example: The sponsor accepts a later launch to preserve safety testing.
Related terms: Constraint · Prioritization · Decision rights
Study in: A System for Value Delivery · Project Management Principles · Schedule Performance Domain · Finance Performance Domain · Risk Performance Domain
Transition
The planned movement of a deliverable and its supporting capabilities into operational use or a new state.
Plain language: Helping people and systems move from project delivery to normal use.
Example: The project trains service staff, migrates data, and transfers support ownership.
Related terms: Handover · Operational readiness · Change management
Study in: Introduction · A System for Value Delivery · Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Inputs and Outputs · Evolution of the PMBOK Guide
Uncertainty
Limited knowledge about future events, conditions, estimates, or the best way to achieve an objective.
Plain language: What the team does not yet know with confidence.
Example: User behavior remains uncertain until the pilot produces evidence.
Related terms: Risk · Estimate · Adaptive approach
Study in: Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Schedule Performance Domain · Finance Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Tools and Techniques · Artificial Intelligence · Procurement
Validation
Evaluation of whether a result serves its intended use and stakeholder need in context.
Plain language: Checking that the right solution was built.
Example: Clinicians use the prototype to confirm it supports the real appointment workflow.
Related terms: Verification · Acceptance criteria · Requirements
Study in: A System for Value Delivery · Project Management Principles · Introduction · Scope Performance Domain · Schedule Performance Domain · Inputs and Outputs · Tools and Techniques · Artificial Intelligence
Value
The net worth or usefulness stakeholders associate with outcomes relative to investment and alternatives.
Plain language: Whether the gains justify what is spent or sacrificed.
Example: A simpler reminder service creates more value than an expensive dashboard users ignore.
Related terms: Benefit · Outcome · Business case
Study in: Introduction · A System for Value Delivery · Project Management Principles · Project Life Cycles · Introduction · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Resources Performance Domain · Risk Performance Domain · Tailoring · Inputs and Outputs · Tools and Techniques · Project Management Offices · Procurement · Evolution of the PMBOK Guide
Value delivery system
The connected organizational system through which strategy, investments, projects, products, operations, and feedback produce value.
Plain language: The full chain that turns strategic choices into real-world gains.
Example: Portfolio funding, project delivery, product evolution, and operations jointly reduce transit delays.
Related terms: Strategy · Portfolio · Benefits realization
Study in: Introduction
Value proposition
A testable explanation of why a proposed result should create worthwhile value for particular stakeholders.
Plain language: The reason people should benefit from or choose the result.
Example: The portal's value proposition is faster access with fewer in-person visits.
Related terms: Business case · Minimum viable product · Benefit
Study in: A System for Value Delivery · Project Management Principles · Project Life Cycles · Governance Performance Domain · Finance Performance Domain · Project Management Offices
Variance
A quantified difference between actual or forecast performance and an approved reference.
Plain language: The gap between what was expected and what occurred or is now predicted.
Example: Forecast finish is ten days later than the schedule baseline.
Related terms: Baseline · Forecast · Control
Study in: Project Life Cycles · Governance Performance Domain · Scope Performance Domain · Schedule Performance Domain · Finance Performance Domain · Resources Performance Domain · Inputs and Outputs · Tools and Techniques
Verification
Evaluation of whether a result conforms to specified requirements and acceptance conditions.
Plain language: Checking that the solution was built correctly.
Example: A test confirms that the portal encrypts records as specified.
Related terms: Validation · Quality control · Requirements
Study in: Project Management Principles · Scope Performance Domain · Inputs and Outputs
Work breakdown structure
A hierarchical decomposition of the total project scope into manageable deliverable-oriented components.
Plain language: A tree that breaks all included work into controllable pieces.
Example: The facility WBS separates site work, utilities, building systems, and commissioning.
Related terms: Decomposition · Work package · Scope baseline
Study in: Scope Performance Domain
Work package
The lowest WBS component planned and controlled as a unit for estimation, assignment, and monitoring.
Plain language: A manageable chunk of scoped work.
Example: The electrical-room installation is estimated, assigned, and tracked as one work package.
Related terms: Work breakdown structure · Decomposition · Bottom-up estimating
Study in: Scope Performance Domain · Inputs and Outputs