CAPM-Specific Concepts

CAPM Exam Overview

The Certified Associate in Project Management (CAPM) is a PMI credential designed for entry-level project practitioners who want to demonstrate foundational project management knowledge.

CAPM Eligibility Requirements

To sit for the CAPM exam, candidates must hold a secondary degree (high school diploma, associate degree, or equivalent) and have completed 23 hours of project management education before the exam.

CAPM Exam Format and Structure

The CAPM exam consists of 150 multiple-choice questions to be completed in three hours, delivered at a Pearson VUE test center or via online proctored testing.

CAPM vs PMP

The CAPM is an entry-level PMI certification requiring no project management experience, while the PMP is a professional-level credential requiring substantial experience leading and directing projects.

Project Management Fundamentals (CAPM Domain)

Project Management Fundamentals and Core Concepts is the largest CAPM exam domain (36%), covering foundational PM terminology, roles, structures, and the relationship between projects, programs, and portfolios.

Predictive Plan-Based Methodologies (CAPM Domain)

Predictive Plan-Based Methodologies is a CAPM exam domain (17%) that covers the traditional waterfall approach to project management, emphasizing upfront planning, defined scope, and sequential execution.

Agile Frameworks and Methodologies (CAPM Domain)

Agile Frameworks and Methodologies is a CAPM exam domain (20%) that covers iterative and incremental approaches to project delivery, including Scrum, Kanban, Lean, and the values and principles of the Agile Manifesto.

Business Analysis Frameworks (CAPM Domain)

Business Analysis Frameworks is a CAPM exam domain (27%) that covers needs assessment, stakeholder analysis, requirements management, traceability, and solution evaluation from a business analysis perspective.

Needs Assessment

Needs assessment is the process of identifying and analyzing a business problem or opportunity to determine whether a project or solution is justified and to define the desired future state.

Business Requirements

Business requirements describe the high-level needs of the organization, including why the project is being undertaken, the business goals it supports, and the measurable objectives it must achieve.

Stakeholder Requirements

Stakeholder requirements describe the needs of individual stakeholders or stakeholder groups, including what they need the solution to do for them in order to meet the business requirements.

Solution Requirements

Solution requirements describe the characteristics, features, and capabilities that a solution must possess to meet business and stakeholder requirements. They are divided into functional and non-functional requirements.

Functional Requirements

Functional requirements describe the specific behaviors, features, and capabilities a solution must provide, defining what the system should do in response to inputs or conditions.

Non-Functional Requirements

Non-functional requirements describe the quality attributes, constraints, and performance standards a solution must meet, specifying how well the system should perform rather than what it should do.

Transition Requirements

Transition requirements describe the temporary capabilities, data conversions, training, and activities needed to move from the current state to the future state when a solution is deployed.

Requirements Prioritization

Requirements prioritization is the process of ranking requirements by importance, urgency, risk, and business value to determine the order in which they should be addressed given constraints on time, budget, and resources.

Traceability and Monitoring

Traceability and monitoring is the practice of tracking each requirement from its origin through design, development, testing, and delivery to ensure completeness, manage changes, and verify that all requirements are satisfied.

Solution Evaluation

Solution evaluation is the process of assessing whether a delivered solution meets the business requirements, achieves the expected benefits, and delivers the value that justified the project.

Business Analysis Planning

Business analysis planning defines the approach, activities, deliverables, and resources needed to perform business analysis on a project, ensuring requirements work is structured and aligned with project objectives.

Elicitation Techniques (Business Analysis)

Elicitation techniques are structured methods used by business analysts to gather requirements and information from stakeholders, including interviews, workshops, observation, surveys, document analysis, prototyping, and brainstorming.