Master the Essential Project Management Vocabulary: 40 Key Terms Explained

General Project Management Vocabulary

1. Project Plan

A project plan is a formal document created before any project starts, typically including approved cost, schedule, and scope, guiding execution from initiation to closure and establishing communication foundations among stakeholders.

2. Work Breakdown Structure (WBS)

WBS breaks project deliverables into manageable components, helping the team understand work nature and efficiently advance project goals.

3. Critical Path Method (CPM)

CPM is an algorithm used to schedule project activities, determining activity order and total project duration; activities must follow this sequence to meet project objectives.

4. Project Manager

The person responsible for handling all aspects of a project from start to close, typically overseeing strong planning, intelligent resource utilization, and scope management.

5. Project Stakeholder

Anyone with a direct or indirect interest in the project, influencing or being affected by decisions throughout the project lifecycle; includes team members, managers, sponsors, customers, or end users.

6. Project Portfolio Management (PPM)

PPM involves collectively managing a set of projects to achieve organizational goals, allowing teams to visualize the big picture and maximize return on investment.

7. Collaboration

The process of actively involving each team member in project activities, requiring a network where individuals exchange information and monitor performance.

8. Agile Project Management

An iterative and incremental approach that breaks the project into short cycles called "iterations" and prioritizes them by urgency or importance; Scrum is the most popular framework.

9. Waterfall Model

A traditional linear project lifecycle where each phase must be completed before moving to the next, with no overlap, making mid‑process changes difficult.

10. Project Budget

A formally approved document listing all financial resources required to complete the project.

11. Project Schedule

A chronological outline of project events, capturing what work must be done and how it will be performed throughout the lifecycle.

Gantt Project Management Terms

Gantt charts visually display project schedules, showing work that must be completed within specific time periods.

12. Milestone

A significant event in the project lifecycle used as a reference point to measure progress, often represented by a diamond.

13. Dependency

Specifies the relationship between project activities and their execution order. Four types exist:

Start‑Start – the predecessor must start before the successor starts.

Finish‑Start – the predecessor must finish before the successor starts.

Start‑Finish – the predecessor must start before the successor finishes.

Finish‑Finish – the predecessor must finish before the successor finishes.

Kanban Project Management Terms

14. Work In Progress (WIP)

The number of tasks a team is currently handling at any point, indicating the workflow capacity.

15. WIP Limit

Restricts the amount of work in each workflow stage, helping teams quickly identify bottlenecks and focus on individual items.

16. Bottleneck

A stage where incoming work exceeds the system’s capacity, hindering smooth flow.

17. Scrum

A popular framework for achieving agility, using iterative delivery and continuous collaboration between team members across project cycles.

18. Sprint

A fixed timebox during which specific tasks must be completed; daily stand‑up meetings monitor sprint progress.

Project Management Meeting Terms

19. Project Kick‑off Meeting

The first meeting between the project team and the client after basic project details are defined, aiming to review expectations and align all participants.

20. Meeting Agenda

A list of topics to be discussed during a meeting, often including descriptions, order, and expected outcomes.

21. Meeting Minutes

A written record of everything discussed in a meeting, shared afterward to provide insights and guide follow‑up actions.

22. Stand‑up Meeting

A short daily meeting (also called Daily Scrum) where each team member updates the group on progress.

23. Follow‑up

Post‑meeting activities aimed at gathering feedback from participants; sometimes a dedicated follow‑up meeting is held.

Resource Project Management Terms

24. Resource Allocation

Assigning resources to project tasks in the most effective way to support the final goal.

25. Resource Breakdown Structure

A comprehensive list of all resources needed for the project, typically organized by function and type for planning and control.

26. Resource Leveling

Adjusting the project schedule to keep resource usage below set limits, preventing overtime and affecting the critical path.

27. Resource Availability

Specifies whether a particular resource is available at a given time.

28. Resource Calendar

Shows all working and non‑working days for a specific resource.

Project Risk Management Terms

29. Risk Management

The process of identifying and assessing risks to reduce negative impacts on project operations and ensure objectives remain unaffected.

30. Risk Mitigation

Strategies designed to lower the probability or impact of risks, focusing on actions that protect the overall project goal.

31. Risk Monitoring and Control

Tracking the execution of risk responses compared to the original risk management plan.

32. Risk Owner

The person responsible for ensuring a specific risk is properly managed, including implementing mitigation strategies and possibly conducting qualitative and quantitative analyses.

Issue Management and Bug Tracking Terms

33. Issue Management

The comprehensive process of identifying, resolving, and tracking project‑related issues before they become major problems.

34. Issue Tracking

Identifying potential bugs or errors in a product that affect performance, often using specialized software.

35. Issue Log

A complete record of all project issues (open and closed) and the people responsible for resolving them, including status and resolution dates.

36. Issue Type

Categories defining the kinds of problems a project may encounter, facilitating assignment and tracking.

Typically, three issue types appear:

Bug – any problem affecting product functionality.

Epic – a large body of work composed of multiple issues.

Story – a short feature request viewed from the end‑user perspective.

Quality Assurance Project Management Terms

37. Quality Plan

Defines the expected quality standards for the project and creates systems to ensure those standards are effectively implemented.

38. Quality Assurance

Implements planned activities and systematic processes to meet project quality requirements, often involving regular audits.

39. Quality Control

Uses standardized practices to evaluate whether the final product meets quality expectations, identifying any needed changes after creation.

40. Quality Management Plan

A detailed plan covering stakeholder quality expectations, assurance policies, and control procedures, typically part of the overall project management plan.