Overview
Project Management Fundamentals and Core Concepts is 36% of the CAPM exam, the largest domain, and the base the other three build on. It has five tasks. Understanding life cycles and processes covers distinguishing projects, programs and portfolios, projects from operations, predictive from adaptive approaches, and issues, risks, assumptions and constraints, plus the code of ethics. Project management planning covers the purpose of cost, quality, risk and schedule, the project versus product management plan, milestones versus task durations, resources, and the risk and stakeholder registers. Roles and responsibilities covers project managers, sponsors and teams, leadership versus management, and emotional intelligence. Following strategies covers responding to planned frameworks and project initiation. Problem-solving covers meetings and techniques such as brainstorming and focus groups.
As an entry-level exam, the CAPM tests understanding of these fundamentals across predictive and adaptive approaches. At 36%, this domain is the most important single area, establishing the vocabulary and concepts used throughout the exam.
How it's tested
CAPM questions are knowledge and scenario questions testing understanding of fundamentals, with formats including multiple choice, drag-and-drop and short animations. In this domain they describe a situation or term and ask which concept, role, plan or technique applies. Read for the precise fundamental being tested, since many questions turn on clear definitions.
-
Define the concept
A term or situation is described, and you identify the project concept, such as project versus program or risk versus issue.
-
Role or plan
A responsibility or planning need is described, and you identify the role or the correct plan or register.
-
Technique or approach
A problem or situation is described, and you choose the problem-solving technique or the predictive-versus-adaptive distinction.
A situation describes something that has already occurred and is currently affecting the project. This is an issue, a present problem, not a risk, which is a potential future event that may or may not occur. Distinguishing the two, an issue is happening now while a risk is still uncertain, is the kind of precise fundamental the CAPM expects, and it also determines how the item would be managed.
Domains 5
Official domains from the PMI outline, in outline order.
1.1 Demonstrate an understanding of the various project life cycles and processesProjects, programs, portfolios, predictive vs adaptive, and core terms.
- What it means
- This covers distinguishing a project from a program and a portfolio, a project from operations, predictive from adaptive approaches, and issues, risks, assumptions and constraints, plus reviewing project scope, applying the code of ethics, and seeing a project as a vehicle for change.
- What to understand
- A project is a temporary effort creating a unique result, a program groups related projects, and a portfolio groups programs and projects for strategic goals. Operations are ongoing. Predictive approaches plan upfront while adaptive approaches iterate. Issues are current problems, risks are potential future events, assumptions are things taken as true, and constraints are limitations. These core distinctions are foundational.
- How it shows up
- A term or situation is described, and you must identify the correct concept or distinction.
- Common confusion
- Confusing projects, programs and portfolios, or issues, risks, assumptions and constraints.
1.2 Demonstrate an understanding of project management planningPlan purposes, project vs product plan, milestones, resources and registers.
- What it means
- This covers the purpose and importance of cost, quality, risk and schedule, distinguishing the project management plan from the product management plan, milestones from task durations, determining resource numbers and types, and using the risk register and stakeholder register, plus project closure and transitions.
- What to understand
- The project management plan describes how the project will be executed and controlled, while the product plan concerns the product itself. A milestone is a point in time with zero duration, while a task has duration. The risk register records risks and responses, and the stakeholder register records stakeholders and their interests. Understanding what each planning element is for is the skill.
- How it shows up
- A planning need is described, and you must identify the correct plan, register, or distinction.
- Common confusion
- Confusing the project management plan with the product management plan, or a milestone with a task duration.
1.3 Demonstrate an understanding of project roles and responsibilitiesProject manager, sponsor, team, leadership vs management, and EQ.
- What it means
- This covers comparing the roles of project managers, sponsors and the project team, explaining the project manager's roles such as initiator, negotiator, coach and facilitator, the difference between leadership and management, and emotional intelligence and its impact on project management.
- What to understand
- The project manager leads and coordinates the project, the sponsor provides funding and high-level support and champions the project, and the team does the work. Leadership inspires and sets direction, while management organizes and controls. Emotional intelligence, understanding and managing emotions, helps the project manager lead and work with people effectively.
- How it shows up
- A responsibility or situation is described, and you must identify the role or the leadership concept.
- Common confusion
- Confusing the sponsor's role with the project manager's, or leadership with management.
1.4 Determine how to follow and execute planned strategies or frameworksResponding to planned strategies, and project initiation and benefits.
- What it means
- This covers giving examples of how to appropriately respond to a planned strategy or framework, such as communication or risk, and explaining project initiation and benefit planning.
- What to understand
- Projects follow planned strategies and frameworks, such as a communication plan or risk strategy, and the project team responds to situations according to these plans rather than improvising. Project initiation defines the project and its justification, and benefit planning identifies the value the project will deliver. Following the plan appropriately is the expected behavior.
- How it shows up
- A situation governed by a planned strategy is described, and you must choose the appropriate response per the plan.
- Common confusion
- Improvising a response rather than following the planned strategy or framework for the situation.
1.5 Demonstrate an understanding of common problem-solving tools and techniquesMeeting effectiveness and techniques such as brainstorming and focus groups.
- What it means
- This covers evaluating the effectiveness of a meeting and explaining the purpose of techniques such as focus groups, standup meetings and brainstorming, as common problem-solving and collaboration tools.
- What to understand
- Different techniques suit different needs: brainstorming generates many ideas, focus groups gather targeted feedback, and standup meetings give quick status in agile. Effective meetings have a purpose, agenda and the right participants. Knowing the purpose of each technique and what makes a meeting effective is the expected knowledge.
- How it shows up
- A collaboration or problem-solving need is described, and you must choose the appropriate technique.
- Common confusion
- Confusing the purposes of techniques such as brainstorming (idea generation) and focus groups (targeted feedback).
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Project vs. program vs. portfolio
A unique effort, related projects, and strategic grouping.
- Remember
- Portfolios align to strategy, programs group related projects.
- Tested as
- Core concept questions.
- Trap
- Confusing the three.
-
Project vs. operations
Temporary unique effort versus ongoing work.
- Remember
- Projects are temporary; operations are ongoing.
- Tested as
- Core concept questions.
- Trap
- Treating ongoing work as a project.
-
Predictive vs. adaptive
Plan upfront versus iterate.
- Remember
- Adaptive suits changing requirements.
- Tested as
- Approach questions.
- Trap
- Confusing the two approaches.
-
Issue vs. risk
Current problem versus potential future event.
- Remember
- A risk that occurs becomes an issue.
- Tested as
- Core concept questions.
- Trap
- Confusing the two.
-
Assumption vs. constraint
Something taken as true versus a limitation.
- Remember
- Assumptions are believed; constraints restrict.
- Tested as
- Core concept questions.
- Trap
- Confusing the two.
-
Project vs. product management plan
How the project runs versus the product itself.
- Remember
- The project plan governs execution and control.
- Tested as
- Planning questions.
- Trap
- Confusing the two plans.
-
Milestone vs. task duration
A zero-duration point versus work with duration.
- Remember
- Milestones mark events, not effort.
- Tested as
- Planning questions.
- Trap
- Giving a milestone duration.
-
Risk and stakeholder registers
Records of risks and of stakeholders.
- Remember
- Each tracks its items and attributes.
- Tested as
- Planning questions.
- Trap
- Confusing the registers.
-
Sponsor vs. project manager
Funds and champions versus leads and coordinates.
- Remember
- The sponsor provides support and resources.
- Tested as
- Role questions.
- Trap
- Confusing the two roles.
-
Leadership vs. management
Inspiring and directing versus organizing and controlling.
- Remember
- Both are needed.
- Tested as
- Role questions.
- Trap
- Confusing the two.
-
Emotional intelligence
Understanding and managing emotions.
- Remember
- It improves leading and collaboration.
- Tested as
- Role questions.
- Trap
- Overlooking its project impact.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Project vs. program vs. portfolio
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Project | A temporary, unique effort | Creates a specific result | Confusing with a program |
| Program | Related projects managed together | Coordinated benefits | Confusing with a portfolio |
| Portfolio | Projects and programs for strategy | Aligned to objectives | Confusing with a program |
Issue vs. risk vs. assumption vs. constraint
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Issue | A current problem | Happening now | Confusing with a risk |
| Risk | A potential future event | May or may not occur | Confusing with an issue |
| Assumption / constraint | Taken as true / a limitation | Believed versus restricts | Confusing the two |
Milestone vs. task
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Milestone | A significant point in time | Zero duration | Giving it duration |
| Task | Work to be performed | Has duration and effort | Confusing with a milestone |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Risk is an issue
- What candidates pick
- Call a potential future event an issue.
- Why it looks right
- Both are problems.
- Why it's wrong
- An issue is a current problem; a risk is a potential future event that may or may not occur.
Clue to watch for The event has already happened versus might happen.
-
Program is a big project
- What candidates pick
- Treat a program as simply a large project.
- Why it looks right
- Both involve multiple deliverables.
- Why it's wrong
- A program is a group of related projects managed together for coordinated benefits, not one large project.
Clue to watch for Multiple related projects are managed for combined benefits.
-
Milestone has duration
- What candidates pick
- Assign a duration to a milestone.
- Why it looks right
- It appears on the schedule.
- Why it's wrong
- A milestone is a point in time with zero duration marking an event; a task has duration.
Clue to watch for The item marks an event rather than work.
-
Sponsor manages day to day
- What candidates pick
- Expect the sponsor to manage the project's daily work.
- Why it looks right
- The sponsor is senior.
- Why it's wrong
- The sponsor funds and champions the project; the project manager leads the day-to-day work.
Clue to watch for The task is day-to-day coordination versus funding and support.
-
Assumption is a constraint
- What candidates pick
- Treat something taken as true as a constraint.
- Why it looks right
- Both affect planning.
- Why it's wrong
- An assumption is believed true without proof; a constraint is a real limitation such as budget or time.
Clue to watch for The item is believed versus an actual restriction.
-
Leadership equals management
- What candidates pick
- Use leadership and management interchangeably.
- Why it looks right
- Both involve directing others.
- Why it's wrong
- Leadership inspires and sets direction; management organizes and controls. Projects need both.
Clue to watch for The need is to inspire and align versus organize and control.
Answer framework
For any Domain 1 fundamentals scenario, use these steps to find the answer the CAPM expects.
- Identify which fundamental the question tests: a life-cycle concept, planning, roles, strategy, or problem-solving.
- For core concepts, apply precise definitions, distinguishing project, program and portfolio and issue, risk, assumption and constraint.
- For planning, choose the correct plan, register or element, separating the project from the product management plan and milestones from tasks.
- For roles, assign responsibilities correctly, keeping sponsor, project manager and team distinct and leadership separate from management.
- For strategy and problem-solving, follow the planned framework and choose the technique that fits the need. Where two options seem to fit, choose the one that most precisely matches the textbook definition the question is testing.
Practice question
Want more like this? The CAPM practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Treat this domain as learning the fundamental vocabulary the whole CAPM assumes, and get the definitions exactly right, since many questions turn on precise distinctions. Start with the core concepts that are most confused: project versus program versus portfolio, project versus operations, and especially issue versus risk versus assumption versus constraint, which recur throughout the exam.
Next, learn the planning fundamentals, keeping the project management plan distinct from the product management plan and a milestone distinct from a task, and know what the risk and stakeholder registers hold. Learn the roles clearly, separating sponsor, project manager and team, and leadership from management, and understand emotional intelligence. Then learn the problem-solving techniques and what makes a meeting effective.
Because the CAPM is a knowledge exam, flashcards and practice questions on these definitions are highly effective. As this is the largest domain and the foundation, invest the most time here. Afterwards, move to Domain 2, Predictive, Plan-Based Methodologies.
FAQ
How much of the CAPM is Domain 1?
Project Management Fundamentals and Core Concepts is 36% of the exam, the largest domain, and it establishes the fundamentals the other three domains build on.
What is the difference between a project, a program and a portfolio?
A project is a temporary effort creating a unique result. A program is a group of related projects managed together for coordinated benefits. A portfolio is a collection of projects and programs aligned to strategic objectives.
What is the difference between an issue and a risk?
A risk is a potential future event that may or may not occur. An issue is a current problem that has already occurred and is affecting the project. A risk that materializes becomes an issue.
What is the difference between the project and product management plan?
The project management plan describes how the project will be executed, monitored and controlled. The product management plan concerns the product itself. The CAPM tests distinguishing the two.
What is the difference between a milestone and a task?
A milestone is a significant point in time with zero duration, marking an event such as a phase completion. A task is work that has duration and consumes effort.
What is the difference between leadership and management?
Leadership inspires, motivates and sets direction, while management organizes, plans and controls. Both are needed in project management, and the CAPM tests distinguishing them.
How does Domain 1 connect to the rest of the exam?
These fundamentals underpin the predictive, agile and business analysis domains, which all assume you understand the core concepts, planning, roles and techniques established here.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- CompTIA Project+ Same subject: Domain 1: Project Management Concepts (33%)
- PRINCE2 7 Practitioner Study guide
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- Project Management Professional Study guide
- PRINCE2 7 Foundation Study guide
- Portfolio Management Professional Study guide
- Program Management Professional Study guide
- Agile Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Project Management Professional (PMBOK 7) Study guide
- Disciplined Agile Scrum Master Study guide
Test your Domain 1 knowledge
You have covered life cycles, planning, roles, strategies and problem-solving. Test whether you can apply these fundamentals precisely under exam conditions.