CAPM Domain 1 opens with a foundational distinction PMI expects a candidate to make instantly: is a described piece of work a project, a program, or a portfolio? Getting this right underpins nearly everything else on the exam, because governance, roles, and success measures all differ across the three.
What Makes Something a Project
A project is a temporary endeavor undertaken to create a unique product, service, or result. Temporary means it has a definite beginning and end (not literally short -- a project can run for years) and ends when its objectives are met, when it's terminated because objectives can't or won't be met, or when the need for the project no longer exists. Unique means the deliverable differs in some distinguishing way from other similar deliverables -- even a repeated type of project (building the tenth branch office of an identical design) still counts, because the location, team, stakeholders, and circumstances differ each time.
Programs: Coordinated Groups of Related Projects
A program is a group of related projects, subsidiary programs, and program activities managed in a coordinated manner to obtain benefits not available from managing them individually. The word "related" matters: a program isn't just a bucket of unrelated projects sharing a budget line -- the projects inside a program are grouped together because coordinating them produces benefits (shared resources, reduced risk, consistent stakeholder communication) that wouldn't exist if each project ran in isolation. A company rolling out a new ERP system across 12 regional offices might run it as a program, where each regional rollout is a project, but coordinating them centrally captures efficiencies none of the 12 would achieve alone.
Portfolios: Grouping for Strategic Alignment
A portfolio is a collection of projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives. Where a program's projects are related to each other operationally, a portfolio's components may be entirely unrelated day-to-day -- they're grouped instead because they all serve the same strategic objective, and portfolio management is fundamentally about prioritization and resource allocation across that whole collection so the organization's limited resources go toward the initiatives that matter most strategically.
Why the Distinction Matters on the Exam
PMI scenario questions test this by describing a situation and asking which term fits, or by asking what changes when something is managed as a program rather than as a set of standalone projects. The scale ordering is portfolio > program > project, and a portfolio can contain both programs and stand-alone projects and even ongoing operational work, not just projects.
Key Mechanics
- A project is temporary (definite start and end) and produces a unique product, service, or result.
- A program is a group of related projects and program activities, managed together to gain benefits unavailable from managing them individually.
- A portfolio is a collection of projects, programs, and operations grouped to achieve strategic objectives, prioritized and resourced as a group.
- Relatedness differs by level: program components are operationally related; portfolio components are related only by shared strategic purpose.
- Scale order: a portfolio contains programs and projects; a program contains projects; a project does not contain programs or portfolios.
Exam Tip: If a scenario describes several projects sharing resources and coordinated specifically because coordinating them creates benefits the projects wouldn't get alone, that's a program, not just "multiple projects."
Exam Tip: If a scenario describes grouping unrelated initiatives purely to prioritize and allocate resources toward strategic goals, that's a portfolio -- the components don't need to be operationally related to each other at all.
Exam Tip: A single initiative with a definite end date and a unique deliverable is a project even if it's large, expensive, or multi-year -- "temporary" refers to having a defined end, not to being short.
Worked example: A hospital network is investing in three initiatives: replacing bedside monitors at all 6 hospitals (coordinated because shared vendor negotiation and rollout scheduling produce cost and risk benefits none of the 6 individual replacements would get alone), building a new outpatient clinic (a single unique, temporary undertaking with its own defined end), and continuing routine facility maintenance (ongoing operations, not temporary at all). The organization groups all three under one strategic view to decide how much budget and staff time each deserves relative to the network's strategic goals -- that grouping is the portfolio; the 6 coordinated monitor replacements are the program; the outpatient clinic build is the project; and the routine maintenance is operations, included in the portfolio without being a project itself.