Skarp
CAPM Mastery: Comprehensive Exam-Ready Prep for the Modern CAPM (PMI)
A deep, exam-focused CAPM preparation course aligned to the current PMI Exam Content Outline (effective July 2023), covering project management fundamentals, predictive plan-based methodologies, agile frameworks, and business analysis frameworks. Designed to build calculation skills, conceptual clarity, and test-taking confidence so you can pass the CAPM and apply the knowledge on real projects.
Course Content
21 modules · 9h 27m total
Orientation: Navigating the New CAPM Exam and Study Strategy
Step behind the scenes of the updated CAPM exam and see exactly how PMI’s four domains, tasks, and enablers translate into the questions you’ll face—and how to build a focused study plan that hits the highest‑value topics first.
Projects, Operations, and Life Cycles: Foundations for CAPM
Before you tackle formulas or frameworks, you need rock‑solid clarity on what a project is, how it differs from operations, and how different life cycles shape everything else you’ll learn.
Stakeholders, Governance, and the Project Manager’s Integration Role
Who really holds power on a project, how do decisions get made, and how does a project manager keep everything—from scope to stakeholders—moving in sync?
Roles, Responsibilities, and Communication Across the Project Ecosystem
Step into the shoes of sponsors, product owners, functional managers, and business analysts to see how their decisions, conflicts, and communication styles shape project outcomes.
Cost Management Essentials: Estimates, Baselines, and Reserves
Money talk on projects goes far beyond a single budget line—discover how estimates, baselines, and reserves really work and how the exam expects you to classify and roll them up.
Quality Management and the Cost of Quality Framework
Go beyond buzzwords like ‘quality assurance’ and ‘quality control’ to see how prevention, inspection, and failure costs show up in real projects—and on tricky exam questions.
Scope Foundations: From Requirements to the Work Breakdown Structure
See how vague ideas from stakeholders are transformed into a clear, structured picture of all the work the team must deliver—without leaving dangerous gaps or overlaps.
Predictive Scheduling I: Network Diagrams, Dependencies, and Critical Path Method
Turn a list of activities into a visual schedule model, uncover the true drivers of your end date, and practice the kinds of critical path questions the CAPM loves to ask.
Predictive Scheduling II: Float, Compression, and Schedule Performance
Once the schedule is built, the real exam challenge begins: calculating float, choosing the right compression technique, and interpreting schedule variance under pressure.
Scope and Change Control in Predictive Projects
When stakeholders disagree about what was promised or request late changes, your mastery of baselines, validation, and change control can make or break both the project and the exam question.
Predictive Team and Resource Management in Functional and Matrix Environments
In many CAPM scenarios, you don’t control who works for you—learn how to negotiate for people, resolve conflicts, and keep the team performing within real‑world organizational constraints.
Agile Mindset and Empirical Process Control
Shift from plan‑driven thinking to an agile mindset grounded in transparency, inspection, and adaptation, and see why agile thrives when change is constant and early feedback is essential.
Scrum Deep Dive: Roles, Events, Artifacts, and the Product Backlog
Walk through a Scrum sprint from backlog refinement to review and retrospective, and master the terminology and responsibilities that show up again and again on CAPM agile questions.
Kanban and Extreme Programming (XP): Flow, Quality, and Technical Excellence
Not all agile teams sprint—some flow. Discover how Kanban and XP manage work, limit multitasking, and bake quality into the code from the start.
Agile Planning, Estimation, and Forecasting with Backlogs and Velocity
See how agile teams turn a dynamic product backlog into realistic forecasts, even when scope is still evolving and stakeholders keep refining their ideas.
Hybrid Approaches: Coordinating Predictive and Adaptive Components
Many real projects—and exam questions—live in the messy middle, where contracts, governance, and agile teams must coexist. Learn how to connect these worlds without chaos.
Business Analysis Foundations: Roles, Stakeholders, and Elicitation Techniques
Step into the business analyst’s world to see how they uncover real needs, manage diverse stakeholders, and choose the right elicitation techniques for each situation.
Requirements Analysis, Traceability, and the Product Backlog in BA
Trace every requirement from its origin to delivered value, and see how tools like the requirements traceability matrix and product backlog keep complex change under control.
Process Modeling and Analysis: From Current State to Future State
Visualize how work really flows through an organization, spot bottlenecks and waste, and design leaner future‑state processes that still satisfy required controls.
Prioritization, Decision Modeling, and Solution Evaluation
When you can’t build everything, you must decide what matters most—learn how to prioritize requirements, model decisions, and evaluate whether solutions actually delivered value.
CAPM Exam Readiness: Integrated Review, Drills, and Test‑Day Strategy
Bring everything together in a targeted review that mirrors the exam’s mix of predictive, agile, and business analysis questions—then craft your personal game plan for exam day.
Read the Textbook
Read every chapter for free, right here in your browser.
In this orientation, you will get a clear, practical map of the current CAPM exam so you can study with precision instead of guessing. The exam you are preparing for is the current Certified Associate in Project Management (CAPM), aligned with the 2023 Exam Content Outline (ECO) that PMI introduced to modernize the credential.
The biggest shift in this version is that the exam is now structured around four domains, not just traditional process groups or a single guide. These domains reflect how real projects are actually run today: mixing predictive and agile approaches and tying project work closely to business analysis.
The four CAPM Exam Domains (in order) are: Project Management Fundamentals and Core Concepts Predictive, Plan-Based Methodologies Agile Frameworks/Methodologies Business Analysis Frameworks
Study Flashcards
Key concepts from this course as flashcard pairs.
Orientation: Navigating the New CAPM Exam and Study Strategy
Define: project
A temporary endeavor undertaken to create a unique product, service, or result.
Define: stakeholder
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
Define: predictive life cycle
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
Define: adaptive life cycle
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
Define: work breakdown structure
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
Define: work package
The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
+4 more flashcards
Projects, Operations, and Life Cycles: Foundations for CAPM
Project (PMI canonical definition)
A temporary endeavor undertaken to create a unique product, service, or result.
Stakeholder (PMI canonical definition)
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
Predictive life cycle (PMI canonical definition)
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
Adaptive life cycle (PMI canonical definition)
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
Project life cycle vs product life cycle
Project life cycle: phases a project goes through from start to finish. Product life cycle: stages a product or service goes through in the market from introduction to retirement.
Predictive approach
Project management approach that relies mainly on a predictive life cycle, with detailed up-front planning and tight change control, suited to stable requirements and strict governance.
+4 more flashcards
Stakeholders, Governance, and the Project Manager’s Integration Role
Stakeholder (canonical definition)
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
Stakeholder register
A living document that lists project stakeholders and key information about them, such as role, power, interest, attitude, desired engagement, and communication preferences.
Power/interest grid
A stakeholder analysis tool that maps stakeholders by their level of power (influence) and interest in the project, guiding strategies like collaborate closely, keep satisfied, keep informed, or monitor.
Phase gate
A governance checkpoint at the end of a project phase where decision makers review performance, risks, and the business case to decide whether to continue, modify, or terminate the project.
Change Control Board (CCB)
A formally chartered group that reviews, evaluates, and approves, defers, or rejects change requests, based on their impact on scope, schedule, cost, quality, risk, and stakeholders.
Escalation path
A predefined route for raising issues or risks beyond the project manager’s authority, specifying when and to whom items are escalated.
+5 more flashcards
Roles, Responsibilities, and Communication Across the Project Ecosystem
Project sponsor
Senior person who authorizes the project and charter, provides funding, champions the project, and is ultimately accountable for realizing business benefits and approving major changes.
Project manager
Person responsible for achieving project objectives, integrating all knowledge areas, leading the team, managing trade-offs, and recommending (but usually not unilaterally approving) major changes.
Product owner
Role that owns and manages the product backlog, prioritizes items for value and risk, defines acceptance criteria, and accepts or rejects increments in adaptive approaches.
Product manager
Role with a strategic focus on product vision, roadmap, and market alignment, often spanning multiple projects or releases beyond a single team’s backlog.
Functional manager
Manager of a department or function who controls staffing, performance evaluations, and functional standards, and negotiates resource availability for projects.
PMO types
Supportive (low control, provides templates/guidance), Controlling (moderate control, enforces standards), Directive (high control, directly manages projects and PMs).
+4 more flashcards
Cost Management Essentials: Estimates, Baselines, and Reserves
Analogous estimating
A top‑down estimating technique that uses the actual cost of a previous, similar project or activity as the basis for estimating the cost of the current project or activity; fast but less accurate and reliant on expert judgment.
Parametric estimating
An estimating technique that uses a statistical relationship between historical data and other variables (such as cost per unit, productivity rates, or learning curves) to calculate a cost estimate.
Bottom‑up estimating
An estimating method where costs are estimated at the work package or detailed activity level and then aggregated upward through the work breakdown structure to determine total project costs.
Work package
The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
Contingency reserve
Budget (or time) included in the cost baseline to address identified risks (known‑unknowns) that remain after risk responses are planned; controlled by the project manager.
Management reserve
Budget set aside for unforeseen work within the project scope that has not yet been identified; not part of the cost baseline and typically controlled by senior management or the sponsor.
+6 more flashcards
Quality Management and the Cost of Quality Framework
Quality management plan
A component of the project management plan that describes how applicable policies, procedures, and guidelines will be implemented to achieve quality objectives and how the project will meet and verify quality requirements and acceptance criteria.
Quality assurance (QA)
Process-focused, proactive activities that ensure the project uses appropriate processes and standards to prevent defects. Examples: process audits, training, procedure improvements.
Quality control (QC)
Product-focused, reactive activities that inspect and test deliverables to determine whether they meet quality requirements and acceptance criteria. Examples: inspections, testing, defect measurement.
Cost of conformance
The cost of quality-related activities that ensure compliance with requirements: **prevention** (training, process improvement) and **appraisal** (inspections, testing).
Cost of nonconformance
The cost incurred because of failures to meet requirements: **internal failure** (rework, scrap) and **external failure** (warranty, recalls, penalties, lost reputation).
Prevention cost
Money spent to avoid defects by improving processes and planning quality (e.g., training, requirements workshops, preventive maintenance, process improvement).
+4 more flashcards
Scope Foundations: From Requirements to the Work Breakdown Structure
Project (canonical definition)
A temporary endeavor undertaken to create a unique product, service, or result.
Stakeholder (canonical definition)
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
Predictive life cycle (canonical definition)
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
Adaptive life cycle (canonical definition)
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
Work breakdown structure (WBS) (canonical definition)
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
Work package (canonical definition)
The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
+5 more flashcards
Predictive Scheduling I: Network Diagrams, Dependencies, and Critical Path Method
Schedule network diagram
A visual representation of project activities and the logical relationships (dependencies) among them, used to model the project schedule.
Finish-to-Start (FS) relationship
A dependency where the successor activity cannot start until the predecessor activity has finished. This is the most common relationship type.
Lead
An amount of time whereby a successor activity is advanced with respect to a predecessor activity, allowing overlap between them.
Lag
An amount of time whereby a successor activity is delayed with respect to a predecessor activity, representing waiting time between them.
Mandatory dependency (hard logic)
A dependency that is inherent in the nature of the work or required by contract, safety, or regulation; it cannot be easily changed.
Discretionary dependency (soft logic)
A dependency based on best practices or team preference; it can be adjusted to optimize or compress the schedule.
+4 more flashcards
Predictive Scheduling II: Float, Compression, and Schedule Performance
Total float (TF)
The amount of time an activity can be delayed without delaying the project finish date (or a specified completion date). Calculated as TF = LS − ES or TF = LF − EF.
Free float (FF)
The amount of time an activity can be delayed without delaying the early start of any immediate successor. FF = min(ES of successors) − EF of this activity.
Critical path
The sequence of activities that determines the earliest possible completion date of the project. In a simple network, activities on this path have total float = 0.
Fast tracking
A schedule compression technique that involves performing activities in parallel or overlapping them that were originally planned in sequence, often increasing rework and risk.
Crashing
A schedule compression technique that involves adding resources to critical path activities to shorten their duration, which always increases cost.
Resource leveling
A resource optimization technique that adjusts activity start/finish dates based on resource constraints, which may change the critical path and extend the project end date.
+9 more flashcards
Scope and Change Control in Predictive Projects
predictive life cycle
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
work breakdown structure (WBS)
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
work package
The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
acceptance criteria
A set of conditions that is required to be met before deliverables are accepted.
requirements traceability matrix
A grid that links product requirements from their origin to the deliverables that satisfy them.
Validate Scope vs Control Quality
Control Quality is internal checking of deliverables against quality standards; Validate Scope is external customer acceptance of verified deliverables against the scope baseline and requirements.
+2 more flashcards
Predictive Team and Resource Management in Functional and Matrix Environments
Functional organization
An organizational structure where work is grouped by specialty (e.g., IT, HR) and functional managers control staff and budgets. Project managers have low authority and must request resources.
Matrix organization (weak, balanced, strong)
A structure where staff report to both functional and project managers. Weak matrix is closer to functional (functional manager dominant), strong matrix is closer to projectized (project manager stronger), balanced matrix shares authority more equally.
Projectized organization
An organizational structure where most people work in projects and report to project managers, who have high authority over resources, schedule, and budget.
Resource breakdown structure (RBS)
A hierarchical list of resources by category or type (such as role, department, internal/external) used to organize and plan resource needs.
Resource calendar
A calendar that shows the working days, shifts, and planned unavailability (vacations, maintenance, training) for specific resources such as people or equipment.
Resource histogram
A bar chart that shows the quantity of a resource (e.g., number of developers) needed over time, useful for spotting peaks and over-allocation.
+5 more flashcards
Agile Mindset and Empirical Process Control
Predictive life cycle
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
Adaptive life cycle
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
Empirical process control
A way of managing work that relies on transparency, inspection, and adaptation so decisions are based on observed reality rather than detailed upfront predictions.
Product backlog
An ordered list of everything that is known to be needed in the product, managed by the product owner.
Iterative delivery
An approach where the same part of the product is refined through repeated cycles to improve quality or understanding.
Incremental delivery
An approach where new, complete pieces of functionality are added over time, with each increment being usable and potentially releasable.
+5 more flashcards
Scrum Deep Dive: Roles, Events, Artifacts, and the Product Backlog
Product backlog (canonical definition)
An ordered list of everything that is known to be needed in the product, managed by the product owner.
Acceptance criteria (canonical definition)
A set of conditions that is required to be met before deliverables are accepted.
Definition of Done
A shared, explicit quality standard for all work; an item that does not meet the Definition of Done is not considered Done and cannot be part of the increment.
Increment
The sum of all completed product backlog items; it must be usable and meet the Definition of Done at the end of each sprint.
Sprint Backlog
The set of product backlog items selected for the sprint, plus a plan for delivering them; owned and updated by Developers.
Daily Scrum
A 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours; it is not a status meeting.
+4 more flashcards
Kanban and Extreme Programming (XP): Flow, Quality, and Technical Excellence
Kanban board
A visual representation of the workflow, typically with columns such as To Do, In Progress, Testing, and Done, where cards representing work items move from left to right.
Work-in-progress (WIP) limit
A cap on the number of work items that can be in a given state or column at one time, used in Kanban to reduce multitasking and improve flow.
Pull-based work selection
An approach where team members start new work only when they have capacity, pulling the next item from a queue instead of having work pushed onto them.
Cycle time (Kanban)
The elapsed time from when a work item starts active work (e.g., enters In Progress) until it is completed (Done).
Pair programming (XP)
An XP practice where two developers work together at one workstation, with one typing (driver) and the other reviewing and thinking ahead (navigator).
Test-driven development (TDD)
An XP practice where developers write a failing automated test first, then write minimal code to make it pass, and finally refactor while keeping tests green.
+4 more flashcards
Agile Planning, Estimation, and Forecasting with Backlogs and Velocity
product backlog
An ordered list of everything that is known to be needed in the product, managed by the product owner.
adaptive life cycle
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
acceptance criteria
A set of conditions that is required to be met before deliverables are accepted.
stakeholder
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
velocity (agile context)
The amount of work a team completes in an iteration, typically measured in story points, based only on items that meet the Definition of Done.
Definition of Done (DoD)
A shared understanding of what it means for work to be completely finished and potentially releasable, usually expressed as a checklist that applies to all backlog items.
+2 more flashcards
Hybrid Approaches: Coordinating Predictive and Adaptive Components
predictive life cycle
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
adaptive life cycle
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
product backlog
An ordered list of everything that is known to be needed in the product, managed by the product owner.
requirements traceability matrix
A grid that links product requirements from their origin to the deliverables that satisfy them.
acceptance criteria
A set of conditions that is required to be met before deliverables are accepted.
work breakdown structure (WBS)
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
+4 more flashcards
Business Analysis Foundations: Roles, Stakeholders, and Elicitation Techniques
project
A temporary endeavor undertaken to create a unique product, service, or result.
stakeholder
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
predictive life cycle
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
adaptive life cycle
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
product backlog
An ordered list of everything that is known to be needed in the product, managed by the product owner.
requirements traceability matrix
A grid that links product requirements from their origin to the deliverables that satisfy them.
+4 more flashcards
Requirements Analysis, Traceability, and the Product Backlog in BA
Requirements traceability matrix
A grid that links product requirements from their origin to the deliverables that satisfy them.
Product backlog
An ordered list of everything that is known to be needed in the product, managed by the product owner.
Acceptance criteria
A set of conditions that is required to be met before deliverables are accepted.
Adaptive life cycle
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
Purpose of a requirements traceability matrix
To link requirements back to their sources (stakeholders, objectives, regulations) and forward to design elements and test cases, enabling coverage checks and impact analysis.
Testable requirement
A requirement that is specific and measurable so that objective pass/fail test cases can be defined against it.
+2 more flashcards
Process Modeling and Analysis: From Current State to Future State
Current-state (as-is) process
A model of how work actually happens today, including real behaviors, workarounds, delays, and rework, used as a baseline for analysis and improvement.
Future-state (to-be) process
A model of how work is intended to happen after changes, designed to reduce waste and risk while preserving required controls and compliance.
Swimlane process map
A diagram that shows process activities over time, organized into lanes representing roles, teams, or systems, highlighting handoffs and responsibilities.
SIPOC
A high-level diagram summarizing Suppliers, Inputs, Process, Outputs, and Customers for a process, used to clarify scope and context.
Value stream map
A visualization of the flow of value from request to delivery, including processing times, wait times, queues, and information flows, used to identify waste.
Value-added activity
An activity that directly changes the product or service in a way the customer cares about and that must be done right the first time.
+5 more flashcards
Prioritization, Decision Modeling, and Solution Evaluation
MoSCoW prioritization
A technique that categorizes requirements into Must-have, Should-have, Could-have, and Won't-have (this time), helping stakeholders make explicit trade-offs under constraints.
Decision gateway
A point in a process model where the flow branches based on conditions (e.g., yes/no, approved/rejected), representing different possible paths and outcomes.
Decision table
A structured grid that lists conditions and corresponding actions or outcomes, used to analyze and implement complex business rules and ensure all combinations are covered.
Cause-and-effect (fishbone) diagram
A root cause analysis tool that starts with a problem and visually organizes possible causes into categories such as People, Process, Technology, Policy, and Environment.
Pre-implementation metric (baseline)
A measurement taken before a solution is implemented, used as a reference point to compare with post-implementation results and determine whether value was delivered.
Segmented solution evaluation
Assessing solution performance separately for different stakeholder groups or user segments to see whether each group’s needs are met and to uncover hidden issues.
+4 more flashcards
CAPM Exam Readiness: Integrated Review, Drills, and Test‑Day Strategy
project
A temporary endeavor undertaken to create a unique product, service, or result.
stakeholder
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
predictive life cycle
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
adaptive life cycle
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
work breakdown structure
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
work package
The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
+5 more flashcards