PMP Process Domain Glossary — Key Terms & Definitions

Process Domain Key Terms

Project Charter: A document that formally authorizes the existence of a project and provides the project manager with authority to apply organizational resources.
Project Management Plan: The comprehensive document that defines the basis of all project work and how the project will be executed, monitored, controlled, and closed.
Change Control Board (CCB): A formally chartered group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project.
Integrated Change Control: The process of reviewing all change requests, approving changes, and managing changes to deliverables, project documents, and the project management plan.
Lessons Learned Register: A project document used to record knowledge gained during a project to improve future projects.

Work Breakdown Structure (WBS): A hierarchical decomposition of the total scope of work into manageable work packages. The lowest level is the work package.
Scope Baseline: The approved version of the scope statement, WBS, and WBS dictionary, used as a basis for comparison.
Requirements Traceability Matrix: A grid linking product requirements to the deliverables that satisfy them, ensuring each requirement adds business value.
Scope Creep: The uncontrolled expansion of product or project scope without adjustments to time, cost, and resources.
Gold Plating: Adding extra features or functionality not in the project scope. Unlike scope creep, it's done intentionally by the team.

Critical Path: The longest sequence of activities in a project network that determines the shortest possible project duration. Activities on the critical path have zero float.
Float (Slack): The amount of time an activity can be delayed without delaying the project finish date (total float) or the next activity (free float).
PERT Estimate: Three-point estimate: (Optimistic + 4×Most Likely + Pessimistic) / 6
Fast Tracking: A schedule compression technique that involves performing activities in parallel that would normally be done in sequence. Increases risk.
Crashing: A schedule compression technique that adds resources to critical path activities to shorten duration. Increases cost.
Lead: The amount of time a successor activity can be advanced relative to a predecessor. Allows overlap.
Lag: The amount of time a successor activity must be delayed relative to a predecessor. Forces a waiting period.

Earned Value (EV): The measure of work performed expressed in terms of the budget authorized for that work. EV = % Complete × BAC.
Planned Value (PV): The authorized budget assigned to scheduled work.
Actual Cost (AC): The realized cost incurred for the work performed on an activity during a specific time period.
Budget at Completion (BAC): The sum of all budgets established for the work to be performed on the project.
Cost Performance Index (CPI): A measure of cost efficiency: EV / AC. CPI > 1.0 means under budget.
Schedule Performance Index (SPI): A measure of schedule efficiency: EV / PV. SPI > 1.0 means ahead of schedule.

Risk Register: A document recording identified risks, their analysis, and planned responses.
Probability and Impact Matrix: A grid for mapping the probability of each risk occurrence and its impact on project objectives.
Risk Response Strategies (Threats): Avoid, Transfer, Mitigate, Accept, Escalate.
Risk Response Strategies (Opportunities): Exploit, Share, Enhance, Accept, Escalate.
Expected Monetary Value (EMV): The product of probability and impact used in quantitative risk analysis. EMV = Probability × Impact.
Monte Carlo Simulation: A technique using random sampling to model the probability of different outcomes in a process that involves uncertainty.

Sprint: A time-boxed iteration in Scrum, typically 1-4 weeks, during which a potentially releasable increment is created.
Product Backlog: An ordered list of everything that is known to be needed in the product, managed by the Product Owner.
Sprint Backlog: The set of product backlog items selected for the sprint, plus a plan for delivering them.
User Story: A short description of functionality from the end user's perspective: "As a [role], I want [feature] so that [benefit]."
Velocity: The amount of work a team can complete in a single sprint, measured in story points or similar units.
Definition of Done (DoD): A shared understanding of what it means for work to be complete, ensuring transparency and quality.
Retrospective: A meeting held at the end of each iteration for the team to reflect on what went well, what didn't, and what to improve.
Daily Standup: A brief daily meeting (typically 15 minutes) where team members share progress, plans, and blockers.