FREE CAPM Study Guide 2026: All 4 Domains

This free CAPM study guide walks through everything the Certified Associate in Project Management exam tests, organized to PMI’s current (2023) Examination Content Outline.^[2]

It’s interactive, not a wall of text: every module has built-in checkpoint quizzes, flashcards, and practice questions, so you learn by doing — not just reading.

The CAPM tests four official domains— Project Management Fundamentals & Core Concepts (36%), Predictive Plan-Based Methodologies (17%), Agile Frameworks/Methodologies (20%), and Business Analysis Frameworks (27%).^[2] We teach one module per domain (after a short Foundations module on core concepts), starting with the project-management basics that the rest build on.

Read a module, test yourself at each checkpoint, then drill gaps with our free practice test and flashcards. This is a high-yield overview mapped to the official outline — not a replacement for the PMBOK Guide.

CAPM Exam Snapshot

Study by weight. Fundamentals (36%) and Business Analysis (27%) are 63% of the exam, so that’s where most of your time goes — but the Predictive and Agile domains together are another 37%, and they share many concepts (scope, schedule, iterations) with the rest:

Foundations · Core Concepts & Delivery Approaches

Before the four domains, get the vocabulary and the big picture straight — because almost every CAPM question assumes you know what a project is, how it differs from operations, and which delivery approach a scenario calls for. This short module is the scaffolding the rest of the guide hangs on.

Core project concepts & life cycles

A project is temporary (a definite start and end) and unique (it creates something new). That distinguishes it from operations, which are ongoing and repetitive. Projects roll up into bigger structures: a program groups related projects for shared benefits, and a portfolio groups projects, programs, and operations to meet organizational strategy.^[3]

Every project moves through a project life cycle — generically: starting the project, organizing and preparing, carrying out the work, and closing. Throughout, the project manager balances the triple constraint — scope, schedule, and cost, with quality at the center. Push on one and the others usually move.

Predictive, agile & hybrid

The CAPM devotes a whole domain each to predictive and agile, so you must know all three approaches and when each fits. A predictive life cycle (waterfall) fixes scope up front and is best for stable, well-understood work.

An adaptive life cycle (agile) fixes time and cost and flexes scope by priority, delivering value in short increments — best when requirements are uncertain. A hybrid approach blends both, where most real projects land.^[4]

Module 1 · Project Management Fundamentals & Core Concepts (36%)

The largest domain — 36% of the exam, about 54 questions. It covers the life cycles and processes, project-management planning, the roles people play, the leadership and emotional intelligence that make a PM effective, and the everyday problem-solving tools. Master this and the rest of the exam gets easier.

1.1 Life cycles, processes & planning

Projects are authorized by a project charter, which names the project manager and grants authority to use resources. Planning then defines the work and how it will be managed across knowledge areas — cost, quality, risk, and schedule each get attention.^[2] Two key planning artifacts the CAPM names explicitly are the risk register (identified risks, owners, and responses) and the stakeholder register (who the stakeholders are and their interests).

Distinguish a milestone (a zero-duration marker of a significant point) from a task with duration (actual work that takes time). And separate the project management plan (how the project is executed and controlled) from the product it creates.

1.2 Roles, responsibilities & leadership

Separate the players. The project manager leads the team and is responsible for day-to-day execution. The sponsor provides resources and funding, champions the project, and is accountable for enabling its success — the sponsor authorizes; the PM delivers. Stakeholders are anyone affected by the project, and engaging them well is continuous work.^[2]

A strong PM wears many hats — initiator, negotiator, listener, coach, and facilitator — and leads through influence more than authority. That’s where servant leadership comes in: serve the team, remove impediments, and develop people.

Underpinning all of it is emotional intelligence — self-awareness, empathy, and social skill — which the CAPM lists explicitly. Know the difference between leadership (setting direction and inspiring people) and management (organizing work and resources); the exam rewards the leadership answer in people-focused scenarios.

1.3 Problem-solving tools & ethics

The Fundamentals domain also covers everyday problem-solving and collaboration tools. Know the purpose of focus groups (gather input from a representative group), brainstorming (generate many ideas without early judgment), and standup meetings (short, frequent syncs to surface progress and blockers) — and be able to judge whether a meeting is effective (clear purpose, right people, an agenda, and outcomes).^[2]

Finally, PMI expects ethical behavior. The PMI Code of Ethics and Professional Conduct rests on four values — responsibility, respect, fairness, and honesty — and the CAPM tests applying them to scenarios (e.g., disclosing a conflict of interest, telling the truth in a status report, treating the team fairly). A project is also a vehicle for change: it moves the organization from a current state to a more valuable future state.

Module 2 · Predictive, Plan-Based Methodologies (17%)

17% of the exam, about 26 questions. This domain is the classic, plan-driven way of running a project: decide when predictive fits, define scope with a work breakdown structure, build a schedule and budget, and control performance with documented artifacts and variances.

2.1 When predictive fits; scope & the WBS

Use a predictive life cycle when requirements are well understood and stable and change is expected to be limited — you fix scope, schedule, and cost up front and execute through sequential phases.^[2] Define the work carefully: the work breakdown structure (WBS) decomposes the total scope into work packages, and under the 100% rule nothing outside the WBS is in scope. The approved scope statement, WBS, and WBS dictionary form the scope baseline.

Guard against scope creep — uncontrolled additions that bypass change control — and gold plating, adding extras nobody asked for. Adding planned detail over time is progressive elaboration, which is healthy and not the same thing.

2.2 Schedule, critical path & cost

Build the schedule from activities, their dependencies, and durations. The critical path is the longest path through the network and the shortest time to finish; its activities have zero float, so any delay there delays the whole project. To compress, use crashing (add resources to critical-path activities, raising cost) or fast tracking (run activities in parallel, raising risk).

Estimate costs and durations with techniques the CAPM expects you to recognize: analogous (use a similar past project — fast, less accurate), parametric (use a statistical rate, like cost per unit), and bottom-up (estimate each work package and roll up — most accurate, most effort).

2.3 Earned value & project controls

Predictive projects are controlled with documented artifacts and measured with earned value management, which combines scope, schedule, and cost. The building blocks are planned value (PV), earned value (EV), and actual cost (AC). From them you get the variances and indices the CAPM asks you to calculate:^[2]

• Cost variance: $CV = EV - AC$ — negative means over budget.
• Schedule variance: $SV = EV - PV$ — negative means behind schedule.
• Cost performance index: $CPI = \dfrac{EV}{AC}$ — below 1 is over budget.
• Schedule performance index: $SPI = \dfrac{EV}{PV}$ — below 1 is behind schedule.

Module 3 · Agile Frameworks/Methodologies (20%)

20% of the exam, about 30 questions. This domain covers when an adaptive approach fits, how to plan and track iterations, the major agile frameworks, and the artifacts agile teams use. Expect questions that ask you to weigh agile against predictive and to recognize Scrum and Kanban mechanics.

3.1 When agile fits; planning iterations

Choose an adaptive life cycle (agile) when requirements are uncertain or evolving, early feedback adds value, and the team can deliver in increments. Agile fixes time and cost and flexes scope by priority, planning in short iterations rather than one big plan up front.^[4] You translate a high-level scope (or a portion of a WBS) into iteration-sized work and track progress by working product delivered, not by tasks ticked off a plan — that’s the key difference from predictive tracking.

The Agile Manifesto’s four values capture the mindset: individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; and responding to change over following a plan.

3.2 Scrum, Kanban & adaptive methods

Know the major frameworks the CAPM names — Scrum, Extreme Programming (XP), the Scaled Agile Framework (SAFe), and Kanban. Scrum delivers work in fixed sprints with three roles — the product owner (orders the product backlog), the scrum master (servant-leader who removes impediments), and the developers (build the increment) — and a set of events. Kanban is different: continuous flow on a visual board with work-in-progress (WIP) limits rather than sprints.^[4]

3.3 Agile artifacts & task management

Adaptive projects use their own artifacts. The product backlog is the ordered list of everything that might be needed; the team pulls top items into each iteration and forecasts with velocity.

Work is often written as a user story — “As a [role], I want [goal] so that [benefit]” — with acceptance criteria defining when it’s done. Teams aim to deliver a usable increment each cycle, often building toward a minimum viable product. Prioritize tasks by value, and judge success against the iteration’s defined criteria.^[4]

Module 4 · Business Analysis Frameworks (27%)

The second-largest domain — 27% of the exam, about 40 questions. business analysis is the work of identifying business needs and recommending solutions that deliver value. The CAPM tests BA roles and communication, gathering and tracing requirements, product roadmaps, and validating that what’s delivered actually meets the need.

4.1 BA roles & stakeholder communication

Distinguish the roles a BA works with: a process owner is accountable for a business process; a process manager runs it day to day; a product manager owns the product strategy; and a product owner (in agile) orders the backlog and maximizes value. Roles can be internal or external to the organization, and clear roles and responsibilities keep requirements from falling through the cracks.^[2]

Communication is central to business analysis. The BA recommends the right channel or tool for the situation — a quick chat, a workshop, a written specification, a shared board — and keeps stakeholders across teams aligned, because misunderstood requirements are a top cause of failed solutions.

4.2 Gathering & tracing requirements

Elicitation is how a BA draws out requirements — through interviews, facilitated workshops, surveys, observation (job shadowing), prototyping, document analysis, and brainstorming. The CAPM expects you to match the right technique to a scenario (interviews for deep input from a few; surveys for broad input from many). Requirements come in types — business, stakeholder, and solution (split into functional and non-functional).^[2]

Capture requirements as user stories or use cases, then track them with a requirements traceability matrix (or, in agile, the product backlog). Tracing each requirement from its origin through to delivery and test makes sure nothing is lost and that every requirement delivers value.

4.3 Roadmaps & validating delivery

A product roadmap is a high-level visual of the product’s direction and planned releases over time; the BA helps decide which components go into which release. The BA’s role flexes with the methodology — in predictive projects requirements are often detailed up front, while in adaptive projects they’re elaborated continuously through the backlog.^[2]

Finally, validate requirements through delivery: define acceptance criteria for each requirement, then confirm the product is ready by checking it against the requirements traceability matrix or product backlog. Validation makes sure the solution delivers the intended value — not just that something was built.

How to Use This CAPM Study Guide

This guide is built to be worked, not just read. The most efficient path to a pass:

• Build the vocabulary first. The Foundations module is short but high-leverage — most questions assume the core concepts.
• Study by weight. Fundamentals (36%) and Business Analysis (27%) are 63% of the exam — start there, then Agile and Predictive.
• Check off as you go. Use the Study Guide Contents to mark each section done; it raises your exam-readiness score.
• Take every checkpoint. The end-of-module quizzes show you exactly which domains need another pass.
• Drill the weak domain. Send your weak area into the flashcards and a practice test until the score climbs.
• Learn the reasoning. The CAPM rewards understanding — know why an answer is right, not just the fact.

CAPM Glossary

The high-yield CAPM terms in one place — hover any dotted term in the guide, or flip the whole deck here as a self-grading flashcard set.

Acceptance criteria

The conditions a requirement or solution must satisfy to be accepted as complete and correct.

Actual cost

AC — the real cost incurred for the work completed by a given date.

Adaptive life cycle

An agile approach that flexes scope through iterations, delivering value in short increments with frequent feedback.

Agile

An iterative, incremental approach that fixes time and cost and flexes scope by priority, delivering value in short cycles.

Assumption

A factor considered true for planning without proof; assumptions carry risk if they prove wrong.

Business analysis

The set of activities to identify business needs and recommend solutions that deliver value.

Business case

The documented justification for a project, showing its need, options, benefits, and costs.

Constraint

A limiting factor that affects how the project is executed (e.g., a fixed budget or deadline).

Cost performance index

CPI = EV ÷ AC; greater than 1 is under budget, less than 1 is over budget.

Cost variance

CV = EV − AC; a negative value means the project is over budget.

Crashing

Compressing the schedule by adding resources to critical-path activities, which raises cost.

Critical path

The longest sequence of dependent activities through the schedule; it has zero total float and sets the shortest project duration.

Deliverable

Any unique, verifiable product, result, or capability produced to complete a process, phase, or project.

Earned value

EV — the budgeted cost of the work actually completed by a given date.

Earned value management

An integrated method that combines scope, schedule, and cost to measure and forecast project performance.

Elicitation

Drawing out information from stakeholders and sources to discover requirements (interviews, workshops, observation).

Emotional intelligence

The ability to recognize and manage one's own emotions and to read and influence others' emotions.

Enterprise environmental factors

EEFs — conditions outside the team's control (culture, market, regulations) that influence the project.

Fast tracking

Compressing the schedule by performing activities in parallel that were planned in sequence, which raises risk.

Float

The amount of time an activity can be delayed without delaying the project end date (total float) or the next activity (free float).

Functional requirement

A requirement describing what the solution must do — its features and behaviors.

Hybrid approach

A delivery approach that blends predictive and agile elements, tailored to the project and organization.

Kanban

An agile method based on visualizing work and limiting work in progress to improve continuous flow.

Milestone

A significant point or event in the project; it has zero duration and marks a major deliverable or phase completion.

Minimum viable product

The smallest releasable version of a product that delivers value and enables learning.

Non-functional requirement

A requirement describing how well the solution must perform — quality attributes like security, performance, and usability.

Operations

Ongoing, repetitive work that sustains the business — distinct from temporary, unique project work.

Organizational process assets

OPAs — an organization's plans, processes, policies, templates, and knowledge bases used on projects.

PDU

A professional development unit — the credit used to renew a CAPM (15 PDUs per three-year cycle).

Planned value

PV — the authorized budget assigned to the work scheduled to be done by a given date.

PMBOK Guide

PMI's A Guide to the Project Management Body of Knowledge; the 7th edition is principle- and value-based.

Portfolio

A collection of projects, programs, and operations managed as a group to achieve strategic objectives.

Predictive life cycle

A plan-driven (waterfall) approach where scope, schedule, and cost are fixed up front and work proceeds in sequential phases.

Product backlog

An ordered, evolving list of everything that might be needed in the product, owned by the product owner.

Product owner

The Scrum role accountable for maximizing value and ordering the product backlog.

Product roadmap

A high-level visual of the product's direction and planned releases over time.

Program

A group of related projects managed in a coordinated way to obtain benefits not available from managing them individually.

Project

A temporary endeavor undertaken to create a unique product, service, or result; it has a definite beginning and end.

Project charter

The document that formally authorizes the project, names the project manager, and gives authority to apply resources.

Project life cycle

The series of phases a project passes through from start to completion: starting, organizing & preparing, carrying out the work, and closing.

Project manager

The person assigned to lead the team responsible for achieving the project objectives.

Requirement

A condition or capability needed by a stakeholder to solve a problem or achieve an objective.

Requirements traceability matrix

A grid linking each requirement to its origin and to deliverables, tests, and objectives, so nothing is lost.

Risk register

The artifact recording identified risks with their probability, impact, owner, and planned responses.

Schedule performance index

SPI = EV ÷ PV; greater than 1 is ahead of schedule, less than 1 is behind.

Schedule variance

SV = EV − PV; a negative value means the project is behind schedule.

Scope baseline

The approved scope statement, work breakdown structure, and WBS dictionary used to measure scope performance.

Scope creep

The uncontrolled expansion of scope without adjustments to time, cost, and resources.

Scrum

An agile framework delivering work in fixed timeboxes (sprints) with set roles and ceremonies.

Scrum master

A servant-leader who coaches the team, facilitates events, and removes impediments — does not assign work.

Servant leadership

A leadership style focused on serving and developing the team — removing impediments and enabling a self-organizing team — rather than commanding it.

Sponsor

The person or group that provides resources and support for the project and is accountable for enabling its success.

Sprint

A short, fixed-length iteration (often 1–4 weeks) in which a Scrum team produces a usable increment.

Stakeholder

Any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by the project.

Stakeholder register

The document identifying project stakeholders and their roles, interests, and influence.

Tailoring

Deliberately adapting the approach, processes, and artifacts to fit the specific project context.

Triple constraint

The interrelated balance of scope, schedule, and cost (with quality at the center); changing one usually affects the others.

User story

A short requirement from the user's perspective: 'As a [role], I want [goal] so that [benefit].'

Velocity

The amount of work an agile team completes per iteration, used to forecast future capacity.

Work breakdown structure

A hierarchical decomposition of the total project scope into deliverables and work packages; nothing outside it is in scope.

Work in progress limit

A cap on how many items can be in a workflow stage at once, used in Kanban to improve flow.

Work package

The lowest-level deliverable in the WBS — the unit you estimate, schedule, and assign.

CAPM Study Guide FAQ

References

1. 1.Project Management Institute. “Certified Associate in Project Management (CAPM) Certification.” pmi.org. ↑
2. 2.Project Management Institute. “CAPM Examination Content Outline (2023 ECO).” pmi.org. ↑
3. 3.Project Management Institute. “A Guide to the Project Management Body of Knowledge (PMBOK Guide), 7th ed..” pmi.org. ↑
4. 4.Project Management Institute. “Agile Practice Guide.” pmi.org. ↑
5. 5.Project Management Institute. “CAPM Certification Handbook (eligibility, fees & scoring).” pmi.org. ↑

Career Employer

Career Employer is the ultimate resource to help you get started working the job of your dreams. We cover topics from general career information, career searching, exam preparation with free study materials, career interviewing, and becoming successful in your career of choice.

Follow Us:

All Posts