Dictonary

Acceptance Criteria - Defined conditions that a project deliverable must satisfy to be formally accepted by the customer or sponsor. These criteria ensure clarity of expectations and reduce the risk of disputes. Commonly used in Agile and traditional projects.
Acceptance test - Test, which is run with the predefined criterias to verify that system functionality/functionalities fullfil customer expectations
Action Item - Any task or activity which was agreed to be completed within specified deadline by assigned personel
Activity - A distinct, scheduled portion of work performed during a project. Activities are often broken down into tasks in the Work Breakdown Structure (WBS).
Activity list - List of all activities which are necessary to complete project phase, project or any work package. Every activity in the list has to have assigned ID, description, prerequisites or dependencies (if any), responsible person and a due date.
Acceptance Criteria - Defined conditions that a project deliverable must satisfy to be formally accepted by the customer or sponsor. These criteria ensure clarity of expectations and reduce the risk of disputes. Commonly used in Agile and traditional projects.
Agile - An iterative approach to project management emphasizing flexibility, collaboration, and customer feedback. Agile methodologies include Scrum, Kanban, and XP.
Agile Coach - A professional who guides teams and organizations in implementing Agile principles effectively.
Agile Manifesto - A set of four values and twelve principles guiding Agile software development and project management.
Assumption - A factor considered true without proof for the purpose of planning. Assumptions must be documented and monitored throughout the project life cycle.
Authorization - The formal approval to proceed with a project or phase. Often documented in a project charter or governance document.
Agile Release Planning - The process of planning releases of product increments in Agile frameworks, balancing business priorities and team capacity.
Aggregate planning - Type of project strategy, where the project activities are planned in detail for specified time period (typicaly 3 - 9 months) to ensure, that all required resources will be available for project when needed. This strategy is beneficial when company is using shared resources for multiply projects and is doing joint project planning with integrated resource planning where integrated project plan consists of all project activities for all projects.
Allocation - The assignment of resources to tasks or projects in order to achieve objectives within time and budget constraints.
Artefact - A tangible byproduct produced during a project, such as documents, models, or prototypes. Common term in Agile.
Audit - A formal examination of project processes, performance, or compliance with standards, often performed by internal or external reviewers.
Approval - The official acceptance of deliverables, plans, or changes by the appropriate authority.
Alignment - The process of ensuring that project objectives, deliverables, and processes are consistent with organizational strategy and stakeholder expectations.
Activity-on-Arrow (AOA) - A network diagramming technique where arrows represent activities and nodes represent events or milestones.
Activity-on-Node (AON)- A network diagramming technique where nodes represent activities and arrows indicate dependencies.
Agile Team - A cross-functional team working collaboratively to deliver value iteratively and incrementally in Agile projects.
Anchoring - A cognitive bias where initial information or estimates overly influence subsequent decisions, important to recognize in project planning and estimation.
Application Area - A domain of project management knowledge or industry focus, such as IT, construction, or healthcare.
Analysis - The process of examining data, risks, or requirements to inform project decisions.
Artifact Repository - A centralized storage system for all project artifacts, ensuring traceability and accessibility.
Authorization Limit - The maximum extent of decision-making or approval authority granted to an individual or role.
Agile Metrics - Measurements used to evaluate team performance, project progress, and delivery in Agile environments, such as velocity or burn-down charts.
Agile Planning Poker - An estimation technique in Agile using cards to assign effort values collaboratively to user stories.
Agile Retrospective - A recurring meeting in Agile where the team reflects on performance, identifies improvements, and adjusts processes.
Alignment Workshop - A meeting to ensure that stakeholders and project teams share a common understanding of objectives, scope, and priorities.
Acceptable Quality Level (AQL) - A standard defining the maximum number of defective items or errors considered acceptable in a deliverable.
Audit Trail - A documented history of project decisions, changes, and approvals for accountability and transparency.
Agile Story Points - A relative measure used in Agile to estimate the complexity or effort of user stories, helping with sprint planning and capacity management.

Backlog - A prioritized list of work items or features to be completed, commonly used in Agile methodologies such as Scrum and Kanban. It helps teams manage scope and priorities efficiently.
Baseline - The approved version of a project’s scope, schedule, and cost plan that serves as a reference for measuring project performance. Any deviations require formal change control.
Benchmarking - The process of comparing project practices, metrics, or performance against industry best practices or peer organizations to identify improvement opportunities.
Benefits Realization - The process of ensuring that project outcomes deliver the intended business benefits, including tracking and measuring performance against objectives.
Burn-down Chart - A visual representation of remaining work versus time in Agile projects, used to track progress within a sprint or release.
Business Case - A document that justifies the initiation of a project, analyzing expected benefits, costs, risks, and alternatives to support decision-making.
Budget - The planned allocation of financial resources for the project, including estimates for labor, materials, and contingency funds.
Bridge Document - A document linking requirements, design, and implementation plans to ensure alignment and traceability across project phases.
Bridging Phase - A phase in hybrid project management approaches that connects planning and execution, ensuring smooth transition and readiness.
Business Impact Analysis (BIA) - A method used to evaluate the potential effects of interruptions to business processes, commonly used in risk management and business continuity planning.
Business Process Modeling - A technique to visually represent workflows, roles, and responsibilities to improve understanding, efficiency, and communication.
Buy-in - The commitment or agreement of stakeholders or team members to support project objectives, decisions, or changes.
Benefits Dependency Network - A visual tool showing the relationships between project outputs, outcomes, and organizational benefits to track value realization.
Bridge Role - A role assigned to facilitate communication and coordination between different teams, functions, or project phases.
Budget Variance - The difference between planned and actual project expenditures, used to monitor financial performance.
Business Requirements - Detailed statements describing what the business needs the project to achieve, often forming the basis for functional requirements.
Business Unit - A segment of an organization with specific responsibilities and objectives that may sponsor or be impacted by projects.
Burn-up Chart - A visual tool used to track completed work over time in Agile projects, showing scope changes and progress toward objectives.
Backward Pass - A technique in critical path analysis to calculate the latest possible finish times for project activities, used to identify float.
Bridging Meeting - A session conducted to align multiple teams, stakeholders, or workstreams, ensuring shared understanding of scope, schedule, and priorities.
Business Continuity Plan (BCP) - A plan outlining procedures and processes to ensure critical business functions continue during and after disruptive events
Business Continuity Plan (BCP) - A plan outlining procedures and processes to ensure critical business functions continue during and after disruptive events

Change Control - The formal process of requesting, evaluating, and approving changes to project scope, schedule, or budget. Ensures that all modifications are properly reviewed and authorized to prevent scope creep.
Charter - A document that formally authorizes the project and provides the project manager with authority to apply organizational resources to project activities.
Constraint - A limiting factor that affects project execution, such as time, cost, scope, quality, or resource availability. Commonly represented in the Project Management Triangle.
Critical Path Method (CPM) - A scheduling technique used to identify the sequence of activities that determines the minimum project duration. Delays in critical path tasks directly impact project completion.
Cross-functional Team - A team composed of members with different functional expertise, collaborating to achieve project objectives.
Communication Plan - A formal document outlining who will receive project information, what will be communicated, how often, and through which channels.
Cost Baseline - The approved version of the project budget, used to measure financial performance and manage cost variances.
Cost Performance Index (CPI) - A measure in Earned Value Management indicating cost efficiency of project work. Calculated as Earned Value divided by Actual Cost.
Contingency Plan - A plan developed to address potential risks, detailing steps to take if a risk event occurs.
Configuration Management - A process to systematically manage changes to project deliverables and ensure consistency with requirements, design, and documentation.
Corrective Action - Actions taken to bring project performance in line with the project management plan, addressing deviations from scope, schedule, or cost baselines.
Critical Chain Method (CCM) - A scheduling technique that focuses on resource constraints and buffers to protect the project schedule against uncertainties.
Cost Estimate - The quantified approximation of project costs for resources, labor, materials, and contingencies, forming the basis of the project budget.
Customer Requirements - The documented needs and expectations of the customer or end-user that the project must satisfy.
Cycle Time - The total time taken to complete a process or activity, often used in Agile and Lean metrics to measure efficiency.
Cumulative Flow Diagram (CFD) - A visual representation of work in progress, showing the status of tasks over time in Agile project management.
Capability Maturity Model (CMM) - A framework that assesses the maturity of an organization’s processes, often used in project management to evaluate capabilities and define improvement paths.
Capital Expenditure (CapEx) - Funds used by an organization to acquire, upgrade, and maintain physical assets such as property, technology, or equipment, often linked to project investments.
Case Study - A documented analysis of a completed project or initiative used to extract lessons learned and best practices.
Change Control - The formal process of evaluating, approving, and managing changes to project scope, schedule, or cost.
Change Management - The structured approach to transitioning individuals, teams, and organizations from a current state to a desired future state, often accompanying project delivery.
Charter - See Project Charter. A foundational document authorizing a project’s existence.
Checksheet - A simple quality control tool used to collect data in real time at the location where it is generated.
Closeout - The final phase of a project, including administrative closure, documentation, lessons learned, and stakeholder acceptance.
Coaching - A leadership technique for guiding and developing project team members to achieve better performance.
Collaboration Tools - Software or platforms (e.g., Jira, MS Teams, Confluence) used to facilitate communication and teamwork in projects.
Collective Ownership - An Agile principle where the entire team shares responsibility for code, deliverables, and outcomes.
Communications Management Plan - A component of the project management plan that defines how, when, and by whom information will be shared.
Competence Baseline (ICB) - Defined by IPMA, it provides a reference framework of project management competencies.
Compliance Audit - A review performed to ensure project activities and deliverables meet regulatory, contractual, and organizational requirements.
Configuration Management - A process ensuring that project deliverables and documentation are consistent, controlled, and traceable.
Constraint - A limiting factor that affects project execution, such as time, cost, scope, resources, or technology.
Contingency Reserve - Funds, time, or resources set aside to address identified risks that may occur.
Continuous Delivery (CD) - An Agile/DevOps practice of frequently releasing small, tested increments of software into production.
Continuous Improvement (Kaizen) - An ongoing effort to improve products, services, or processes incrementally.
Contract - A legally binding agreement between buyer and seller that defines project deliverables, terms, and responsibilities.
Contract Management - The process of managing contracts to ensure compliance and performance.
Control Account - A management control point where scope, budget, schedule, and performance are integrated and compared.
Corrective Action - An intentional activity undertaken to bring future project performance back in line with the plan.
Cost Baseline - The approved budget, excluding management reserves, used to measure and monitor cost performance.
Cost Management Plan - A component of the project management plan that defines how costs will be estimated, budgeted, managed, and controlled.
Cost Performance Index (CPI) - An earned value metric that measures cost efficiency by dividing earned value (EV) by actual cost (AC).
Cost Variance (CV) - The difference between earned value (EV) and actual cost (AC), used to assess project cost performance.
Critical Chain Method (CCM) - A schedule method that considers resource constraints and buffers to manage uncertainties.
Critical Path Method (CPM) - A scheduling technique that determines the longest path of dependent tasks and defines the shortest time in which a project can be completed.
Critical Success Factor (CSF) - A key element necessary for project success, often tied to stakeholder expectations or organizational strategy.
Cross-Functional Team - A project team composed of members with different expertise working collaboratively toward project goals.
Customer Requirements - The documented needs and expectations of the client or end users that the project must satisfy.
Cycle Time - The total elapsed time required to complete one iteration of a process, task, or deliverable.
Cynefin Framework - A decision-making framework that helps leaders identify the complexity of a situation and choose the appropriate management style.

Deliverable - A tangible or intangible output produced as a result of project activities, which must meet defined acceptance criteria.
Dependencies - The relationships between project activities, indicating the order in which tasks must be performed.
Duration - The total time required to complete a task or activity, often calculated in working days or hours.
Decision Tree - A diagram representing decisions, chance events, and outcomes used to evaluate risk and make informed project decisions.
Drift - Unintended deviation from the project plan or baseline, often requiring corrective action to realign objectives.
Document Management - A structured system to capture, store, retrieve, and track project documents and artifacts.
Dynamic Estimating - An estimation technique that adapts as more information becomes available, commonly used in Agile environments.
Drawdown - The process of gradually utilizing allocated budget or resources over the project life cycle.
Dotted-Line Reporting - A reporting structure where a team member reports to multiple managers, typically a functional and project manager.
Due Date - The specific date by which a project task or deliverable must be completed.
Daily Standup - A short, recurring meeting in Agile teams to review progress, identify blockers, and plan work for the day.
Dashboard - A visual interface displaying key project metrics and performance indicators for stakeholders and managers.
Decomposition - The process of breaking down project deliverables into smaller, manageable components, often used in creating a WBS.
Dependency Matrix - A tool used to document and visualize the relationships between project tasks, helping to identify critical paths and potential bottlenecks.
Duration Estimating - The process of predicting the time required to complete project activities, considering resources, effort, and dependencies.
Design Review - A formal evaluation of project designs to ensure compliance with requirements and standards before implementation.
Discretionary Dependency - A task relationship that is defined based on best practices or preferences rather than mandatory constraints.
Dynamic Risk Assessment - An ongoing evaluation of risks as the project progresses, ensuring timely response to emerging issues.

Earned Value (EV) - A measure of work performed expressed in terms of the approved budget assigned to that work, used in Earned Value Management to assess project performance.
Earned Value Management (EVM) - A project management technique that integrates scope, schedule, and cost parameters to assess project performance and progress.
Effort - The amount of labor required to complete a task or activity, usually measured in person-hours or person-days.
Estimate - An approximation of the time, cost, or resources required to complete project activities.
Estimating Techniques - Methods used to predict project costs, durations, or resource requirements, such as expert judgment, analogous estimating, parametric estimating, and three-point estimating.
Exit Criteria - The conditions that must be met before a project phase, milestone, or deliverable can be considered complete.
Exception Report - A document highlighting deviations from the project plan, such as cost overruns, schedule delays, or quality issues.
Executive Sponsor - A senior-level individual responsible for championing the project, providing guidance, and ensuring alignment with organizational strategy.
Exploit Risk Response - A strategy to maximize the probability or impact of an opportunity by actively taking measures to ensure it occurs.
Express Lane - A fast-tracking technique in project scheduling to accelerate critical tasks without violating dependencies.
External Dependency - A dependency between project tasks and factors outside the project team’s control, such as vendor deliverables or regulatory approvals.
Expert Judgment - The use of specialized knowledge or experience to guide project decisions, assessments, or estimates.
Escalation Procedure - A defined process for escalating unresolved issues or risks to higher authority levels for resolution.
Estimation Accuracy - A measure of how closely estimates match actual outcomes, often tracked to improve future project forecasting.
Event Chain Methodology - A risk management technique that visualizes the cause-and-effect relationships of events affecting project schedules.
Early Start (ES) - The earliest possible point in time an activity can begin, determined using critical path or network analysis.
Early Finish (EF) - The earliest possible point in time an activity can be completed, considering dependencies and durations.
Earned Schedule (ES) - An extension of Earned Value Management that measures schedule performance by comparing planned and actual progress.

Feasibility Study - An analysis conducted to determine the viability of a proposed project, considering technical, financial, legal, and operational factors.
Float The amount - of time a task can be delayed without affecting the overall project schedule. Includes total float and free float.
Forecast - A projection of future project performance based on current data, trends, and assumptions.
Functional Requirements - Detailed descriptions of the specific behaviors or functions the project deliverables must perform to meet business objectives.
Function Point Analysis - A method of measuring software size and complexity based on functionality delivered to the user, used for estimating effort and cost.
Funding Limit Reconciliation - The process of comparing the project budget to available funding and adjusting expenditure plans accordingly.
Framework - A structured approach or set of guidelines for managing projects, such as Agile, PRINCE2, or PMBOK.
Free Float - The amount of time an activity can be delayed without delaying its successor activity.
Fast Tracking - A schedule compression technique where tasks normally done in sequence are performed in parallel to reduce overall project duration.
Functional Manager - A manager responsible for specific organizational functions and the allocation of resources to projects.
Failure Mode and Effects Analysis (FMEA) - A systematic method for evaluating potential failure modes in processes or deliverables and their effects on project objectives.
Forward Pass - A technique in critical path method to calculate the earliest start and finish times for project activities.
Forecast Accuracy - A metric measuring how close predicted project outcomes (cost, time, scope) are to actual results.
Facilitation - The act of guiding discussions, meetings, or workshops to ensure productive outcomes and consensus among stakeholders.
Functional Decomposition - Breaking down complex systems or deliverables into simpler, manageable components for analysis and planning.
Feature-Driven Development (FDD) - An Agile methodology focused on delivering client-valued features in short, iterative cycles.
Full-time Equivalent (FTE) - A measurement representing the workload of one full-time employee, used in resource planning and allocation.

Gantt Chart - A bar chart used to illustrate a project schedule, showing the start and finish dates of tasks and their dependencies. Useful for planning, monitoring, and communicating project timelines.
Governance - The framework, functions, and processes that guide project decision-making, accountability, and performance.
Goal - A broad primary outcome a project seeks to achieve, providing strategic direction.
Gap Analysis - A method to identify differences between current and desired project or organizational performance, informing planning and improvement strategies.
Graphical Evaluation and Review Technique (GERT) - A network analysis technique that allows probabilistic treatment of both network logic and activity duration, used in complex project scheduling.
Ground Rules - Agreed-upon norms, behaviors, and expectations that govern team interactions and project activities.
Green Project - A project focused on sustainable practices and environmental impact reduction.
Guideline - A recommended approach or principle for performing project activities, supporting consistency and quality.
Governance Board - A group of individuals responsible for overseeing project compliance with organizational standards and strategic objectives.
Group Decision-Making - A process where a team or stakeholder group collectively evaluates options and makes project-related decisions.
Graphical Representation - Visual illustrations such as charts, diagrams, or dashboards used to communicate project information.
Growth Metrics - Indicators used to measure the expansion or development of project outcomes, benefits, or organizational impact.
Groundwork Phase - An initial stage in some methodologies focusing on establishing project foundations, such as objectives, resources, and stakeholder alignment.

Histogram - A graphical representation showing the distribution of data or resources, often used to visualize workloads, resource allocation, or frequency of events.
Hybrid Project Management - A methodology combining elements of Agile and traditional project management to leverage the benefits of both approaches.
Handover - The formal transfer of project deliverables, documentation, or responsibilities from one team or phase to another.
High-Level Requirements - Broad, strategic requirements that define what the project aims to achieve without detailed specifications.
Human Resource Management - The processes and activities involved in planning, acquiring, developing, and managing the project team.
Hypercare - A post-implementation support phase where the project team provides close monitoring and immediate response to issues after deployment.
Heuristic - A rule-of-thumb or practical method used to guide project decision-making, estimation, or problem-solving.
Hold Point - A point in the project process where work must pause until a specific condition is met or approval is obtained.
Historical Information - Past project data, records, and lessons learned used as references for planning, estimating, and risk management.
Health Check - An evaluation of project performance, processes, and risk exposure to identify issues and improvement opportunities.
Hybrid Team - A team composed of members following different methodologies or working from different locations and structures, coordinated to achieve project objectives.
Hierarchy Chart - A diagram representing organizational structure, responsibilities, or task decomposition within a project or program.
Handling Change Requests - The process of receiving, evaluating, approving, or rejecting proposed changes to project scope, schedule, or budget.

Impact Analysis - The process of assessing the potential consequences of project changes, risks, or decisions on objectives, schedule, cost, and stakeholders.
Implementation - The phase of a project where plans and designs are executed to deliver the project’s objectives and outputs.
Issue - An unplanned event or problem that affects project objectives, requiring resolution or mitigation.
Iteration - A time-boxed development cycle in Agile projects, where work is planned, executed, reviewed, and adjusted.
Integrated Change Control - A formal process to review, approve, and manage changes across scope, schedule, and cost baselines to maintain project integrity.
Integration Management - Processes and activities that ensure project components are properly coordinated, including plan development, execution, and performance monitoring.
Interface Management - The process of managing interactions, dependencies, and information exchange between project systems, teams, or stakeholders.
Influencer Analysis - Identifying individuals or groups who can impact the project’s success, and assessing their influence and engagement strategies.
Incremental Delivery - Delivering project outputs in small, usable increments, allowing earlier feedback and value realization, common in Agile approaches.
Inspection - A formal review or testing of project deliverables to ensure compliance with specifications, quality standards, and acceptance criteria.
Infrastructure Project - A project focused on physical systems, facilities, or foundational services required to support organizational operations.
Information Radiator - A visible display of project information, metrics, or progress to facilitate transparency and team communication, common in Agile environments.
Iteration Planning - The process of planning the work for a specific Agile iteration, including task selection, estimation, and assignment.

Just-in-Time (JIT) - A lean project management technique that reduces inventory and delivers resources or products only as needed to minimize waste and increase efficiency.
Joint Application Development (JAD) - A collaborative methodology involving workshops with stakeholders to gather requirements and achieve consensus on project objectives.
Judgment Sampling - A non-probabilistic sampling technique where subject matter experts select a sample based on knowledge, commonly used in quality control or auditing.
Job Breakdown Structure (JBS) - A hierarchical decomposition of project activities into smaller, manageable tasks for planning, scheduling, and tracking.
Jumpstart - An initial project activity or meeting designed to accelerate team alignment, clarify objectives, and establish early momentum.
Job Shadowing - A technique for training and knowledge transfer, where team members observe experienced staff performing project tasks.
Joint Review - A collaborative assessment of project deliverables or progress involving multiple stakeholders to ensure alignment and identify issues.
J-curve - A graphical representation showing an initial investment or performance dip followed by improvement, often used in benefit realization or change management.
Job Assignment - The allocation of specific tasks or responsibilities to project team members according to skills, roles, or capacity.
Job Costing - A method to track costs for specific project tasks or activities, enabling detailed financial monitoring and reporting.

Kanban - A visual workflow management method that uses cards, columns, and continuous flow principles to manage tasks and limit work in progress in Agile projects.
Key Performance Indicator (KPI) - A measurable value used to evaluate the success of a project in achieving its objectives, such as schedule adherence or defect rates.
Knowledge Area - A category of project management knowledge defined by PMBOK, representing areas such as scope, cost, schedule, quality, and risk management.
Knowledge Base - A repository of project knowledge, lessons learned, and best practices that can be referenced in future projects.
Kick-off Meeting - An initial meeting with stakeholders and team members to align on project objectives, scope, responsibilities, and timelines.
Key Risk Indicator (KRI) - A metric used to provide an early signal of increasing risk exposure in a project, allowing proactive risk management.
Key Stakeholder - An individual or group with significant influence over project outcomes or with interests directly affected by project deliverables.
Knowledge Transfer - The process of sharing information, skills, or expertise among project team members or across organizational units.
Key Milestone - A significant event or point in the project schedule used to measure progress and trigger approvals or reviews.
Kill Point - A decision point at which a project may be terminated if it is no longer viable or aligned with organizational objectives.
KPI Dashboard - A visual display of key performance indicators to provide stakeholders with real-time insights into project health.
Knowledge Management - A systematic approach to capturing, distributing, and effectively using project knowledge and information.
Kitting - The process of assembling necessary components or resources before they are used in project execution, often used in manufacturing and logistics.
Key Assumption - An important assumption that forms the basis of project planning and decision-making; must be validated and monitored.
Key Deliverable - A critical output of a project phase or the entire project, which must meet specific acceptance criteria.
Knock-on Effect - The subsequent impact of a delay, change, or risk on other project tasks or deliverables, often analyzed in dependency management.
Knowledge Repository - A centralized storage system for documents, best practices, lessons learned, and templates to support organizational learning.
Key Decision Point - A formal stage in project governance where stakeholders assess progress and authorize continuation, changes, or termination.

Lean - A methodology focused on maximizing value while minimizing waste in project processes, emphasizing efficiency and continuous improvement.
Lessons Learned - Documented knowledge gained from project experiences, highlighting successes, challenges, and recommendations for future projects.
Lifecycle - The series of phases a project goes through from initiation to closure, including planning, execution, monitoring, and completion.
Logframe (Logical Framework) - A structured planning tool used to define project objectives, indicators, assumptions, and activities in a clear hierarchy.
Lead Time - The total time required to complete a task or deliverable from initiation to completion, including wait periods.
Lag - A delay or waiting period inserted between project activities to account for dependencies or constraints.
Level of Effort (LOE) - Work that supports the project but is measured in duration rather than discrete deliverables, such as project management activities.
Limit of Authority - The boundaries within which a project manager or team member can make decisions without additional approval.
Linear Responsibility Chart (LRC) - A visual representation of roles and responsibilities for project tasks, similar to a RACI chart.
Logical Relationship - The dependency between two project activities, such as finish-to-start, start-to-start, finish-to-finish, or start-to-finish.
Low-Hanging Fruit - Tasks or opportunities that are easy to accomplish and yield quick, visible benefits.
Lean Six Sigma - A methodology combining Lean principles and Six Sigma quality management techniques to improve processes and reduce defects.
Limit of Performance - The maximum capacity or capability of a resource, team, or system to perform a task within the project.
Long Lead Item - A critical item or resource with a long procurement or manufacturing time that may affect project scheduling.
Lessons Learned Repository - A centralized system for storing, categorizing, and retrieving lessons learned from projects for organizational knowledge retention.
Load Balancing - The process of distributing work evenly among resources to optimize efficiency and avoid overloading individuals or teams.

Milestone - A significant event or point in the project schedule used to monitor progress and mark the completion of key deliverables or phases.
Monitoring and Controlling - The process group in project management that tracks, reviews, and regulates project performance to ensure alignment with the plan.
Management Reserve - An allocated portion of the project budget or schedule set aside for unforeseen work or risks, controlled by senior management.
Matrix Organization - An organizational structure in which team members report to both a functional manager and a project manager.
Monte Carlo Simulation - A quantitative risk analysis technique that uses random sampling to model potential project outcomes and assess probability distributions.
Methodology - A structured approach or system of practices, procedures, and rules used to manage and deliver projects.
Modularity - The design principle of breaking down systems or deliverables into independent, interchangeable components to simplify management.
Meeting Minutes - A documented record of discussions, decisions, and action items from project meetings.
Multi-Project Management - The practice of managing multiple projects simultaneously, including prioritization, resource allocation, and inter-project dependencies.
Metrics - Quantitative measures used to assess project performance, quality, progress, and efficiency.
Management by Exception - A governance principle where project managers report only significant deviations from the plan, allowing senior management to focus on critical issues.
Mind Mapping - A visual technique to organize ideas, concepts, and tasks hierarchically for planning, brainstorming, or problem-solving.
Mandatory Dependency - A relationship between tasks that must occur due to contractual, legal, or physical constraints.
Milestone Chart - A visual representation of key project milestones plotted along a timeline to track progress and deadlines.
Monte Carlo Analysis - A risk management method using repeated random sampling to predict project schedule or cost variability and uncertainty.
Motivation Plan - A strategy to encourage and maintain team engagement, commitment, and high performance throughout the project.

Network Diagram - A graphical representation of project activities and their dependencies, used for scheduling and critical path analysis.
Non-Conformance - Any instance where project deliverables or processes fail to meet specified requirements or standards.
Nominal Group Technique (NGT) - A structured group brainstorming method used to prioritize ideas, requirements, or solutions by achieving consensus.
Non-Recurring Costs - One-time expenses associated with a project, such as equipment purchase, initial setup, or training.
Needs Assessment - A process for identifying gaps between current conditions and desired outcomes to determine project objectives and priorities.
Negative Risk - A potential event that could have an adverse impact on project objectives, also known simply as a threat.
Node - A point in a network diagram representing the start or finish of an activity, milestone, or event.
Nominal Estimating - An estimation approach that uses standard or predefined values for activities when detailed information is not yet available.
NPV (Net Present Value) - A financial metric used to evaluate the value of a project by discounting future cash flows to present value and subtracting initial investment.
Negotiation Plan - A strategy outlining approaches, objectives, and tactics for resolving conflicts, securing resources, or reaching agreements in projects.
Non-Functional Requirements - Criteria specifying how a system must operate, such as performance, usability, reliability, or security standards.
Network Logic - The sequence and dependencies that determine the order of project activities in a network diagram.
Near-Critical Path - A sequence of activities not on the critical path but with minimal float, potentially affecting the overall schedule if delayed.
Non-Disclosure Agreement (NDA) - A legal contract ensuring confidentiality of project information between parties.
Nominal Team Size - The planned or standard number of team members assigned to a project for optimal performance.

Objective - A specific, measurable outcome that a project aims to achieve within defined time, cost, and quality constraints.
Off-the-Shelf Solution - A ready-made product or system used to meet project requirements without custom development.
Opportunity - A potential positive event or condition that, if exploited, can enhance project outcomes or benefits.
Organizational Breakdown Structure (OBS) - A hierarchical representation of the project organization that shows reporting relationships and responsibilities.
Outcome - The result or effect of project deliverables, focusing on value realization and benefits rather than just outputs.
Output - A tangible or intangible product, service, or result produced by project activities.
Overrun - An excess in project cost, schedule, or resource usage beyond planned estimates.
Oversight - The process of monitoring and supervising project activities to ensure compliance with standards, policies, and objectives.
Option Analysis - A decision-making technique that evaluates multiple alternatives to select the best approach for achieving project objectives.
Ownership - The assignment of responsibility and accountability for project deliverables, decisions, or processes.
Operational Risk - The risk of loss due to inadequate internal processes, people, systems, or external events affecting project performance.
Organization Process Assets (OPA) - Organizational resources, templates, guidelines, and historical information that support project planning and execution.
Opportunity Register - A document listing potential opportunities, their likelihood, impact, and planned responses to maximize benefits.
Overlapping Activities - Tasks scheduled to occur concurrently to compress project duration, often used in fast-tracking techniques.
Out-of-Scope Work - Activities or deliverables that are not included in the project scope and require separate approval or management.

Pareto Principle: The concept that 80% of effects come from 20% of causes, used in project risk and quality management.
Performance Measurement Baseline (PMB): The approved plan for scope, schedule, and cost against which project performance is measured.
Portfolio: A collection of projects, programs, and operations managed to achieve strategic objectives.
Program: A group of related projects managed in a coordinated way to obtain benefits not available from managing them individually.
Project Charter: A document that formally authorizes a project and defines its objectives, scope, and participants.
Project Management Office (PMO): An organizational unit responsible for defining project management standards, providing governance, and supporting project execution.
Progressive Elaboration: Developing project details iteratively as more information becomes available.
Project Scope Statement: A detailed description of project deliverables, boundaries, and acceptance criteria.

Quality Assurance (QA): The process of auditing and evaluating project processes to ensure they meet defined quality standards.
Quality Control (QC): Monitoring specific project results to ensure that they comply with quality requirements.
Quality Management Plan: A document defining the quality standards, roles, responsibilities, and processes for quality management.
Quantitative Risk Analysis: A numerical assessment of the probability and impact of identified risks on project objectives.

Risk: An uncertain event or condition that, if it occurs, has a positive or negative effect on project objectives.
Risk Register: A document containing details of identified risks, their assessments, and planned responses.
Resource Allocation: Assigning available resources to project tasks in a way that optimizes productivity.
Responsibility Assignment Matrix (RAM): A table linking project tasks to responsible individuals or groups (e.g., RACI chart).
Requirements Traceability Matrix: A grid that links requirements to deliverables, ensuring all requirements are fulfilled.

Stakeholder: Any individual, group, or organization that may affect or be affected by project outcomes.
Scope Creep: Uncontrolled changes or continuous growth in project scope without proper approval.
Schedule Baseline: The approved version of the project schedule used to monitor project progress.
Scrum: An Agile framework for iterative development, emphasizing collaboration, accountability, and incremental delivery.
Sprint: A fixed-length iteration in Agile frameworks where a set of work is completed and reviewed.
Six Sigma: A methodology focused on process improvement and reducing defects.

Triple Constraint: The balance of project scope, time, and cost, where changes to one affect the others.
Team Charter: A document that defines team purpose, roles, responsibilities, and operational guidelines.
Task: A discrete unit of work within a project, often assigned to a team member.
Timeboxing: Allocating a fixed period to complete a task or activity, commonly used in Agile practices.
Total Quality Management (TQM): A management approach focused on continuous improvement in processes, products, and services.

Use Case: A description of how a system interacts with users or other systems to achieve a specific goal.
User Story: A short, simple description of a software feature from the perspective of the end user, common in Agile.
Urgent Risk: A risk requiring immediate attention due to its potential impact on project objectives.
Uncertainty: The state of having incomplete knowledge about potential events affecting project outcomes.

Variance: The difference between planned and actual performance in cost, schedule, or scope.
Value Engineering: A systematic approach to improving the value of a project by analyzing functions and reducing unnecessary costs.
Visual Management: The use of visual signals, dashboards, and charts to communicate project status and performance.
Verification: Ensuring that deliverables meet specified requirements through inspections, testing, or reviews.

Work Breakdown Structure (WBS): A hierarchical decomposition of project deliverables into smaller, manageable components.
Work Package: A group of related tasks within a WBS that can be assigned and tracked as a unit.
Workflow: The sequence of processes, tasks, or activities required to complete project work.
Weighted Scoring Model: A tool for prioritizing projects or features by assigning weights and scores based on criteria.
Weekly Status Report: A regular report summarizing project progress, risks, issues, and upcoming activities.

XP (Extreme Programming): An Agile software development methodology emphasizing technical excellence, frequent releases, and customer collaboration.
XML in Project Documentation: Using XML to structure, share, and store project information digitally for interoperability.

Y-axis Analysis: A method for analyzing project performance trends or metrics along the vertical axis in charts.
Yield: The measure of output or results achieved relative to inputs or expected targets in project activities.

Zero Defects: A quality management philosophy aiming for no defects in deliverables, emphasizing prevention over inspection.
Z-Chart: A visual tool to monitor progress, resource allocation, or performance trends in project management.
Zoning: Dividing project activities, resources, or responsibilities into segments or zones for better control and clarity.