Understanding the four domains of the CAPM exam is the foundation of your certification success. Unlike many other certifications, the CAPM doesn't just test your knowledge of a single methodology—it evaluates your understanding across traditional predictive approaches, modern agile frameworks, and essential business analysis skills.
The current CAPM Exam Content Outline (ECO), effective since July 2023, represents a significant evolution in how PMI assesses entry-level project management professionals. With 47% of the exam now covering agile and hybrid approaches (combining Domain 3's 20% with agile concepts integrated throughout), mastering all four domains is non-negotiable for first-attempt success.
📋 Table of Contents
⚠️ Critical Misconception
Many candidates believe the CAPM exam is based solely on the PMBOK Guide. This is incorrect. The CAPM exam is based on the CAPM Exam Content Outline (ECO), not the PMBOK Guide. The PMBOK Guide (7th Edition) is one of several reference documents—studying it alone will not be sufficient to pass.
Understanding the CAPM Exam Content Outline Structure
The CAPM ECO organizes exam content into a three-tier hierarchy that you must understand to study effectively:
Domains
High-level knowledge areas essential to the practice of project management. There are four domains, each with a specific percentage weight on the exam.
Tasks
The underlying responsibilities of project team members within each domain. Each domain contains between 3-6 tasks that define what you're expected to know and do.
Enablers
Illustrative examples of the work associated with each task. These are not exhaustive lists but provide guidance on the scope of knowledge required.
| Domain | Weight | Tasks | Questions (approx.) |
|---|---|---|---|
| 1. Project Management Fundamentals | 36% | 5 Tasks | ~49 questions |
| 2. Predictive, Plan-Based Methodologies | 17% | 3 Tasks | ~23 questions |
| 3. Agile Frameworks/Methodologies | 20% | 5 Tasks | ~27 questions |
| 4. Business Analysis Frameworks | 27% | 6 Tasks | ~36 questions |
Note: Of the 150 exam questions, 15 are unscored pretest questions distributed randomly throughout. Approximate question counts are based on the 135 scored questions.
Domain 1: Project Management Fundamentals and Core Concepts (36%)
This is the largest domain and forms the foundation for all your project management knowledge. It covers the basic terminology, concepts, and frameworks that underpin both predictive and adaptive project management approaches.
Tasks in Domain 1:
Key Concepts You Must Master
Project vs. Program vs. Portfolio
A project is a temporary endeavor to create a unique product, service, or result. A program is a group of related projects managed together to realize benefits not achievable if managed independently. A portfolio is a collection of projects, programs, and other work grouped together to facilitate effective management and meet strategic business objectives.
Project vs. Operations
Projects are temporary and create unique outputs. Operations are ongoing, repetitive activities that sustain the organization. Understanding when work transitions from project to operations is a common exam topic.
Predictive vs. Adaptive Approaches
Predictive (Waterfall): Detailed planning upfront, sequential phases, scope defined early, changes managed through formal change control. Best for projects with well-understood requirements.
Adaptive (Agile): Iterative development, requirements evolve, frequent delivery of increments, welcomes change. Best for projects with evolving requirements or uncertainty.
Issues, Risks, Assumptions, and Constraints (IRAC)
- Issues: Problems that have already occurred and need resolution
- Risks: Uncertain events that may occur and could impact objectives (positive or negative)
- Assumptions: Factors considered true without proof for planning purposes
- Constraints: Limitations that restrict project options (budget, time, scope, resources)
Project Life Cycle Phases
All projects, regardless of methodology, move through phases: Initiating → Planning → Executing → Monitoring & Controlling → Closing. In predictive projects, these are sequential. In adaptive projects, planning through closing repeat in iterations.
PMI Code of Ethics and Professional Conduct
You must understand the four values: Responsibility (ownership of decisions), Respect (treating others appropriately), Fairness (making impartial decisions), and Honesty (truthfulness in communications). Expect scenario questions testing ethical decision-making.
💡 Exam Focus: Domain 1
Expect questions asking you to distinguish between similar concepts (project vs. program, risk vs. issue), identify appropriate approaches for given scenarios, and apply ethical principles to workplace situations. This domain tests foundational vocabulary and conceptual understanding.
Key Artifacts and Tools
- Project Charter: Formally authorizes the project and provides the project manager with authority
- Stakeholder Register: Documents stakeholders, their interests, attitudes, and engagement levels
- Risk Register: Records identified risks, analysis results, and planned responses
- Lessons Learned: Knowledge gained during the project to improve future performance
Domain 2: Predictive, Plan-Based Methodologies (17%)
This domain focuses on traditional "waterfall" project management—the structured, sequential approach where detailed planning precedes execution. While it has the smallest percentage, don't underestimate it. Predictive concepts appear throughout other domains.
Tasks in Domain 2:
When to Use Predictive Approaches
Predictive methodologies are appropriate when:
- Requirements are well-defined and unlikely to change
- The project scope is clear from the beginning
- Regulatory or compliance requirements demand extensive documentation
- Stakeholders need detailed upfront planning for budgeting purposes
- The technology and approach are well-understood
- Industries like construction, manufacturing, or government contracts
Key Predictive Concepts
Work Breakdown Structure (WBS)
A hierarchical decomposition of the total scope of work. The WBS breaks the project into manageable work packages. Remember: The WBS shows deliverables, not activities. The 100% rule states that the WBS must include 100% of the project scope—no more, no less.
Critical Path Method (CPM)
The critical path is the longest sequence of dependent activities that determines the minimum project duration. Activities on the critical path have zero float—any delay extends the project. Understanding how to identify the critical path and calculate float is essential.
Earned Value Management (EVM)
Key formulas you must know:
- Planned Value (PV): Budgeted cost of work scheduled
- Earned Value (EV): Budgeted cost of work performed
- Actual Cost (AC): Actual cost of work performed
- Schedule Variance (SV): EV - PV (positive = ahead of schedule)
- Cost Variance (CV): EV - AC (positive = under budget)
- Schedule Performance Index (SPI): EV / PV (>1 = ahead of schedule)
- Cost Performance Index (CPI): EV / AC (>1 = under budget)
⚠️ Formula Alert
Approximately 25-30 questions on the CAPM exam involve calculations. While you'll have access to an on-screen calculator, you must memorize these formulas. Practice until EVM calculations become second nature.
Project Baselines
The three baselines (scope, schedule, cost) form the performance measurement baseline against which project performance is measured. Changes to baselines require formal change control approval.
Change Control Process
In predictive projects, changes follow a formal process: Submit change request → Review impact → Approve/reject via Change Control Board (CCB) → Update project documents if approved → Communicate to stakeholders.
Domain 3: Agile Frameworks/Methodologies (20%)
Agile has become essential across industries beyond software development. This domain tests your understanding of agile principles, frameworks like Scrum and Kanban, and the adaptive mindset that welcomes change rather than resisting it.
Tasks in Domain 3:
The Agile Manifesto
The foundation of all agile frameworks rests on four values:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
Note: While the items on the right have value, agile practitioners value the items on the left more.
Scrum Framework
Scrum is the most widely used agile framework and heavily tested on the CAPM exam.
Scrum Roles
- Product Owner: Represents the customer/stakeholders, owns the Product Backlog, prioritizes features based on business value, defines acceptance criteria
- Scrum Master: Servant leader who facilitates Scrum practices, removes impediments, coaches the team, protects the team from distractions
- Development Team: Self-organizing, cross-functional team (typically 3-9 members) that delivers potentially shippable increments
Scrum Events (Ceremonies)
- Sprint: Time-boxed iteration (typically 2-4 weeks) that produces a potentially releasable increment
- Sprint Planning: Team selects items from Product Backlog and plans the Sprint
- Daily Scrum (Stand-up): 15-minute daily meeting to synchronize and plan the next 24 hours
- Sprint Review: End-of-sprint demonstration of completed work to stakeholders
- Sprint Retrospective: Team reflects on the Sprint and identifies improvements
Scrum Artifacts
- Product Backlog: Prioritized list of all desired features, owned by Product Owner
- Sprint Backlog: Items selected for the current Sprint plus the plan for delivering them
- Increment: The sum of all completed Product Backlog items, must meet Definition of Done
Kanban
Kanban focuses on visualizing workflow and limiting work in progress (WIP).
Key Kanban Principles
- Visualize the workflow: Kanban board with columns (To Do, In Progress, Done)
- Limit WIP: Cap the number of items in each column to prevent overload
- Manage flow: Monitor lead time and cycle time to optimize throughput
- Make policies explicit: Clear rules for how work moves through the system
- Implement feedback loops: Regular reviews to improve the process
- Improve collaboratively: Continuous, evolutionary improvement
🔑 Scrum vs. Kanban: Know the Difference
Scrum uses fixed-length sprints, prescribed roles (Product Owner, Scrum Master), and defined ceremonies. Kanban has continuous flow, no prescribed roles, and no iterations—work is pulled as capacity allows. Both are agile, but their structures differ significantly. Expect exam questions requiring you to identify which framework fits a given scenario.
Agile Estimation Techniques
- Story Points: Relative estimation based on complexity, risk, and effort
- Planning Poker: Team consensus-based estimation using cards
- T-shirt Sizing: Quick relative sizing (XS, S, M, L, XL)
- Velocity: Average story points completed per sprint, used for forecasting
Hybrid Approaches
Hybrid projects combine predictive and adaptive elements. For example, using waterfall for hardware development while applying agile to software components. Understanding when and how to blend approaches is increasingly tested.
Domain 4: Business Analysis Frameworks (27%)
The addition of Business Analysis to the CAPM reflects the reality that entry-level project professionals often perform BA tasks. This domain covers stakeholder engagement, requirements gathering, and ensuring project outcomes align with business goals.
Tasks in Domain 4:
Business Analysis Roles
Internal Stakeholder Roles
- Executive Sponsor: Provides strategic direction, resources, and executive support
- Process Owner: Responsible for the design and improvement of specific business processes
- Process Manager: Manages day-to-day execution of business processes
- Product Manager: Owns product strategy, roadmap, and lifecycle
- Product Owner: (Agile) Manages the product backlog and maximizes value
- Subject Matter Experts (SMEs): Provide domain expertise
External Stakeholder Roles
- Customers: End users of the product or service
- Vendors/Partners: External entities providing resources or services
- Regulators: Government or industry bodies imposing compliance requirements
Requirements Gathering Techniques
The CAPM tests your ability to select appropriate techniques based on project context:
- Interviews: One-on-one discussions to explore stakeholder needs in depth
- Surveys/Questionnaires: Efficient for gathering information from large audiences
- Workshops/Focus Groups: Collaborative sessions to define requirements with multiple stakeholders
- Observation: Watching users perform tasks to understand actual workflows
- Document Analysis: Reviewing existing documentation, processes, and systems
- Prototyping: Creating preliminary versions for stakeholder feedback
- User Stories: (Agile) Short descriptions from user perspective: "As a [user], I want [goal] so that [benefit]"
- Use Cases: Detailed descriptions of system-user interactions
Requirements Traceability Matrix
A tool that links requirements throughout the project lifecycle, connecting each requirement to its source, related deliverables, and test cases. This ensures nothing is missed and facilitates impact analysis when changes occur.
Product Roadmaps
Visual strategic documents showing product evolution over time. Roadmaps help communicate planned features, releases, and timelines to stakeholders. Key elements include:
- Vision and goals
- Features and epics
- Release timelines
- Dependencies
- Resource requirements
Validating Requirements
Requirements validation ensures deliverables meet stakeholder expectations:
- Acceptance Criteria: Predefined conditions that must be met for deliverables to be accepted
- Definition of Done: (Agile) Team agreement on what "complete" means
- User Acceptance Testing (UAT): Stakeholders verify the solution meets requirements
- Product Backlog: Living document for tracking and validating requirements in agile
✅ Business Analysis in Different Methodologies
In predictive projects, BA activities are front-loaded—comprehensive requirements gathering before development begins. In adaptive projects, BA activities are ongoing throughout iterations, with requirements refined continuously. Expect scenario questions asking you to identify appropriate BA approaches based on the project methodology.
Domain-Based Study Strategy
Given the domain weightings, allocate your study time proportionally—but don't neglect any domain:
| Domain | Weight | Recommended Study Time | Priority Focus |
|---|---|---|---|
| Domain 1: PM Fundamentals | 36% | 35% of study time | Vocabulary, concepts, ethics |
| Domain 2: Predictive | 17% | 20% of study time | Formulas, WBS, CPM, EVM |
| Domain 3: Agile | 20% | 20% of study time | Scrum roles/events, Kanban |
| Domain 4: Business Analysis | 27% | 25% of study time | Requirements, stakeholders |
💡 Study Tip: Cross-Domain Integration
Domains aren't isolated—they interconnect. Risk management (Domain 1) applies differently in predictive (Domain 2) vs. agile (Domain 3) projects. Business analysis (Domain 4) adapts based on methodology. Practice recognizing how concepts span multiple domains.
Common Mistakes to Avoid
1. Studying Only the PMBOK Guide
The exam is based on the ECO, not the PMBOK. Use the PMBOK 7th Edition and Agile Practice Guide as references, but structure your study around the ECO domains and tasks.
2. Ignoring Domain 2 Due to Low Weight
At 17%, predictive concepts seem less important. However, EVM formulas, WBS, and change control appear in scenario questions across domains. A weak foundation here hurts your overall score.
3. Memorizing Without Understanding
The CAPM tests application, not just recall. You'll face scenario-based questions requiring you to select the best action—not just define a term. Practice applying concepts to realistic situations.
4. Neglecting the Agile Mindset
Many candidates with traditional project management backgrounds struggle with agile questions. It's not just about knowing Scrum events—it's about understanding the iterative, collaborative, change-welcoming mindset that drives agile success.
5. Underestimating Business Analysis
At 27%, Domain 4 is the second-largest domain. Many candidates skip or skim BA content. Don't make this mistake—stakeholder management and requirements gathering are heavily tested.
🔑 Key Takeaway
The CAPM exam tests your ability to work effectively on project teams using predictive, agile, and hybrid approaches. Master all four domains, understand how they interconnect, and practice applying concepts to scenario-based questions. Domain knowledge alone isn't enough—you must demonstrate practical application.
Next Steps
Now that you understand the four CAPM domains, it's time to deepen your knowledge in each area:
- Download the official CAPM Exam Content Outline from PMI.org and review each task and enabler
- Study reference materials including PMBOK Guide 7th Edition, Agile Practice Guide, and Business Analysis for Practitioners
- Take domain-specific practice quizzes to identify knowledge gaps
- Focus extra time on weaker domains while maintaining proficiency across all four
- Practice with full-length simulated exams to build stamina and time management skills
Test Your Domain Knowledge
Ready to see how well you understand all four CAPM domains? Practice with questions mapped to each domain and task.