PECB ISO 21502 Lead Project Manager key terms

A temporary endeavor undertaken to create a unique product, service, or result, governed by defined objectives, constraints, and acceptance criteria, and terminated when those objectives are achieved or the endeavor is abandoned.

The application of methods, tools, techniques, and competencies to direct and control project activities so that agreed objectives are met within approved constraints and stakeholder expectations are addressed.

The sequence of phases through which a project evolves from initial concept to final closure, each phase ending with a decision point, deliverable, or review that authorizes the next stage.

A distinct, logically grouped portion of the project life cycle with its own objectives, deliverables, and control arrangements, used to structure work and enable incremental review and approval.

A formal decision point at the end of a phase where authorized stakeholders review achievements and approve, conditionally approve, redirect, pause, or terminate continuation of the project.

The framework of authority, accountability, policies, and decision-making structures that directs how a project is sponsored, overseen, controlled, and held answerable for its performance and outcomes.

The organizational arrangements through which the portfolio of projects is prioritized, resourced, monitored, and aligned with strategic objectives, ensuring consistent oversight across all projects rather than one project alone.

The individual or body accountable for the project at the executive level, securing resources and funding, championing the business case, and making key decisions beyond the project manager's authority.

The person assigned to lead the project team and accountable for achieving project objectives through planning, organizing, directing, and controlling work, while managing stakeholder expectations and constraints.

A documented justification for the project describing the problem or opportunity, expected benefits, costs, risks, and rationale, used to authorize investment and later to judge whether the project remains worthwhile.

The process of ensuring that the improvements and value expected from a project are actually achieved and sustained after deliverables are transferred, often requiring action beyond project closure.

The measurable change or result that the project produces for the organization or users, distinguishing it from the outputs delivered and from the benefits eventually realized from those outputs.

A tangible or intangible output produced by project work that is verifiable and subject to acceptance by the customer or sponsor, often defined at a level suitable for progress measurement.

A document issued by the sponsor that formally authorizes the project, names the project manager, states high-level objectives and boundaries, and conveys authority to apply organizational resources.

The integrated document describing how the project will be executed, monitored, controlled, and closed, consolidating subsidiary plans for scope, schedule, cost, quality, resources, risk, and communication.

An approved, version-controlled reference for scope, schedule, or cost against which actual performance is compared, changed only through formal change control.

Uncontrolled expansion of project scope through small, unapproved additions that erode the baseline, consume contingency, and are typically detected late in the schedule.

A hierarchical decomposition of the total scope of work into manageable components, with the lowest level, work packages, suitable for estimating, scheduling, and assigning responsibility.

The process of reviewing all change requests, assessing their impact on scope, schedule, cost, risk, and quality, and approving, rejecting, or deferring them while communicating decisions to stakeholders.

A formal proposal to modify a document, deliverable, or baseline, which must be logged, evaluated for impact, and decided upon through the agreed change control authority.

The discipline of identifying, recording, controlling, and verifying the versions and status of project items such as documents, designs, and deliverables so that only approved versions are used.

Any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by the project, including those who influence decisions or receive its outputs.

A documented approach describing how each stakeholder group will be informed, consulted, involved, and managed, including methods, frequency, responsibilities, and escalation paths for concerns.

The agreed specification of what information will be distributed to whom, in what format, when, and by what channel, aligned with stakeholder needs and project reporting obligations.

A register of current problems, conflicts, or unresolved matters affecting the project, recording ownership, priority, status, and resolution actions so that none is lost or ignored.

An uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives such as scope, schedule, cost, or quality.

A living record of identified risks with their causes, potential effects, probability and impact assessments, owners, planned responses, and current status, used to direct risk treatment.

A planned action to address an identified risk, such as avoiding, mitigating, transferring, accepting, or exploiting it, selected according to severity and the organization's tolerance.

The amount and type of uncertainty an organization is willing to accept in pursuit of objectives, which sets the threshold for deciding whether a risk requires treatment or can be tolerated.

Time or money set aside in the approved baseline to cover known risks with identified responses, released under defined authority when those risks materialize.

Time or money held outside the approved baseline for unforeseen work within the project scope, released only through senior management authorization, typically for unknown risks.

A performance measurement technique comparing planned value, earned value, and actual cost to quantify schedule and cost variance and forecast likely completion outcomes.

A significant point or event in the project with zero duration, used to mark completion of a key deliverable, a decision, or the start of a new phase.

A periodic account of project status against the baseline, covering achievements, variances, forecasts, issues, and risks, tailored in content and detail to its intended audience.

The group of individuals performing project work under the project manager's direction, whose composition, roles, competencies, and development must be planned and managed throughout.

The documented identification of the people, equipment, materials, and facilities needed for project work, including quantities, timing, sourcing approach, and responsibility assignments.

A defined piece of work with an estimated duration and resource requirement, forming the building block of a schedule and typically derived from a work package.

The planned, systematic activities that provide confidence that project processes and deliverables will meet specified requirements, distinct from the inspection-based verification of finished outputs.

The defined, testable conditions that a deliverable must satisfy for the customer or sponsor to accept it, agreed before work begins to avoid later disputes.

The phase in which deliverables are handed over and accepted, contracts are settled, resources released, records archived, and lessons captured, with formal confirmation that the project is complete.

Knowledge captured from project experiences, both positive and negative, recorded and shared so that future projects and the wider organization benefit from what was discovered.

An organizational unit that provides project-related services such as standards, templates, coaching, portfolio reporting, and assurance, with authority varying from supportive to directive.