CAPM

Who Should Take This

Individuals who have completed 23 hours of project‑management education or accumulated 1,500 hours of project experience, such as recent graduates, junior project coordinators, or aspiring analysts, should enroll. They seek a recognized credential that validates foundational knowledge and opens entry‑level opportunities in project‑focused organizations.

What's Covered

1 All domains in the PMI Certified Associate in Project Management (CAPM) exam content outline: Project Management Fundamentals and Core Concepts

2 , Predictive Plan-Based Methodologies

3 , Agile Frameworks and Methodologies

4 , and Business Analysis Frameworks

What's Included in AccelaStudy® AI

Adaptive Knowledge Graph

Practice Questions

Lesson Modules

Console Simulator Labs

Exam Tips & Strategy

20 Activity Formats

Course Outline

75 learning goals

1 Domain 1: Project Management Fundamentals and Core Concepts

7 topics

Project Life Cycle and Organizational Context

Define the characteristics that distinguish a project from ongoing operations, including temporary nature, unique deliverables, and progressive elaboration of scope.
Identify the phases of a generic project life cycle including initiation, planning, execution, and closing, and describe the typical activities and deliverables associated with each phase.
Describe the differences between functional, matrix, and projectized organizational structures and explain how each affects project manager authority, resource availability, and communication pathways.
Identify the role and responsibilities of key project stakeholders including the project sponsor, project manager, functional managers, and project team members within different organizational structures.
Apply the concept of progressive elaboration to explain how project scope, schedule, and cost estimates are refined iteratively as more information becomes available throughout the project life cycle.

PMBOK Seventh Edition Principles and Performance Domains

List and describe the twelve project management principles from PMBOK Seventh Edition, including stewardship, team, stakeholders, value, systems thinking, leadership, tailoring, quality, complexity, risk, adaptability, and change.
Identify the eight project performance domains defined in PMBOK Seventh Edition: Stakeholders, Team, Development Approach and Life Cycle, Planning, Project Work, Delivery, Measurement, and Uncertainty.
Apply tailoring principles to select appropriate development approaches, processes, and artifacts based on project characteristics such as complexity, uncertainty, team experience, and stakeholder needs.
Analyze how the systems thinking principle applies to project management by identifying interactions and dependencies among project performance domains, organizational processes, and external environmental factors.

Stakeholder and Communications Management Fundamentals

Identify project stakeholders using techniques such as brainstorming, expert judgment, and stakeholder registers, and classify them by power, interest, influence, and impact.
Apply stakeholder engagement strategies including managing expectations, resolving competing interests, and using a stakeholder engagement assessment matrix to monitor engagement levels.
Describe the components of a communications management plan including stakeholder communication requirements, methods, frequency, escalation procedures, and the communication channels formula.
Analyze the impact of communication barriers on project outcomes and evaluate when to use push, pull, and interactive communication methods based on stakeholder needs and message urgency.

Scope, Schedule, and Cost Fundamentals

Define project scope using a work breakdown structure by decomposing deliverables into work packages and establishing the scope baseline with the project scope statement and WBS dictionary.
Describe the purpose and structure of a requirements traceability matrix and explain how it links project requirements to their source, WBS elements, and verification activities.
Apply scheduling techniques including precedence diagramming method, critical path method, and resource leveling to develop a project schedule network diagram and identify float values.
Identify the four types of logical dependencies in scheduling: finish-to-start, start-to-start, finish-to-finish, and start-to-finish, and describe when each relationship is used.
Apply cost estimation techniques including analogous, parametric, bottom-up, and three-point estimating to develop project budget estimates and establish a cost baseline with management reserves.
Analyze earned value management metrics including planned value, earned value, actual cost, schedule variance, cost variance, SPI, and CPI to assess project performance against baselines.

Quality, Resource, and Risk Fundamentals

Define the distinction between quality assurance and quality control and identify key quality tools including checklists, cause-and-effect diagrams, Pareto charts, control charts, and flowcharts.
Apply the concept of cost of quality by categorizing quality costs into prevention, appraisal, internal failure, and external failure and explaining their impact on project budgets.
Describe resource management processes including estimating activity resources, acquiring project team members, developing team capabilities through training and team-building, and managing team performance.
Apply risk identification techniques including brainstorming, SWOT analysis, checklists, and assumptions analysis to populate a risk register with identified risks, triggers, and potential responses.
Apply qualitative risk analysis using probability and impact matrices to prioritize risks and determine which risks warrant detailed quantitative analysis or immediate response planning.
Identify the five risk response strategies for threats (avoid, mitigate, transfer, accept, escalate) and the five strategies for opportunities (exploit, enhance, share, accept, escalate).

Integration and Change Control

Describe the purpose and key components of a project charter including business case justification, high-level requirements, milestone schedule, initial budget, stakeholder list, and project manager authority.
Apply the integrated change control process to evaluate change requests by assessing their impact on scope, schedule, cost, quality, and risk baselines before approval or rejection.
Describe the activities involved in closing a project or phase including final deliverable acceptance, lessons learned documentation, resource release, procurement closure, and archiving project records.
Analyze the interrelationships among project management knowledge areas to explain how changes in one area (such as scope) produce cascading impacts on schedule, cost, quality, and risk.

Procurement Fundamentals

Identify the types of contracts used in project procurement including fixed-price, cost-reimbursable, and time-and-materials contracts, and describe the risk allocation characteristics of each.
Apply the plan procurement management process to determine which project needs can be met through external sourcing, develop procurement statements of work, and select appropriate contract types.
Describe the conduct procurements process including bid evaluation criteria, source selection methods (weighting systems, independent estimates, screening systems), and contract negotiation activities.

2 Domain 2: Predictive Plan-Based Methodologies

3 topics

Predictive Life Cycle Characteristics

Describe the characteristics of a predictive (waterfall) project life cycle including sequential phase progression, upfront requirements definition, and baseline-driven execution and control.
Identify the conditions under which a predictive approach is most appropriate, including well-defined requirements, low uncertainty, regulatory compliance needs, and fixed-scope contractual obligations.
Compare predictive and adaptive life cycles by evaluating their treatment of requirements stability, change tolerance, stakeholder feedback frequency, and deliverable release cadence.

Predictive Planning Techniques

Create a work breakdown structure using the decomposition technique to break project scope into manageable work packages with clear deliverables and acceptance criteria.
Apply the critical path method to calculate early start, early finish, late start, late finish, and total float for each activity in a project schedule network diagram.
Apply three-point estimating using PERT formulas (optimistic, most likely, pessimistic) to calculate expected duration and standard deviation for schedule and cost estimates.
Analyze schedule compression techniques including crashing and fast-tracking by evaluating their impact on project cost, risk, quality, and resource utilization.

Predictive Execution and Control

Execute the project management plan by directing and managing project work, implementing approved changes, and coordinating resources according to the established baselines.
Apply variance analysis to monitor and control project performance by comparing actual scope, schedule, and cost results against the approved baselines and initiating corrective actions.
Analyze the estimate at completion using earned value formulas (EAC = BAC/CPI, EAC = AC + ETC, EAC = AC + BAC - EV) and determine which formula is appropriate for a given project scenario.
Apply the perform integrated change control process in a predictive environment by routing change requests through a change control board and updating affected baselines upon approval.

3 Domain 3: Agile Frameworks and Methodologies

5 topics

Agile Principles and Mindset

List and describe the four values of the Agile Manifesto and the twelve supporting principles, and explain how they guide decision-making in agile project environments.
Describe the servant leadership model in agile environments and identify how it differs from command-and-control leadership in terms of team empowerment, facilitation, and impediment removal.
Analyze how agile principles address uncertainty by emphasizing iterative delivery, continuous feedback, timeboxed development, and the ability to adapt plans based on emergent requirements.

Scrum Framework

Identify the three Scrum roles (Product Owner, Scrum Master, Development Team) and describe their distinct responsibilities, accountabilities, and interaction patterns within the Scrum framework.
Describe the five Scrum events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective) including their purpose, timebox durations, participants, and expected outcomes.
Apply Sprint Planning techniques to select product backlog items for the Sprint Backlog based on team velocity, capacity, Definition of Done, and the Sprint Goal.
Apply the Sprint Retrospective format to identify process improvements by analyzing what went well, what could be improved, and creating actionable improvement commitments for the next Sprint.
Identify the three Scrum artifacts (Product Backlog, Sprint Backlog, Increment) and their associated commitments (Product Goal, Sprint Goal, Definition of Done) as defined in the Scrum Guide.

Kanban and Other Agile Approaches

Describe the core Kanban practices including visualizing workflow, limiting work in progress, managing flow, making process policies explicit, implementing feedback loops, and improving collaboratively.
Apply work-in-progress limits on a Kanban board to optimize flow, reduce cycle time, and identify bottlenecks in the team's delivery process.
Recognize the characteristics of Extreme Programming (XP) practices including pair programming, test-driven development, continuous integration, collective code ownership, and sustainable pace.
Analyze the differences between iteration-based agile methods (Scrum, XP) and flow-based methods (Kanban) in terms of cadence, roles, planning approach, and change management.

Agile Planning, Estimation, and Metrics

Apply user story writing techniques using the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) and the role-feature-benefit format to define product backlog items.
Apply relative estimation techniques including story points, T-shirt sizing, and planning poker to size product backlog items and forecast team delivery capacity.
Describe agile metrics including velocity, burndown charts, burnup charts, cumulative flow diagrams, cycle time, and lead time, and explain what each metric reveals about team performance.
Analyze a team's velocity trend and burndown chart pattern to assess whether the team is on track to meet the release plan and identify when corrective action may be needed.

Hybrid Approaches

Describe the characteristics of a hybrid project life cycle that combines predictive and agile elements, and identify scenarios where a hybrid approach provides advantages over purely predictive or purely agile methods.
Apply tailoring guidelines to construct a hybrid approach by selecting predictive elements for well-understood components and agile elements for components with high uncertainty or evolving requirements.

4 Domain 4: Business Analysis Frameworks

4 topics

Needs Assessment and Business Case

Describe the needs assessment process including problem or opportunity identification, current state analysis, desired future state definition, and gap analysis to justify project initiation.
Identify the components of a business case including financial analysis (ROI, NPV, IRR, payback period), strategic alignment, alternative analysis, and recommendation for the selected approach.
Apply project selection methods including benefit-cost analysis, weighted scoring models, and constrained optimization to evaluate and rank competing project proposals.

Requirements Elicitation and Analysis

Identify and apply requirements elicitation techniques including interviews, focus groups, workshops, questionnaires, observation, prototyping, and document analysis to gather stakeholder needs.
Describe the categories of requirements including business, stakeholder, solution (functional and non-functional), transition, and project requirements, and explain how each category contributes to project scope.
Apply requirements analysis techniques including data flow diagrams, use case diagrams, state diagrams, and process models to decompose, organize, and specify detailed solution requirements.
Apply requirements prioritization techniques including MoSCoW, Kano model, and weighted ranking to sequence requirements for implementation based on business value, risk, and dependencies.
Analyze requirements for completeness, consistency, feasibility, and traceability to identify conflicts, gaps, and ambiguities before requirements are baselined.

Traceability and Change Management

Apply a requirements traceability matrix to establish bidirectional links between business needs, stakeholder requirements, solution requirements, and test cases throughout the project life cycle.
Describe the requirements change management process including impact assessment, configuration management, version control, and the relationship between requirements changes and scope changes.
Analyze the impact of scope creep versus gold plating on project outcomes and evaluate techniques for preventing unauthorized scope changes while maintaining stakeholder satisfaction.

Solution Evaluation

Describe solution evaluation activities including acceptance criteria verification, user acceptance testing, and validation that deliverables meet the stated business needs and requirements.
Apply solution evaluation techniques to assess whether a delivered solution achieves expected business outcomes by comparing actual results against the objectives defined in the business case.
Analyze lessons learned from solution evaluation to identify patterns of requirements defects, process improvements, and recommendations for organizational process assets updates.

Scope

Included Topics

All domains in the PMI Certified Associate in Project Management (CAPM) exam content outline: Project Management Fundamentals and Core Concepts (36%), Predictive Plan-Based Methodologies (17%), Agile Frameworks and Methodologies (20%), and Business Analysis Frameworks (27%).
Foundational project management knowledge aligned to PMBOK Guide Seventh Edition including project performance domains, principles, tailoring, and models, methods, and artifacts.
Core project management concepts: project life cycles, organizational structures, stakeholder identification, scope definition, scheduling techniques (CPM, PERT, Gantt), cost estimation, quality management, resource management, communications planning, risk identification and qualitative analysis, and procurement fundamentals.
Agile and hybrid approaches including Scrum framework, Kanban method, user stories, product backlogs, sprint planning, retrospectives, velocity tracking, burndown charts, and the Agile Practice Guide principles.
Business analysis fundamentals including needs assessment, requirements elicitation, analysis and documentation techniques, traceability, solution evaluation, and the relationship between business analysis and project management.

Not Covered

Advanced portfolio and program management concepts that fall under the PMP, PgMP, or PfMP certification scope.
Deep organizational change management, benefits realization tracking, and strategic alignment activities beyond the CAPM exam content outline.
Proprietary tool-specific configuration or administration (e.g., Microsoft Project, Jira, Azure DevOps) not required by the CAPM exam.
Industry-specific regulatory frameworks, compliance requirements, and domain-specific project management practices not covered in the CAPM content outline.
Advanced earned value management calculations beyond basic CPI, SPI, EV, PV, and AC computations.

Official Exam Page

Learn more at Project Management Institute

Visit