Introduction

Introduction (PM Standard, Section 1)

PMBOK 8 opens its Standard for Project Management by defining the work — what a project is, what value means, how projects sit inside organizational governance, and how portfolios/programs/projects/operations relate. This section sets the foundation for the six principles that follow.

Key terms (§ 1.2)

PMBOK 8 formal definitions:

• Project success — the consensus view across intended beneficiaries, other stakeholders, and project participants that a project was perceived to have delivered value that was worth the effort and expense.
• Project team — a set of individuals performing the work of the project to achieve its objectives.
• Value — the excess of financial and nonfinancial benefits over investment that is gained from achieving the goals of a portfolio, program, or project. Stakeholders perceive value differently: organizations use performance metrics or financial measures like ROI; customers may value convenience; governments and NGOs prioritize societal and environmental impact.
• Value delivery system — a collection of strategic business activities aimed at building, sustaining, and/or advancing an organization. Portfolios, programs, projects, products, and operations can all be part of an organization’s system for value delivery.

See the PMI Lexicon of Project Management Terms for additional definitions.

---

Foundational Elements (§ 1.3)

Characteristics of a project (§ 1.3.1)

Temporary

Projects have a defined beginning and end. The deliverables often persist long after, but the project itself does not. A project ends when one or more of these five conditions are met:

1. The project’s objectives have been achieved.
2. A governing body, the project sponsor, or the project team has determined that the objectives will not or cannot be met.
3. Resources (funding, human, or physical) are exhausted or no longer available.
4. Due to changes in strategy, priorities, or the external environment, the need for the project no longer exists.
5. The project is terminated for other reasons such as legal, regulatory, or compliance issues.

Unique context

Even projects that look alike differ in goals, scope, duration, location, technology, quality, costs, risks, resources, and stakeholders. Each project’s unique context demands a tailored management approach. PMBOK’s housing-development example: a builder may produce 50 homes in the same district, but each unit has different lenders, buyers, customizations, and grading — every project is unique.

Value creation through organizational change

A project drives change. From a business perspective, a project moves the organization from a Current State (before the project) to a Future State (after the project delivers value). Some projects pass through an intermediate Transition State — a set of structured steps that bridge current and future. The project succeeds when the organization reaches the future state and key stakeholders see the intended value.

Organizational governance vs. project governance (§ 1.3.2)

Two distinct concepts, both essential.

Organizational governance provides direction and control through policies, processes, procedures, and decisions to meet strategic and operational goals. Typically overseen by an executive committee. It influences portfolios/programs/projects in six ways:

• Enforcing legal, regulatory, and compliance requirements
• Defining ethical, social, and environmental responsibilities
• Specifying operational, legal, financial, and risk policies
• Promoting alignment with strategic objectives at different hierarchical levels
• Ensuring that initiatives contribute to organizational mission and vision
• Facilitating decision-making that maximizes delivered value through the value delivery system

Project governance is the adaptable framework that guides project management activities to create value through a unique product, service, or result. It provides structure, systems and processes, roles, responsibilities, and decision-making models — examples include RACI (responsible, accountable, consulted, informed) matrices and governance boards or steering committees. Project governance also defines accountability and communication protocols.

In short: organizational governance directs the whole organization; project governance focuses on managing individual projects. The detailed performance-domain treatment lives in Governance Domain.

Project initiation (§ 1.3.2.1)

Organizational leaders authorize projects in response to strategic objectives and stakeholder needs, which fall into four categories:

• Meeting regulatory, legal, or social requirements
• Satisfying stakeholder requests or needs
• Implementing or changing business or technological strategies
• Creating, improving, or fixing products, processes, organizations, or services

Projects ultimately link back to organizational strategic objectives and business value.

Operations and project management (§ 1.3.3)

Operations management focuses on the efficient, effective production of products and services — managing processes that transform inputs (materials, components, energy, labor) into outputs (products, goods, services, results). Operations are ongoing; projects are temporary. They are distinct disciplines.

But they intersect at specific points in a product’s life cycle:

• When developing new products or services, upgrading offerings, or expanding outputs
• While improving product or service delivery operations or their development process
• At the end of the product life cycle
• At each closeout phase or iteration

At hand-off, deliverables, human resources, and knowledge transfer between project and operations to ensure seamless integration. Engaging operations teams early in project planning is beneficial and significantly influences long-term project success.

Portfolio, program, project, and operations (§ 1.3.4)

Projects can stand alone, be grouped into programs (related projects managed coordinately for benefits unavailable from independent management — programs drive significant organizational change, not just “big projects”), or sit within a portfolio (a collection of programs, projects, and operations managed as a group to maximize value, meet mandatory obligations, or generate income). Portfolio management selects, prioritizes, and optimizes the organization’s programs and projects in line with strategy.

Portfolios, programs, projects, and operations often engage the same stakeholders and compete for the same resources — their managers must coordinate to keep resource allocation and stakeholder engagement balanced. See Organizational Project Management (OPM) for the integrating framework.

Table 1-1 — Comparative overview (PMBOK 8):

Dimension	Portfolios	Programs	Projects
Definition	A collection of programs, projects, and operations managed as a group to maximize value delivery and achieve strategic objectives, meet mandatory obligations, or generate income streams	A group of related projects and program activities managed in a coordinated manner to obtain benefits not available from managing them individually	A temporary initiative in a unique context undertaken to create value
Scope	Organizational scope aligned with strategic objectives	Includes and integrates the scope of its component projects and subprograms	Defined objectives, progressively elaborated
Change	Adaptable to continuous monitoring and adjustment to align with strategic priorities and changes in the environment	Adaptable to optimize value delivery at the program level	Adaptable to enable and maximize value delivery
Planning	Strategic planning, priority definition, and resource allocation between programs and projects	High-level planning that tracks interdependencies and aligns with program objectives	Predictive, adaptive, or hybrid, depending on project requirements and organizational context
Monitoring	Monitors strategic changes and resource allocation	Monitors progress of component projects and benefits realization	Monitoring and controlling outputs and value
Success	Strategic value delivery, overall change-management success, alignment with organizational vision and mission	Program’s ability to collectively deliver benefits and value and achieve strategic objectives	Delivered value that was worth the effort and expense — including quality, timeliness, budget compliance, sustainability, and stakeholder satisfaction

---

Related

• Value Delivery System — § 2 deep dive
• Organizational Project Management (OPM)
• Governance Domain — performance-domain treatment of governance
• Business Case
• Benefits Management

Exam angle

• Temporary ≠ short. A 10-year project is still temporary because it has a defined end. Wrong answers conflate “temporary” with “quick.”
• Five ways a project ends — not two. Memorizing only “objectives met” and “terminated” leaves three traps: resources exhausted, need no longer exists, and legal/regulatory/compliance termination. Scenarios that describe an external regulation change forcing project shutdown test condition #5.
• Operations are ongoing, projects are unique-and-temporary. Recurring work (maintenance windows, monthly payroll, customer support) is operations — not a project — even when complex.
• Governance is two layers. Organizational governance directs the whole org; project governance directs the project. Answer choices that mix them up are testing this distinction.
• Programs are not big projects. Programs deliver benefits unavailable from independent projects. If a scenario describes “coordinated benefits realization across several efforts,” the right answer is program.
• Portfolios optimize at the strategic level. Portfolio decisions are about which programs/projects to fund, not how to run them. A “stop this project because strategy changed” decision is a portfolio-level call.
• Engage operations early. Wrong answers wait until handover; right answers engage operations during planning to influence long-term sustainability.