ManagementCAPM

CAPM: Certified Associate in Project Management Fundamentals

The CAPM (Certified Associate in Project Management) is PMI's entry-level project management credential — the stepping stone before the PMP. It validates that you understand the project management framework from PMBOK and can apply the core concepts in a project environment. You do not need years of experience to take the CAPM (unlike the PMP which requires 36-60 months), making it ideal for recent graduates, people transitioning into project management, and team members who support project managers.

10 min
3 sections · 10 exam key points

Project Management Fundamentals and Process Groups

A project is a temporary endeavour undertaken to create a unique product, service, or result — temporary means it has a defined beginning and end, unique means it is different from operations (ongoing repetitive work). The project lifecycle: a project goes through phases from conception to closure, with each phase producing deliverables that feed the next. PMBOK 6 defines five process groups: Initiating (authorise and define the project — creates the Project Charter, identifies stakeholders), Planning (develop the Project Management Plan across all knowledge areas — the most complex group with the most processes), Executing (lead the team and perform the work — managing people, communications, and quality), Monitoring and Controlling (track, review, and regulate progress — compare actuals to baseline, manage changes), Closing (formally complete the project — obtain sign-off, release resources, document lessons learned). The Project Charter formally authorises the project and names the Project Manager — it is created during Initiating and signed by a sponsor who is external to the project.

Planning Knowledge Areas for CAPM

Planning is the most tested area in CAPM. Scope Management: collect requirements (gather stakeholder needs), define scope (detailed description of deliverables), create WBS (Work Breakdown Structure — decompose scope into manageable work packages). The WBS is a hierarchical decomposition — the lowest level elements are Work Packages. Schedule Management: define activities (break work packages into schedule activities), sequence activities (identify dependencies — Finish-to-Start is most common), estimate durations, develop schedule. Critical Path Method: the longest path through the network diagram determines project duration — activities on the critical path have zero float. Cost Management: estimate costs (estimate resources and their costs), determine budget (aggregate cost estimates into the cost baseline), plan cost control. Risk Management: identify risks (risk register), perform qualitative analysis (probability-impact matrix), plan risk responses (avoid, mitigate, transfer, accept). Communications Management: identify stakeholder information needs, plan communication channels — formula: N(N-1)/2 gives number of channels for N stakeholders.

Execution, Monitoring, and Change Control

During execution, the PM leads the team and keeps the project on track. Direct and Manage Project Work: execute the plan, manage issues, communicate progress. Manage Project Knowledge: capture and share lessons learned throughout (not just at the end). Monitoring and Controlling: compare actuals to baseline using Earned Value Management (EVM). Key EVM formulas: PV (Planned Value — budgeted cost of work scheduled), EV (Earned Value — budgeted cost of work done), AC (Actual Cost). SV = EV-PV (Schedule Variance), CV = EV-AC (Cost Variance), SPI = EV/PV (Schedule Performance Index), CPI = EV/AC (Cost Performance Index). Values below 1.0 indicate problems. EAC (Estimate at Completion) = BAC/CPI when current performance will continue. Integrated Change Control: all change requests must be formally submitted, evaluated for impact on scope/schedule/cost/risk, approved or rejected by the Change Control Board, and tracked. The Project Manager never approves their own changes — the CCB has this authority. Stakeholder Engagement: monitor and manage stakeholder engagement levels — use the engagement assessment matrix (Unaware, Resistant, Neutral, Supportive, Leading).

Key exam facts — CAPM

  • Project Charter authorises the project — signed by sponsor, not the Project Manager
  • WBS decomposes scope into work packages — lowest level elements; planning packages for undefined work
  • Critical Path: longest path = project duration; zero float on critical path activities
  • EVM: CPI = EV/AC; SPI = EV/PV — below 1.0 means behind/over budget
  • Communications channels: N(N-1)/2 — adding one person disproportionately increases complexity
  • All changes go through Integrated Change Control and the CCB — PM does not self-approve
  • Risk responses: Avoid (eliminate), Transfer (insure/contract), Mitigate (reduce), Accept (acknowledge)
  • Closing process: obtain formal acceptance, release resources, document lessons, close contracts
  • CAPM requires 23 hours of project management education — no experience requirement
  • Process groups are not phases — multiple process group activities occur within each project phase

Common exam traps

CAPM is an easier version of PMP covering the same content

CAPM tests foundational knowledge of PMBOK concepts. PMP tests application and judgment in complex scenarios. CAPM is primarily knowledge-based; PMP is primarily situational. Both test PMBOK but at different cognitive levels.

The WBS lists tasks and activities

The WBS decomposes the project SCOPE into deliverables and components — it represents what will be produced, not what activities will be done. Activities are derived from work packages and documented in the activity list, which feeds schedule development.

Practice this topic

Test yourself on CAPM Fundamentals

JT Exams routes you to questions in your exact weak areas — automatically, after every session.

No credit card · Cancel anytime

Related certification topics