The Project Management Glossary You Wish Onboarding Had

Project management has its own language, and most onboarding does not teach it. New PMs spend their first months on every team learning by context: "critical" in "critical path" means zero-float, not important. A "milestone" is not a deliverable. A "risk" and an "issue" trigger completely different responses. Stakeholders who have never managed a project encounter the same vocabulary gap from the other direction: they sit in steering committees parsing terminology the PM uses as shorthand, and they make decisions based on half-understood terms.

This project management glossary is the reference you can hand a new PM in their first week, share with a stakeholder who keeps confusing risk with issue, or use to settle a vocabulary dispute before it affects a decision. Definitions are plain English, one sentence each. Each term includes a one-line example that makes the definition concrete.

TL;DR. Sixty-plus terms, organized by category, with a particular focus on the pairs that cause the most confusion: risk vs issue, milestone vs deliverable, float vs contingency reserve, and CPI vs SPI. Jump to the category you need, or read the confused-pairs section first if you only have five minutes.

How to use this project management glossary

Terms are organized into six categories: planning and scheduling, execution and control, resource and cost, governance and oversight, and methodology. The categories broadly align with PMBOK knowledge areas, though the terminology here favors plain English over PMI-specific jargon where the two diverge. Some terms appear under multiple frameworks with different names; where that matters, the most common alternative is noted. The glossary links to deeper posts on the Onplana blog for terms that carry enough nuance to justify their own treatment.

The most commonly confused pairs in PM vocabulary

Vocabulary errors cause real project damage when they reach a decision. A sponsor who treats a risk as an issue responds differently, often too urgently. A PM who treats a deliverable as a milestone loses tracking on whether the output actually exists. These six pairs are responsible for more communication failures than the rest of the glossary combined.

Risk vs issue

A risk is a potential future event that has a probability and an impact if it occurs. It lives in the risk register, with a mitigation plan (to reduce the probability) and a contingency plan (to reduce the impact if it fires). An issue is a risk that has already happened: the vendor missed the delivery, the server is down, the key resource resigned. It moves from the risk register to the issue log and requires active management, not monitoring. The distinction matters because the response is different. Monitoring a risk that is already an issue wastes time and gives the team false comfort that something is being "managed" when it actually needs to be solved.

Milestone vs deliverable

A milestone is a zero-duration event that marks a significant point in the schedule. No work occurs at a milestone; work occurs before it. "Design approved" is a milestone. "The design document" is the deliverable that made the milestone reachable. The confusion causes real problems in schedule reporting: a PM who marks a milestone complete without verifying the deliverable exists is reporting schedule progress that does not reflect actual work completion. For more on how these differ in practice, see the post on milestones vs deliverables vs tasks.

Float vs contingency reserve

Float is a mathematical property of the task network: it is the amount of time a task can slip without pushing the project end date. Critical path tasks have zero float by definition. Float is not time you can spend; it is slack in the schedule that the network creates passively. Contingency reserve is an explicit planning decision: a budget or schedule buffer set aside to cover identified risks that have been quantified. One is structural; the other is intentional. A PM who points to float as the reason the project can absorb a risk has confused the two.

Critical path vs near-critical path

The critical path is the longest sequence of dependent tasks from project start to finish. Any task on the critical path has zero float; any delay cascades directly to the end date. The near-critical path is the next-longest sequence, typically defined as tasks with float of five days or fewer. Near-critical paths are dangerous precisely because they look like they have room. Float erodes. A task with four days of float that slips by five days is now on the critical path, and the event may not surface in a status report until it already has. Managing near-critical paths proactively is one of the most underutilized schedule risk controls.

CPI vs SPI

Both metrics come from earned value management. CPI (Cost Performance Index) measures cost efficiency: CPI = EV / AC, where EV is earned value (budgeted cost of work performed) and AC is actual cost. A CPI above 1.0 means you are spending less than planned for the work completed. SPI (Schedule Performance Index) measures schedule efficiency: SPI = EV / PV, where PV is planned value (budgeted cost of work scheduled). SPI above 1.0 means you are ahead of schedule. The two can diverge: a project can be on schedule but over budget (SPI near 1.0, CPI below 1.0), which means the team is spending more to maintain the same pace. Reporting both gives a complete picture.

Sponsor vs steering committee

The project sponsor is one person: the executive who owns the business case, holds budget authority, and is accountable for the project outcome. The steering committee is a group: typically the sponsor plus other senior stakeholders who represent affected business areas or oversight functions. The sponsor can make decisions unilaterally within their authority; the steering committee provides input, alignment, and cross-functional visibility. When something needs an immediate decision and the steering committee cannot convene in time, the sponsor decides. When something requires political alignment across multiple business units, bring it to the committee.

Planning and scheduling terms

Critical path. The longest sequence of dependent tasks through the project network, where any delay pushes the end date by the same number of days. Example: if design, development, and testing must each complete before the next begins, all three are on the critical path. See critical path method explained for the full network calculation.

Float (also: slack). The number of days a task can be delayed without affecting the project end date. Critical path tasks have zero float; tasks on parallel paths accumulate float based on the difference in path lengths.

Baseline. A fixed, approved snapshot of the project plan (scope, schedule, cost) against which actual performance is measured. Example: "We are 12 days behind the baseline completion date" has meaning only because a baseline exists to compare against.

Work Breakdown Structure (WBS). A hierarchical decomposition of all work required to complete the project, organized into progressively smaller work packages. The WBS is the foundation for cost estimates, schedule estimates, and resource assignments. See work breakdown structure guide for how to build one.

Gantt chart. A bar chart that displays project tasks along a timeline, showing start and end dates, dependencies, and critical path visually. Gantt charts are the most common schedule format but can obscure network logic if used as the sole planning artifact.

Milestone. A zero-duration task that marks a significant point in the schedule. Milestones have no work attached to them; they signal completion of a phase or approval of a deliverable.

Dependency (also: predecessor/successor). A logical relationship between two tasks that constrains when the second can start or finish relative to the first. The four standard types are finish-to-start, start-to-start, finish-to-finish, and start-to-finish. See dependency types deep dive for practical guidance on each.

Lag. A deliberate delay added to a dependency. Example: a finish-to-start dependency with three days of lag means the successor cannot start until three days after the predecessor finishes.

Lead. An overlap allowed between a predecessor and successor. A lead compresses the schedule by letting the successor begin before the predecessor fully completes.

Duration. The elapsed calendar time between a task's start and finish, including non-working time. A task with 5 days of effort that starts on a Monday and has a 3-day weekend in the middle has a duration of 8 calendar days.

Effort. The total amount of work required to complete a task, expressed in person-hours or person-days. A task requiring 10 hours of effort assigned to two resources at 50% utilization each has a 10-day duration.

Contingency reserve. An explicit amount of time or budget added to the project plan to cover identified risks that have been quantified. Contingency is not a buffer for poor estimates; it is tied to specific risk events.

Management reserve. An additional budget held by the project sponsor for unknown unknowns: unforeseeable events not captured in the risk register. Unlike contingency, management reserve requires sponsor approval to access.

Execution and control terms

Status report. A recurring written summary of project health covering accomplishments, upcoming work, risks, issues, and decisions needed. A useful status report tells the reader what to do, not just what happened. See status report writing guide for format and content guidance.

RAG status. A three-value health indicator: Red (immediate problem requiring intervention), Amber (risk or issue needs attention before it becomes critical), Green (on track). RAG status should be defined explicitly for the project so that "Green" means the same thing to the PM and the sponsor.

Change request. A formal document proposing a change to the approved scope, schedule, or budget. Change requests are not optional for significant changes: without them, the baseline loses its meaning as a performance reference.

Change Control Board (CCB). A group authorized to approve or reject change requests. The CCB typically includes the sponsor, key stakeholders, and the PM. Small projects may give the PM CCB authority alone up to a defined threshold.

Issue. A risk that has materialized and requires active resolution. Issues are tracked in an issue log with an owner, a target resolution date, and a status update at each reporting cycle.

Risk. A potential future event that could affect the project positively (opportunity) or negatively (threat). Risks are tracked in the risk register with probability, impact, response strategy, and an owner.

Assumption. A condition believed to be true for planning purposes that has not been verified. Assumptions that prove false become risks or issues. Documenting assumptions protects the PM when conditions change.

Risk register. A living document that lists all identified risks, their probability, impact, response strategy, owner, and current status. The risk register is reviewed and updated at each reporting cycle.

Variance. The difference between planned and actual performance. Schedule variance = EV minus PV. Cost variance = EV minus AC. Positive variance is favorable in earned value terms; negative variance means the project is behind or over budget.

Action item. A specific, assigned task with an owner and a due date that results from a meeting or decision. Action items are distinct from project tasks: they are typically short-horizon commitments made in real time that need tracking between meetings.

Resource and cost terms

Resource. Any person, equipment, or material required to complete project work. Resources are assigned to tasks and consume capacity; the aggregate of all assignments drives the resource demand profile.

Overallocation. The condition in which a resource is assigned more work in a given time period than their available capacity allows. See the resource heatmap tool for a visual approach to identifying overallocation across the team.

Resource leveling. Adjusting the schedule by delaying tasks to resolve overallocation, even if doing so extends the project end date. Leveling prioritizes workload balance over schedule compression.

Resource smoothing. Adjusting resource assignments within available float to even out demand without changing the project end date. Smoothing is less disruptive than leveling but is limited by the float available.

Utilization. The percentage of a resource's available capacity that is committed to assigned work. 100% utilization means fully allocated with no buffer; above 100% means overallocated.

Earned Value (EV). The budgeted cost of work actually completed to date. EV measures how much value the project has produced relative to the plan, independent of what was actually spent.

Planned Value (PV). The budgeted cost of work scheduled to be completed by a given date. PV is the baseline against which actual progress is measured at any point in time.

Actual Cost (AC). The total cost actually incurred to complete work to date. AC is compared against EV (not PV) to determine cost efficiency.

CPI (Cost Performance Index). EV divided by AC. A CPI of 0.90 means the project is getting 90 cents of earned value for every dollar spent.

SPI (Schedule Performance Index). EV divided by PV. An SPI of 1.05 means the project has earned 5% more value than was planned for this point in time.

BAC (Budget at Completion). The total approved budget for the project. BAC is the denominator for several EV forecasting formulas.

EAC (Estimate at Completion). A forecast of the total project cost based on current performance trends. The most common formula is BAC divided by CPI, which assumes current cost efficiency continues for the rest of the project.

Governance and oversight terms

Sponsor. The executive who owns the business case, holds budget authority, removes organizational blockers, and is ultimately accountable for the project outcome. The sponsor is not the day-to-day manager of the project; that is the PM's role.

Steering committee. A group of senior stakeholders, typically including the sponsor, who provide oversight, cross-functional alignment, and decision authority above the PM's level. Steering committees meet on a defined cadence, typically monthly or at phase gates.

PMO (Project Management Office). A function that defines and maintains project management standards, provides oversight of the project portfolio, and in some organizations directly manages large projects. PMO maturity ranges from advisory to directive depending on organizational model.

RACI. A responsibility assignment matrix with four roles: Responsible (does the work), Accountable (owns the outcome), Consulted (provides input), Informed (receives updates). Each task or decision has exactly one Accountable party.

Project charter. A document that formally authorizes the project and gives the PM authority to apply organizational resources. The charter records the project purpose, objectives, high-level scope, major milestones, budget, sponsor, and key stakeholders.

Gate review. A formal checkpoint at the end of a project phase where the sponsor and steering committee evaluate whether the project should proceed to the next phase, be replanned, or be terminated. Gate reviews are the governance mechanism for phase-gated delivery models.

Lessons learned. A structured review of what worked and what did not across the project, conducted at closure and at key phase transitions. Lessons learned are only useful if they are documented, shared, and accessible to future project teams.

Methodology terms

Waterfall. A sequential delivery approach where each phase (requirements, design, build, test, deploy) completes before the next begins. Waterfall suits projects where scope is well-defined and stable, and where changes mid-execution are costly.

Agile. An iterative delivery approach that produces working increments of the product in short cycles, with requirements refined continuously based on feedback. Agile suits projects where scope evolves and early feedback is valuable.

Sprint. A fixed-length iteration in Scrum, typically one to four weeks, at the end of which a potentially shippable product increment is produced.

Backlog. The prioritized list of features, user stories, and tasks to be completed in a product or project. The product backlog covers all remaining work; the sprint backlog covers work committed for the current sprint.

Burndown chart. A chart that tracks remaining work (typically in story points or hours) against time across a sprint or release. A healthy burndown line trends toward zero by the sprint end date.

Kanban. A visual workflow management method that limits work in progress and makes the flow of tasks visible. Kanban boards show tasks moving through states (To Do, In Progress, Done) and surface bottlenecks where tasks accumulate.

Critical chain. A scheduling method that accounts for resource constraints alongside task dependencies, and places buffers at the end of the critical chain rather than padding individual tasks. Critical chain was developed by Eli Goldratt as an alternative to traditional critical path scheduling.

Hybrid. A delivery approach that combines waterfall and agile elements, typically applying sequential planning to scope and contracts while using iterative delivery cycles for build and test. See hybrid team mixed methodology for a practical approach to combining the two.

---

Run the free Schedule Health Check Upload your .mpp file and get a report on critical path integrity, float health, missing baselines, and resource overallocation. No signup required. → Open the Schedule Health Check