Skarp
CAPM Exam Mastery: Project Management, Predictive, Agile, and Business Analysis Foundations
A deep, exam-focused preparation program for the current PMI Certified Associate in Project Management (CAPM) exam, aligned to the official Exam Content Outline. You will build a rigorous understanding of project management fundamentals, predictive and agile approaches, and core business analysis practices needed to pass with confidence and perform on real projects.
Course Content
20 modules · 9h total
CAPM Exam Orientation, Strategy, and Study Roadmap
Step into the CAPM journey with a clear map: how the exam is structured, what each domain really tests, and how to turn the Exam Content Outline into a practical study and practice plan.
Projects, Operations, and the Project Environment
Before tackling tools and techniques, anchor your understanding in what a project actually is, how it differs from ongoing operations, and the environments where projects live.
Project Life Cycles, Development Approaches, and Governance
Trace how a project moves from concept to closure, and see how different development life cycles—predictive and adaptive—shape planning, control, and governance.
Stakeholders, Stakeholder Register, and Risk Register Essentials
Dive into the people and uncertainties that shape every project: who your stakeholders are, how to document them, and how to systematically capture and track risks.
Roles, Responsibilities, Cost, and Quality Fundamentals
Clarify who does what on a project and how foundational cost and quality concepts guide decisions, trade-offs, and performance measurement.
Scope Foundations and the Work Breakdown Structure
Turn broad ideas into a clear, manageable picture of the work by structuring scope with a work breakdown structure and defining work packages you can estimate and control.
Scheduling Predictive Projects: Network Diagrams and Critical Path Method
See how activities become a realistic schedule by sequencing work, estimating durations, and using the critical path method to reveal where delays really matter.
Controlling Predictive Projects: Schedule Variance, Cost, and Project Controls
Move beyond static plans into active control by tracking performance, interpreting schedule variance, and using key artifacts to keep predictive projects on track.
Resource and Quality Management in Predictive Projects
Connect people, materials, and quality expectations to your predictive plan so that resources are available when needed and deliverables meet agreed standards.
Adaptive and Agile Mindset: When to Use an Adaptive Approach
Shift your thinking from locking down scope to embracing change by understanding when adaptive approaches shine and how they differ from predictive planning.
Scrum Fundamentals: Roles, Events, and Artifacts
Walk through a Scrum sprint from vision to increment, meeting the key players, events, and artifacts that structure one of the most widely used agile frameworks.
Kanban, Flow-Based Work, and Extreme Programming (XP) Basics
Discover how Kanban visualizes work and manages flow, and how Extreme Programming (XP) uses disciplined engineering practices to boost quality and responsiveness.
Planning and Executing in Agile: Backlogs, Estimation, and Delivery
See how agile teams turn a vision into a prioritized backlog, size and forecast work, and deliver value iteratively and incrementally.
Hybrid Life Cycles and Tailoring Across Predictive and Agile
Blend the best of both worlds by examining how real projects mix predictive and adaptive elements, and how CAPM candidates should think about tailoring approaches.
Business Analysis Roles, Stakeholders, and Communication
Step into the business analysis perspective to see how BA roles interact with project stakeholders and how effective communication underpins successful change.
Requirements Elicitation Techniques and Requirements Quality
Go beyond “gathering requirements” to use structured elicitation techniques and quality checks that ensure requirements are clear, feasible, and testable.
Requirements Analysis, Prioritization, and the Requirements Traceability Matrix
Transform raw requirements into an organized, traceable set of needs by analyzing, grouping, and prioritizing them and linking them through a requirements traceability matrix.
Agile Requirements: Product Backlog, Roadmaps, and Validation
See how agile teams manage evolving requirements through product backlogs and roadmaps, and how they validate that what was built truly meets stakeholder needs.
Solution Evaluation, Benefits, and Business Value
Complete the business analysis picture by evaluating delivered solutions, measuring benefits, and feeding insights back into future project and product decisions.
CAPM Exam Review, Integrated Scenarios, and Test-Taking Tactics
Bring it all together with integrated scenarios that cross predictive, agile, and business analysis domains, and sharpen the exam tactics you’ll use on test day.
Read the Textbook
Read every chapter for free, right here in your browser.
In this module, you will build a clear mental map of the current Certified Associate in Project Management (CAPM) exam and turn it into a concrete study roadmap.
As of today (about 2 years after PMI’s major CAPM refresh in early 2024), the exam is fully aligned with modern project management, agile, and business analysis practices. It is no longer just a mini-PMP; it explicitly tests predictive, agile, and business analysis skills.
Key exam facts (current version): Total questions: 150 Scored questions: 135 Pretest (unscored) questions: 15 (mixed in; you cannot tell which they are) Total time: 3 hours (180 minutes) Format: Multiple-choice and multiple-response, with scenario-style questions becoming more common Scoring: PMI uses psychometric analysis; there is no published fixed “pass score” like 61%. Questions have different difficulty weights.
Study Flashcards
Key concepts from this course as flashcard pairs.
CAPM Exam Orientation, Strategy, and Study Roadmap
Definition of project
A project is "A temporary endeavor undertaken to create a unique product, service, or result."
Definition of stakeholder
A stakeholder is "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."
CAPM exam domains in canonical order
1) Project Management Fundamentals and Core Concepts 2) Predictive (Plan-Based) Methodologies 3) Agile Frameworks and Methodologies 4) Business Analysis Frameworks
Definition of predictive life cycle
A predictive life cycle is "A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle."
Definition of adaptive life cycle
An adaptive life cycle is "A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration."
Definition of work breakdown structure (WBS)
A work breakdown structure is "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
Projects, Operations, and the Project Environment
Project (PMI canonical definition)
A project is: **"A temporary endeavor undertaken to create a unique product, service, or result."**
Key difference: Project vs Operations
**Project:** temporary, unique output, defined start and end. **Operations:** ongoing, repetitive work that sustains the business, no defined end date.
Program
A group of related projects (and sometimes related operations) managed in a coordinated way to obtain benefits not available from managing them individually.
Portfolio
A collection of projects, programs, and sometimes operations managed as a group to achieve strategic objectives such as growth, innovation, or cost reduction.
Functional Organization
Structure where people are grouped by specialty (e.g., marketing, IT). Functional managers control resources; project managers have low authority and may be part-time.
Matrix Organization
Structure where team members report to both functional and project managers. Authority is shared and can be weak, balanced, or strong for the project manager.
+4 more flashcards
Project Life Cycles, Development Approaches, and Governance
Project life cycle
The series of phases that a project goes through from start to finish, typically including concept/initiation, planning, execution with monitoring and controlling, and closure.
Product life cycle
The stages a product passes through from initial idea and introduction to the market, through growth and maturity, until its retirement.
Predictive life cycle (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 (definition)
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
Hybrid life cycle
A development approach that combines elements of predictive and adaptive life cycles, using each where it fits best.
Phase gate / stage gate
A governance point at the end of a phase or major milestone where decision makers review progress and decide to continue, change, pause, or terminate the project.
+4 more flashcards
Stakeholders, Stakeholder Register, and Risk Register Essentials
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.
Stakeholder register (purpose)
A living document that identifies stakeholders and captures information such as their roles, power, interest, attitude, requirements, and preferred engagement and communication approaches to support stakeholder engagement planning.
Risk register (purpose)
A central log of identified risks (threats and opportunities) that records descriptions, categories, probability, impact, priority, owners, response strategies, and status for ongoing risk management.
Power–interest grid: High power / High interest
Manage closely: collaborate, involve in key decisions, and keep them well informed because they can strongly influence the project and care deeply about outcomes.
Power–interest grid: High power / Low interest
Keep satisfied: provide periodic high-level updates and address major concerns, but avoid overloading them with detail.
Contingency reserve vs management reserve
Contingency reserve covers identified risks and is included in the cost baseline. Management reserve covers unknown-unknowns and is not in the cost baseline but is part of the total project budget.
+4 more flashcards
Roles, Responsibilities, Cost, and Quality Fundamentals
project (definition)
A temporary endeavor undertaken to create a unique product, service, or result.
stakeholder (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.
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.
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
Scope Foundations and the Work Breakdown Structure
Predictive life cycle (definition)
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 (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 (definition)
The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
Product scope vs project scope
Product scope: features and characteristics of the product, service, or result. Project scope: the work that needs to be done to deliver that product with those features.
Scope baseline components
Approved project scope statement, work breakdown structure (WBS), and WBS dictionary.
Acceptance criteria (definition)
A set of conditions that is required to be met before deliverables are accepted.
+3 more flashcards
Scheduling Predictive Projects: Network Diagrams and Critical Path Method
Precedence Diagramming Method (PDM)
A method of constructing a schedule network diagram where activities are represented by nodes and are graphically linked by one or more logical relationships (dependencies) to show the sequence in which the activities are to be performed.
Finish-to-Start (FS) relationship
A logical relationship in which a successor activity cannot start until a predecessor activity has finished. It is the most common dependency type in predictive schedules.
Mandatory dependency (hard logic)
A relationship that is legally or contractually required or inherent in the nature of the work. It cannot be changed without changing the work itself.
Discretionary dependency (soft logic)
A relationship that is based on best practices, preferences, or convenience. It can be changed if needed, for example to compress the schedule.
Early Start (ES) and Early Finish (EF)
ES is the earliest time an activity can start given its predecessors. EF is the earliest time it can finish, calculated as ES plus its duration.
Late Start (LS) and Late Finish (LF)
LS is the latest time an activity can start without delaying the project finish. LF is the latest time it can finish without delaying the project finish.
+5 more flashcards
Controlling Predictive Projects: Schedule Variance, Cost, and Project Controls
schedule variance (SV) – definition
A measure of schedule performance expressed as the difference between earned value and planned value.
Schedule variance (SV) – formula
SV = EV − PV. Positive SV means ahead of schedule; negative SV means behind schedule; zero SV means on schedule.
Planned Value (PV)
The authorized budget assigned to the work scheduled to be completed by a given date. Answers: “According to the plan, how much value should we have earned by now?”
Earned Value (EV)
The measure of work performed expressed in terms of the budget authorized for that work. Answers: “Given what we actually completed, how much value have we earned?”
Actual Cost (AC)
The realized cost incurred for the work performed during a given time period. Answers: “How much have we actually spent so far?”
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.
+5 more flashcards
Resource and Quality Management in Predictive Projects
Resource calendar
A calendar that identifies the working days and shifts on which each specific resource is available, as well as nonworking times such as holidays, vacations, and other commitments. It constrains when activities requiring that resource can be scheduled.
Resource histogram
A bar chart showing the amount of a resource used over time, such as the number of developers needed each week. It is used to detect over-allocation and under-utilization.
Resource leveling
A resource optimization technique in which start and finish dates are adjusted based on resource constraints with the goal of balancing demand for resources with the available supply. It can change the critical path and project end date.
Resource smoothing
A resource optimization technique that adjusts the activities of a schedule model such that the requirements for resources on the project do not exceed certain predefined resource limits. It does not change the project completion date or the critical path and only uses float.
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.
+4 more flashcards
Adaptive and Agile Mindset: When to Use an Adaptive Approach
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.
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.
acceptance criteria
A set of conditions that is required to be met before deliverables are accepted.
Iterative vs Incremental
Iterative: refine the same product through repeated cycles. Incremental: deliver new usable chunks of functionality over time.
+4 more flashcards
Scrum Fundamentals: Roles, Events, and Artifacts
Scrum
A lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems, using defined roles, events, and artifacts.
Product Backlog
An ordered list of everything that is known to be needed in the product, managed by the product owner.
Product Owner
The single person accountable for maximizing the value of the product and managing and ordering the product backlog.
Scrum Master
A servant-leader for the Scrum Team and organization who coaches in Scrum, removes impediments, and helps everyone understand and apply the framework.
Developers (Scrum)
Members of the Scrum Team committed to creating any aspect of a usable Increment each Sprint; cross-functional and self-managing.
Sprint
A fixed-length (1–4 week) timebox during which a usable, potentially releasable Increment is created; the container for all other Scrum events.
+4 more flashcards
Kanban, Flow-Based Work, and Extreme Programming (XP) Basics
Kanban
A flow-based method for managing work that emphasizes visualizing workflow, limiting work-in-progress, and improving flow using metrics like cycle time and throughput.
Work-in-progress (WIP) limit
A policy that sets the maximum number of work items allowed in a given workflow stage or column at one time, used to reduce multitasking and improve flow.
Cycle time
The amount of time from when work starts on an item until it is completed. It reflects how long the team actively works on the item.
Lead time
The total time from when a request is made until it is completed, representing how long a stakeholder waits from request to delivery.
Throughput
The number of work items completed per unit of time, such as items per week, used to understand and forecast delivery capacity.
Extreme Programming (XP)
An agile software development approach focused on technical excellence and frequent delivery, using practices like pair programming, test-driven development, continuous integration, and refactoring.
+5 more flashcards
Planning and Executing in Agile: Backlogs, Estimation, and Delivery
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.
velocity
The amount of work a team completes in an iteration, usually measured in story points, based on items that meet the Definition of Done.
Planning Poker
A collaborative agile estimation technique where team members independently select story point values, reveal them simultaneously, discuss differences, and re-vote until they converge.
Minimum Viable Product (MVP)
The smallest set of features that delivers real value to users and enables meaningful learning about the product direction.
+1 more flashcards
Hybrid Life Cycles and Tailoring Across Predictive and Agile
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.
Hybrid life cycle (concept)
An approach that intentionally combines predictive and adaptive elements within a single project or program, often using predictive planning and governance with agile delivery for parts of the work.
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.
product backlog
An ordered list of everything that is known to be needed in the product, managed by the product owner.
+4 more flashcards
Business Analysis Roles, Stakeholders, and Communication
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 Elicitation Techniques and Requirements Quality
Functional requirement
Describes what the system, product, or process must do (its behaviors, features, or services), for example, "The system shall allow users to reset their password via email."
Nonfunctional requirement
Describes how well or under what conditions the solution must perform (performance, security, usability, reliability, etc.), for example, "The system shall display the dashboard within 2 seconds for 95% of requests."
Acceptance criteria (canonical definition)
Acceptance criteria: "A set of conditions that is required to be met before deliverables are accepted."
Interview vs workshop
Interviews: one-on-one or small-group, good for depth and sensitive topics. Workshops: facilitated group sessions to build shared understanding, resolve conflicts, and prioritize requirements.
Observation (in elicitation)
Watching stakeholders perform their work (passive or active) to uncover real workflows, workarounds, and bottlenecks that may not appear in documented procedures.
Survey/questionnaire (in elicitation)
Structured set of questions sent to many stakeholders, useful for gathering input from geographically distributed groups and validating patterns found in interviews or observation.
+2 more flashcards
Requirements Analysis, Prioritization, and the Requirements Traceability Matrix
requirements traceability matrix
A grid that links product requirements from their origin to the deliverables that satisfy them.
MoSCoW categories
Must-have, Should-have, Could-have, Won’t-have (this time). Used to prioritize requirements and features.
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.
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
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
Agile Requirements: Product Backlog, Roadmaps, and Validation
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.
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 roadmap (concept)
A visual, time-oriented plan that shows how major product outcomes, features, or epics will be delivered over time to support strategy. It connects high-level vision to the product backlog.
release (in agile)
A deployable package of functionality that delivers value to users, often combining the results of several iterations.
+2 more flashcards
Solution Evaluation, Benefits, and Business Value
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.
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.
+4 more flashcards
CAPM Exam Review, Integrated Scenarios, and Test-Taking Tactics
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