Are flashcards effective for the CAPM exam?

Yes. Flashcards use active recall — retrieving an answer from memory — which research shows is one of the most effective study methods, especially in short, spaced sessions. They're ideal for the CAPM's heavy terminology: EVM formulas, agile roles, requirement types, and project concepts.

What topics do the CAPM flashcards cover?

All four ECO domains: Fundamentals (life cycles, roles, planning), Predictive (scope, WBS, critical path, earned value), Agile (Scrum, Kanban, iterations), and Business Analysis (requirements, traceability, roadmaps), plus a Foundations deck of exam concepts and the PMI mindset.

How should I study with these CAPM flashcards?

Lead with the highest-weighted domains — Fundamentals (36%) and Business Analysis (27%) — then Agile and Predictive. Mix the modes: flip to learn, type to test recall, match for speed, and quiz to check yourself before a full practice test. Drill the EVM and requirements decks until they're automatic.

Are the CAPM flashcards free?

Yes — 100% free, all four study modes, no paywall and no sign-up.

Do these flashcards match the current CAPM exam?

Yes. The cards follow PMI's current 2023 Examination Content Outline and the PMBOK Guide. No CAPM content change is announced — the July 9, 2026 update applies to the PMP, not the CAPM — so these cards reflect the active exam.

The Certified Associate in Project Management — PMI's entry-level credential for those starting a project-management career or supporting projects.

The Project Management Institute — the body that issues the CAPM and PMP and publishes the PMBOK Guide.

A Guide to the Project Management Body of Knowledge — PMI's standard; the 7th edition is principle- and value-based.

How many questions are on the CAPM exam?

150 multiple-choice questions, answered in a single 3-hour (180-minute) session.

How long is the CAPM exam?

180 minutes (3 hours) for 150 questions.

The four CAPM domains (2023 ECO)

Project Management Fundamentals & Core Concepts (36%), Predictive Plan-Based Methodologies (17%), Agile Frameworks/Methodologies (20%), and Business Analysis Frameworks (27%).

A secondary degree (high-school diploma, GED, or global equivalent) plus 23 hours of project-management education completed before the exam.

CAPM is the entry-level credential (no experience required, 23 contact hours); PMP is advanced and requires months of leading projects plus 35 contact hours.

How is the CAPM scored?

Pass/fail. PMI sets the cut score psychometrically based on question difficulty; it does not publish a fixed passing percentage.

CAPM certification validity

Three years; renew by earning 15 PDUs (professional development units) in the CCR cycle.

Where is the CAPM exam taken?

At a Pearson VUE test center or via online proctored testing from home.

Any individual, group, or organization that can affect, be affected by, or perceive itself affected by the project.

A temporary endeavor undertaken to create a unique product, service, or result; it has a definite start and end.

What makes a project 'temporary'?

It has a defined beginning and end — it ends when objectives are met, when it's terminated, or when the need no longer exists.

A group of related projects managed together to obtain benefits not available by managing them individually.

A collection of projects, programs, and operations managed as a group to achieve strategic business objectives.

Operations vs. projects

Operations are ongoing and repetitive (keeping the business running); projects are temporary and unique (creating change).

The series of phases a project passes through from start to completion: starting, organizing & preparing, carrying out the work, and closing.

The person assigned by the performing organization to lead the team responsible for achieving the project objectives.

The person or group that provides resources and support and is accountable for enabling the project's success.

The document that formally authorizes the project, names the project manager, and grants authority to apply resources.

A leadership style focused on serving and developing the team — removing impediments and enabling self-organization — rather than commanding.

Functional organization

A traditional hierarchy grouped by specialty; the functional manager holds authority and the project manager has little.

Projectized organization

An organization structured around projects; the project manager has high authority and resources report to them.

A blend of functional and projectized structures; authority is shared, ranging from weak to strong matrix.

PMO (Project Management Office)

An organizational unit that standardizes project governance and shares resources, methodologies, tools, and techniques.

Enterprise environmental factors (EEFs)

Conditions outside the team's control (culture, market, regulations, infrastructure) that influence the project.

Organizational process assets (OPAs)

The organization's own plans, processes, policies, templates, and knowledge bases used on projects.

The interrelated balance of scope, schedule (time), and cost; changing one usually affects the others, with quality at the center.

The 12 PMBOK 7 principles (purpose)

Value-based guides for behavior (stewardship, team, stakeholders, value, systems thinking, leadership, tailoring, quality, complexity, risk, adaptability, change).

The 8 project performance domains (PMBOK 7)

Stakeholders, Team, Development approach & life cycle, Planning, Project work, Delivery, Measurement, and Uncertainty.

Deliberately adapting the approach, processes, and artifacts to fit the specific project context — there is no one-size-fits-all.

The worth, importance, or usefulness of something; projects exist to deliver value to stakeholders and the organization.

Any unique, verifiable product, result, or capability produced to complete a process, phase, or project.

A significant point or event in the project; it has zero duration and marks the completion of a major deliverable or phase.

A limiting factor that affects how the project is executed (e.g., a fixed budget, deadline, or required technology).

A factor considered true, real, or certain for planning purposes without proof; assumptions carry risk if wrong.

The documented justification for a project, showing the need, options, costs, and expected benefits and value.

Benefits management plan

Describes how and when a project's benefits will be delivered and measured against the business case.

Progressive elaboration

Continuously improving and detailing a plan as more information becomes known — not the same as uncontrolled change.

Project management plan

The integrated document that defines how the project is executed, monitored, controlled, and closed; it includes the baselines and subsidiary plans.

An approved version of a plan (scope, schedule, or cost) against which actual performance is measured; change only via change control.

Emotional intelligence

The ability to recognize and manage one's own emotions and read and influence others' — foundational to leading a team.

A stakeholder-analysis tool mapping each stakeholder by power and interest to decide how closely to engage them.

A responsibility assignment matrix marking who is Responsible, Accountable, Consulted, and Informed for each task.

Your FREE CAPM Flashcards 2026 – 250+ Cards

Realistic, CAPM exam-style flashcards across all 4 PMI domains — flip, match, type, and quiz yourself on fundamentals, predictive, agile, and business analysis.

Master cards to boost your scoreMaster cards to raise your exam readiness score

How well do you know them?

CAPM Flashcards

CAPM: The Certified Associate in Project Management — PMI's entry-level credential for those starting a project-management career or supporting projects.
PMI: The Project Management Institute — the body that issues the CAPM and PMP and publishes the PMBOK Guide.
PMBOK Guide: A Guide to the Project Management Body of Knowledge — PMI's standard; the 7th edition is principle- and value-based.
How many questions are on the CAPM exam?: 150 multiple-choice questions, answered in a single 3-hour (180-minute) session.
How long is the CAPM exam?: 180 minutes (3 hours) for 150 questions.
The four CAPM domains (2023 ECO): Project Management Fundamentals & Core Concepts (36%), Predictive Plan-Based Methodologies (17%), Agile Frameworks/Methodologies (20%), and Business Analysis Frameworks (27%).
CAPM eligibility: A secondary degree (high-school diploma, GED, or global equivalent) plus 23 hours of project-management education completed before the exam.
CAPM vs. PMP: CAPM is the entry-level credential (no experience required, 23 contact hours); PMP is advanced and requires months of leading projects plus 35 contact hours.
How is the CAPM scored?: Pass/fail. PMI sets the cut score psychometrically based on question difficulty; it does not publish a fixed passing percentage.
CAPM certification validity: Three years; renew by earning 15 PDUs (professional development units) in the CCR cycle.
Where is the CAPM exam taken?: At a Pearson VUE test center or via online proctored testing from home.
Stakeholder: Any individual, group, or organization that can affect, be affected by, or perceive itself affected by the project.
Project: A temporary endeavor undertaken to create a unique product, service, or result; it has a definite start and end.
What makes a project 'temporary'?: It has a defined beginning and end — it ends when objectives are met, when it's terminated, or when the need no longer exists.
Program: A group of related projects managed together to obtain benefits not available by managing them individually.
Portfolio: A collection of projects, programs, and operations managed as a group to achieve strategic business objectives.
Operations vs. projects: Operations are ongoing and repetitive (keeping the business running); projects are temporary and unique (creating change).
Project life cycle: The series of phases a project passes through from start to completion: starting, organizing & preparing, carrying out the work, and closing.
Project manager: The person assigned by the performing organization to lead the team responsible for achieving the project objectives.
Project sponsor: The person or group that provides resources and support and is accountable for enabling the project's success.
Project charter: The document that formally authorizes the project, names the project manager, and grants authority to apply resources.
Servant leadership: A leadership style focused on serving and developing the team — removing impediments and enabling self-organization — rather than commanding.
Functional organization: A traditional hierarchy grouped by specialty; the functional manager holds authority and the project manager has little.
Projectized organization: An organization structured around projects; the project manager has high authority and resources report to them.
Matrix organization: A blend of functional and projectized structures; authority is shared, ranging from weak to strong matrix.
PMO (Project Management Office): An organizational unit that standardizes project governance and shares resources, methodologies, tools, and techniques.
Enterprise environmental factors (EEFs): Conditions outside the team's control (culture, market, regulations, infrastructure) that influence the project.
Organizational process assets (OPAs): The organization's own plans, processes, policies, templates, and knowledge bases used on projects.
Triple constraint: The interrelated balance of scope, schedule (time), and cost; changing one usually affects the others, with quality at the center.
The 12 PMBOK 7 principles (purpose): Value-based guides for behavior (stewardship, team, stakeholders, value, systems thinking, leadership, tailoring, quality, complexity, risk, adaptability, change).
The 8 project performance domains (PMBOK 7): Stakeholders, Team, Development approach & life cycle, Planning, Project work, Delivery, Measurement, and Uncertainty.
Tailoring: Deliberately adapting the approach, processes, and artifacts to fit the specific project context — there is no one-size-fits-all.
Value: The worth, importance, or usefulness of something; projects exist to deliver value to stakeholders and the organization.
Deliverable: Any unique, verifiable product, result, or capability produced to complete a process, phase, or project.
Milestone: A significant point or event in the project; it has zero duration and marks the completion of a major deliverable or phase.
Constraint: A limiting factor that affects how the project is executed (e.g., a fixed budget, deadline, or required technology).
Assumption: A factor considered true, real, or certain for planning purposes without proof; assumptions carry risk if wrong.
Business case: The documented justification for a project, showing the need, options, costs, and expected benefits and value.
Benefits management plan: Describes how and when a project's benefits will be delivered and measured against the business case.
Progressive elaboration: Continuously improving and detailing a plan as more information becomes known — not the same as uncontrolled change.
Project management plan: The integrated document that defines how the project is executed, monitored, controlled, and closed; it includes the baselines and subsidiary plans.
Baseline: An approved version of a plan (scope, schedule, or cost) against which actual performance is measured; change only via change control.
Emotional intelligence: The ability to recognize and manage one's own emotions and read and influence others' — foundational to leading a team.
Power/interest grid: A stakeholder-analysis tool mapping each stakeholder by power and interest to decide how closely to engage them.
RACI chart: A responsibility assignment matrix marking who is Responsible, Accountable, Consulted, and Informed for each task.
Accountable (in RACI): The single person who owns the outcome and signs off — there is exactly one Accountable per task.
Tuckman ladder: The stages of team development: forming, storming, norming, performing, and adjourning.
Storming stage: The team-development stage where conflict surfaces as members assert ideas; the leader should coach and resolve conflict.
Collaborating (conflict mode): Working together to a win-win that addresses everyone's needs — the most effective, durable resolution and usually the preferred answer.
Forcing (conflict mode): Pushing one viewpoint at others' expense — a fast win-lose outcome that breeds resentment.
Withdrawing (conflict mode): Retreating from or postponing the conflict, leaving it unresolved.
Smoothing/accommodating: Emphasizing agreement over differences and conceding your position; a temporary fix at best.
Compromising: Each party gives up something for a partial, lose-lose middle ground.
Communication channels formula: n(n − 1) ÷ 2, where n is the number of people; it counts the possible communication channels in a team.
Lessons learned register: A document recording knowledge gained during the project so it can improve current and future work.
Issue log: A document where current issues (events affecting the project that need resolution) are recorded and tracked to closure.
Project phase: A collection of logically related project activities that culminates in the completion of one or more deliverables.
Phase gate (stage gate): A review at the end of a phase to decide whether to continue, change, or end the project.
Governance: The framework of rules, processes, and authority that guides and oversees project decisions and performance.
Sponsor's role at initiation: Authorizing the project, providing the business case and funding, and signing the project charter.
Predictive (waterfall) life cycle: Scope, schedule, and cost are determined early and the project proceeds through sequential phases; best for stable, well-understood work.
When to use a predictive approach: When requirements are well-defined and stable, the deliverable is clear, and change is expected to be limited.
Scope statement: The description of the project scope, major deliverables, assumptions, and constraints — the basis for future decisions.
Work breakdown structure (WBS): A hierarchical decomposition of the total project scope into deliverables and work packages; nothing outside it is in scope.
100% rule (WBS): The WBS captures all of the project work and only the project work — no more, no less.
Work package: The lowest-level deliverable in the WBS — the unit you estimate, schedule, and assign.
WBS dictionary: A document detailing each WBS component: scope of work, deliverables, owner, milestones, and acceptance criteria.
Scope baseline: The approved scope statement, WBS, and WBS dictionary used to measure scope performance.
Scope creep: The uncontrolled expansion of scope without adjustments to time, cost, and resources.
Gold plating: Adding extras the customer didn't request — wasted effort and added risk for no agreed value.
Critical path: The longest sequence of dependent activities through the schedule; it has zero total float and sets the shortest project duration.
Float (slack): The time an activity can be delayed without delaying the project end date (total float) or the next activity (free float).
Activities on the critical path have how much float?: Zero total float — any delay to a critical-path activity delays the whole project.
Crashing: Compressing the schedule by adding resources to critical-path activities, which raises cost.
Fast tracking: Compressing the schedule by performing activities in parallel that were planned in sequence, which raises risk.
Gantt chart: A bar chart showing the schedule with activity start/finish dates and durations along a timeline.
Network diagram: A schematic showing project activities and their logical dependencies (predecessors and successors).
Finish-to-start (FS) dependency: The most common relationship: a successor activity cannot start until its predecessor finishes.
Lead vs. lag: Lead lets a successor start earlier (overlap); lag delays a successor (a waiting period) relative to its predecessor.
Three-point estimate (PERT): Estimate = (Optimistic + 4 × Most likely + Pessimistic) ÷ 6, which accounts for uncertainty in the estimate.
Analogous estimating: Using actual values from a similar past project as the basis — quick and cheap but less accurate (top-down).
Parametric estimating: Using a statistical relationship between historical data and variables (e.g., cost per unit) to calculate an estimate.
Bottom-up estimating: Estimating individual work packages and rolling them up — the most accurate but most time-consuming method.
Cost baseline: The approved, time-phased budget used to measure and monitor cost performance, excluding management reserves.
Contingency reserve: Budget set aside for identified ('known-unknown') risks; the project manager can use it.
Management reserve: Budget for unforeseen ('unknown-unknown') work; it requires management approval to use and is outside the cost baseline.
Earned value management (EVM): An integrated method combining scope, schedule, and cost to measure and forecast project performance objectively.
Planned value (PV): The authorized budget assigned to the work scheduled to be done by a given date.
Earned value (EV): The budgeted cost of the work actually completed by a given date.
Actual cost (AC): The real cost incurred for the work completed by a given date.
Cost variance (CV): CV = EV − AC; a negative value means the project is over budget.
Schedule variance (SV): SV = EV − PV; a negative value means the project is behind schedule.
Cost performance index (CPI): CPI = EV ÷ AC; greater than 1 is under budget, less than 1 is over budget.
Schedule performance index (SPI): SPI = EV ÷ PV; greater than 1 is ahead of schedule, less than 1 is behind.
Budget at completion (BAC): The total authorized budget for the project's planned work.
Estimate at completion (EAC): The forecast total cost; when current performance continues, EAC = BAC ÷ CPI.
Quality assurance: Process-focused activities that build confidence the project will meet quality requirements (managing quality).
Quality control: Product-focused activities that verify deliverables meet requirements (controlling quality).
Prevention vs. inspection: Prevention keeps errors out of the process (cheaper); inspection keeps errors out of the customer's hands.
Cost of quality (COQ): The total cost of conformance (prevention, appraisal) plus non-conformance (internal and external failure).
Risk register: The artifact recording identified risks with their probability, impact, owner, and planned responses.
Qualitative risk analysis: Prioritizing risks by assessing probability and impact, usually with a probability-and-impact matrix.
Quantitative risk analysis: Numerically modeling the combined effect of prioritized risks on cost and schedule objectives.
Threat response strategies: Avoid, transfer, mitigate, accept, and escalate — for negative risks (threats).
Opportunity response strategies: Exploit, share, enhance, accept, and escalate — for positive risks (opportunities).
Mitigate (risk): Reduce the probability or impact of a threat to an acceptable level.
Transfer (risk): Shift the impact of a threat to a third party (e.g., insurance, warranties, contracts).
Procurement: Obtaining goods or services from outside the project team, governed by contracts.
Fixed-price contract: A contract with a set price; the seller carries most of the cost risk.
Cost-reimbursable contract: A contract paying the seller's allowable costs plus a fee; the buyer carries more cost risk.
Time and materials (T&M) contract: A hybrid paying hourly/unit rates with no fixed total; cost risk is shared.
Statement of work (SOW): A narrative description of the products, services, or results to be supplied under a contract.
Change control board (CCB): A formally chartered group that reviews, approves, or rejects requested changes to the project.
Integrated change control: The process of reviewing all change requests and managing changes to deliverables and baselines.
Verify scope vs. control quality: Validate Scope is formal acceptance of deliverables by the customer; Control Quality checks correctness against requirements first.
Resource leveling: Adjusting start/finish dates based on resource constraints to balance demand with available supply; it may extend the schedule.
Schedule baseline: The approved version of the schedule model used to measure schedule performance.
Decomposition: Dividing project scope and deliverables into smaller, more manageable parts (used to build the WBS).
Rolling wave planning: Planning near-term work in detail and future work at a higher level, elaborating it as the project progresses.
Agile: An iterative, incremental approach that fixes time and cost and flexes scope by priority, delivering value in short cycles.
Agile Manifesto: Four values: individuals & interactions over processes & tools; working software over documentation; customer collaboration over contract negotiation; responding to change over following a plan.
When to use agile: When requirements are uncertain or evolving, early and frequent feedback is valuable, and the team can deliver in increments.
Scrum: An agile framework delivering work in fixed timeboxes (sprints) with set roles and ceremonies.
Sprint: A short, fixed-length iteration (often 1–4 weeks) in which a Scrum team produces a usable increment.
Product owner: The Scrum role accountable for maximizing value and managing (ordering) the product backlog.
Scrum master: The servant-leader who coaches the team, facilitates events, and removes impediments — does not assign work.
Development team (developers): The cross-functional Scrum members who do the work to deliver a usable increment each sprint; they self-organize.
Product backlog: An ordered, evolving list of everything that might be needed in the product, owned by the product owner.
Sprint backlog: The set of product-backlog items selected for a sprint plus the plan to deliver them; owned by the developers.
Sprint planning: The event that starts a sprint: the team selects backlog items it can complete and sets a sprint goal.
Daily standup (daily scrum): A short (≤15 min) daily sync where developers inspect progress toward the sprint goal and adapt the plan.
Sprint review: The event at the end of a sprint to demo the increment to stakeholders and gather feedback.
Sprint retrospective: The event where the team inspects how it worked and commits to improvements for the next sprint.
Increment: A usable, potentially shippable piece of the product produced each sprint that meets the definition of done.
Definition of done (DoD): The shared, agreed checklist a backlog item must meet to be considered complete.
User story: A short requirement from the user's perspective: 'As a [role], I want [goal] so that [benefit].'
Acceptance criteria: The conditions a user story must satisfy to be accepted by the product owner.
Epic: A large body of work that can be broken down into multiple user stories.
Velocity: The amount of work (e.g., story points) an agile team completes per iteration, used to forecast capacity.
Story points: A relative unit estimating the effort/complexity of a backlog item, not hours.
Planning poker: A consensus estimating technique where the team reveals story-point estimates simultaneously and discusses differences.
Burndown chart: A chart showing remaining work over time in a sprint or release; the line trends down toward zero.
Burnup chart: A chart showing completed work rising toward the total scope line over time.
Kanban: An agile method based on visualizing work and limiting work in progress (WIP) to improve continuous flow.
Work in progress (WIP) limit: A cap on how many items can be in a workflow stage at once, used in Kanban to improve flow and expose bottlenecks.
Kanban board: A visual board with columns (e.g., To Do, Doing, Done) showing work items as they move through the workflow.
Scrum vs. Kanban: Scrum uses fixed sprints, set roles, and a sprint commitment; Kanban uses continuous flow with WIP limits and no required roles or sprints.
Minimum viable product (MVP): The smallest releasable version of a product that delivers value and enables learning.
Timeboxing: Allocating a fixed maximum amount of time to an activity (e.g., a sprint or a meeting).
Hybrid approach: A delivery approach blending predictive and agile elements, tailored to the project and organization.
Servant leadership in agile: Leaders serve the team — removing impediments, coaching, and protecting focus — so a self-organizing team can perform.
Self-organizing team: A team that decides internally how to accomplish its work rather than being directed by a manager.
Information radiator: A highly visible display (e.g., a task board or burndown chart) that broadcasts progress to anyone passing by.
Refinement (grooming): The ongoing activity of adding detail, estimates, and order to product-backlog items.
Spike: A short, time-boxed research task used to reduce uncertainty about a story or technical approach.
Cadence: A rhythm of activities conducted throughout a project (e.g., the regular sprint length).
Retrospective purpose: Continuous improvement — the team reflects on its process and chooses concrete changes to try next.
Backlog prioritization: Ordering the product backlog by value, risk, and dependencies so the most valuable work is done first.
Empirical process control: Scrum's foundation: decisions are based on observation and experiment via transparency, inspection, and adaptation.
Business analysis: The set of activities to identify business needs and recommend solutions that deliver value to stakeholders.
Business analyst (BA) vs. project manager: The BA defines and manages requirements and the solution scope; the PM manages the project scope, schedule, and delivery.
Requirement: A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Business requirements: High-level needs of the organization — the why behind the project (goals, objectives, value).
Stakeholder requirements: The needs of a stakeholder or stakeholder group that must be met to achieve the business requirements.
Solution requirements: The features and qualities of a solution; split into functional and non-functional requirements.
Functional vs. non-functional requirements: Functional describes what the solution must do; non-functional describes how well it must do it (performance, security, usability).
Transition requirements: Temporary capabilities needed to move from the current state to the future state (e.g., data conversion, training).
Elicitation: Drawing out information from stakeholders and sources to discover requirements (interviews, workshops, observation, surveys).
Elicitation techniques: Interviews, focus groups, facilitated workshops, surveys/questionnaires, observation, prototyping, document analysis, and brainstorming.
Facilitated workshop: A structured session bringing key stakeholders together to define, refine, and reconcile requirements quickly.
Prototyping: Building an early working model of the solution to elicit and validate requirements through feedback.
Requirements traceability matrix (RTM): A grid linking each requirement to its origin and to deliverables, tests, and objectives, ensuring nothing is lost.
Why use a traceability matrix?: To track requirements through the life cycle, confirm each delivers value, and manage scope and change.
Requirements management plan: Describes how requirements will be analyzed, documented, prioritized, traced, and managed throughout the project.
Backlog (in business analysis): A prioritized list of requirements or work items, refined and reprioritized as understanding grows.
Acceptance criteria (BA): The conditions that must be met for a stakeholder to accept a requirement or solution as complete and correct.
Validation vs. verification (requirements): Validation confirms requirements deliver business value (right thing); verification confirms they are well-formed and meet quality (built right).
Solution evaluation: Assessing how well a delivered solution meets the business need and identifying improvement opportunities.
Current state vs. future state: Current state is how things work today; future state is the desired condition the solution should achieve.
Gap analysis: Comparing the current state to the desired future state to identify what must change to close the difference.
Root cause analysis: Identifying the underlying cause of a problem (e.g., the 5 Whys or a fishbone diagram) rather than treating symptoms.
Fishbone (Ishikawa) diagram: A cause-and-effect diagram that groups potential causes of a problem into categories to find root causes.
SWOT analysis: Evaluating Strengths, Weaknesses, Opportunities, and Threats to inform decisions and solution options.
MoSCoW prioritization: Classifying requirements as Must have, Should have, Could have, and Won't have (this time) to manage scope.
Stakeholder analysis (BA): Identifying stakeholders and assessing their influence, attitudes, and requirements to plan engagement.
Use case: A description of how an actor interacts with a system to achieve a goal, including the main and alternate flows.
Process model / flowchart: A visual representation of a business process showing the sequence of activities, decisions, and flows.
Context diagram: A high-level model showing the system, its boundaries, and how it interacts with external entities.
Decision tree / decision table: Tools that map combinations of conditions to outcomes, clarifying complex business rules.
Business rule: A specific, testable directive that defines or constrains some aspect of the business (e.g., approval thresholds).
Backlog refinement role of the BA: Helping clarify, detail, and prioritize requirements so the team always works on the most valuable, well-understood items.
Requirements baseline: An agreed, approved set of requirements that changes only through a controlled change process.
Change in requirements: Managed through impact assessment and approval; uncontrolled requirement changes drive scope creep.
Non-functional requirement examples: Performance, scalability, security, reliability, usability, availability, and compliance.
Business need: The problem or opportunity, defined by its impact, that justifies starting a project or initiative.
Solution scope: The boundaries of the solution that will satisfy the business need and stakeholder requirements.
Brainstorming: A group technique to generate many ideas or potential requirements quickly without early judgment.
Document analysis: Reviewing existing materials (procedures, contracts, regulations) to discover relevant requirements.
Observation (job shadowing): Watching how work is actually performed to elicit requirements that stakeholders may not articulate.
Survey/questionnaire: A set of written questions to gather information from many stakeholders efficiently, often when they are dispersed.
Interview (elicitation): A direct conversation with one or a few stakeholders to draw out detailed requirements and expectations.
Why business analysis is on the CAPM: Roughly a quarter of the exam covers BA frameworks because requirements drive the value a project delivers.
Requirements prioritization: Ranking requirements by value, cost, risk, and dependencies to decide order and what is in or out of scope.
Confirming elicitation results: Reviewing elicited information with stakeholders to ensure it is accurate, complete, and consistent before use.
Project scope vs. solution (product) scope: Product/solution scope is the features of the product; project scope is the work needed to deliver it.
Closing a project: Finalizing all activities, obtaining formal acceptance, releasing resources, and recording lessons learned.
Formal acceptance: The customer's or sponsor's sign-off that deliverables meet acceptance criteria — required to close a phase or project.
Project initiation: Authorizing the project: developing the charter and identifying stakeholders.
Project planning: Defining scope, refining objectives, and creating the plan and baselines to achieve them.
Project executing: Doing the work defined in the plan to deliver the project's objectives and manage the team.
Monitoring & controlling: Tracking, reviewing, and regulating progress and performance, and managing changes against the baselines.
Kickoff meeting: A meeting to announce the start of a project (or phase), align the team and stakeholders, and review objectives and roles.
Team charter: A document defining team values, agreements, ground rules, and operating guidelines.
Communications management plan: Defines what information is communicated, to whom, when, how, and by whom on the project.
Push vs. pull vs. interactive communication: Push sends to recipients (email); pull lets recipients access at will (portals); interactive is real-time exchange (meetings).
Net present value (NPV): Future cash flows discounted to today minus the investment; a positive NPV adds value and a higher NPV is preferred.
Return on investment (ROI): The percentage gain from a project relative to its cost; higher is better.
Payback period: The time it takes for a project's cumulative cash inflows to recover its initial investment; shorter is better.
Cost-benefit analysis: Comparing the expected costs of a project to its expected benefits to support a go/no-go decision.
Feasibility study: An assessment of whether a proposed solution is technically, operationally, and economically practical.
Definition of ready (DoR): The agreed checklist a backlog item must meet before the team will pull it into a sprint.
Product roadmap: A high-level visual of the product's direction and planned releases over time.
Release planning: Mapping which features/increments will be delivered in which release to meet a goal or date.
Pair work / mob work: Two or more team members working together on the same item to improve quality and share knowledge.
Retrospective output: A small set of concrete, actionable improvements the team commits to for the next iteration.
Why iterate?: Frequent increments produce early feedback, reduce risk, and let priorities adapt as understanding grows.
Adaptive vs. predictive life cycle: Adaptive (agile) flexes scope through iterations; predictive fixes scope up front and proceeds sequentially.
Iterative vs. incremental: Iterative refines the same work through repeated cycles; incremental builds the product in successive usable pieces.
Customer collaboration (agile value): Engaging the customer continuously throughout development rather than only at contract or hand-off.
Working product over documentation: Agile favors delivering usable product as the primary measure of progress over exhaustive documentation.
Project benefits vs. deliverables: Deliverables are what the project produces; benefits are the value the organization realizes from using them.
Benefits realization: Confirming the project's intended benefits and value are actually achieved, often after the project closes.
On time and on budget ≠ success: A project can finish on schedule and budget yet fail if the intended value or benefits never materialize.
Configuration management: Controlling product characteristics and versions so the team knows the current approved state of deliverables.
Variance analysis: Comparing planned to actual performance to determine the cause and degree of difference and decide on corrective action.
Corrective vs. preventive action: Corrective action realigns performance with the plan; preventive action reduces the probability of future negative outcomes.
Defect repair: An action to fix a nonconforming product component identified during quality control.
Histogram: A bar chart showing the frequency distribution of data — a quality tool for spotting patterns.
Pareto chart: A histogram ordered by frequency illustrating the 80/20 rule — focusing on the vital few causes.
Control chart: A chart showing process performance over time against upper and lower control limits to detect whether it is stable.
Rule of seven (control charts): Seven consecutive points on one side of the mean signal a non-random trend that should be investigated.
Scatter diagram: A quality tool plotting two variables to reveal the relationship or correlation between them.
Check sheet: A structured form for collecting and tallying data in real time, often to count defects by category.
Quality metrics: The specific measures and how they are checked to determine whether the project meets quality requirements.
Risk appetite: The degree of uncertainty an organization or stakeholder is willing to accept in pursuit of reward.
Risk threshold: The level of risk exposure above which action is required and below which it may be accepted.
Probability and impact matrix: A grid rating each risk by likelihood and consequence to prioritize which risks need attention.
Secondary risk: A new risk that arises as a direct result of implementing a risk response.
Residual risk: The risk that remains after a planned response has been implemented.
Risk owner: The person responsible for monitoring a risk and carrying out the agreed response.
Make-or-buy analysis: Deciding whether to perform work internally or procure it externally based on cost, capability, and risk.
Bid documents (RFP, RFQ, IFB): Requests sent to sellers: RFP (proposal), RFQ (quote), and IFB (sealed bid) to solicit competitive responses.
Source selection criteria: The standards used to evaluate and choose among seller proposals (price, technical capability, past performance).
Contract closure: Verifying all work and deliverables are complete and acceptable and formally closing the procurement.
Project schedule network analysis: Techniques (e.g., critical path method) used to calculate early/late dates and identify schedule flexibility.
Forward pass: Calculating early start and early finish dates by working forward through the schedule network.
Backward pass: Calculating late start and late finish dates by working backward from the project end date.
Mandatory vs. discretionary dependency: Mandatory (hard logic) is required by the nature of the work; discretionary (soft logic) is a preferred best practice.
External dependency: A relationship between project and non-project activities, often outside the team's control (e.g., a vendor delivery).
Project calendar vs. resource calendar: The project calendar shows working days for project work; resource calendars show when each resource is available.
Cost aggregation: Summing the estimated costs of work packages up the WBS to establish the cost baseline.
Funding limit reconciliation: Comparing planned spending to any funding limits and adjusting the schedule of work to stay within them.
Estimate to complete (ETC): The expected cost to finish the remaining project work; ETC = EAC − AC.
Variance at completion (VAC): The forecast budget surplus or deficit; VAC = BAC − EAC. A negative VAC forecasts an overrun.
To-complete performance index (TCPI): The cost efficiency required on remaining work to meet a goal (e.g., (BAC − EV) ÷ (BAC − AC)).
Agile coach: Someone who guides individuals and teams in adopting agile practices and improving their ways of working.
Servant-leader behaviors: Removing impediments, shielding the team from distractions, facilitating, and developing people.
Osmotic communication: Information flowing in the background among co-located team members, who absorb relevant details by being near each other.
Daily scrum purpose: Inspect progress toward the sprint goal and adapt the plan — it is for the developers, not a status report to managers.
Who orders the product backlog?: The product owner, based on value, risk, and stakeholder priorities.
Sprint goal: The single objective for a sprint that gives the increment coherence and guides the team's decisions.
Scrum values: Commitment, courage, focus, openness, and respect.
Agile principles (overview): Twelve principles behind the Manifesto, including early/continuous delivery, welcoming change, and sustainable pace.
Sustainable pace: Working at a steady, indefinitely maintainable rate to keep quality high and avoid burnout.
Backlog item lifecycle: From idea to refined and estimated, to selected for a sprint, to done — value-ordered throughout.
Feature: A piece of functionality that delivers value to a stakeholder; larger than a story, smaller than an epic.
Retrospective vs. review: The review inspects the product (with stakeholders); the retrospective inspects the team's process.
Cumulative flow diagram: A chart showing the amount of work in each workflow state over time, used to spot bottlenecks in Kanban.
Lead time vs. cycle time: Lead time is from request to delivery; cycle time is from when work starts to when it's done.
Solution life cycle: The stages a solution passes through from concept and development to operation and eventual retirement.
Business analysis planning: Determining how business-analysis work will be performed: approach, stakeholders, governance, and information management.
Stakeholder engagement (BA): Building and maintaining working relationships with stakeholders to keep requirements accurate and supported.
Requirements life cycle management: Managing and maintaining requirements from inception through retirement, including tracing, prioritizing, and approving them.
Allocate requirements: Assigning requirements to solution components and releases to deliver the most value within constraints.
Approve requirements: Obtaining agreement on and sign-off of requirements from the responsible stakeholders before development.
Maintain requirements: Keeping requirements accurate and current and reusing them where possible across initiatives.
Solution performance measures: The metrics used to evaluate whether a delivered solution is meeting the business need and delivering value.
Risk analysis (BA): Identifying and assessing risks related to requirements and the solution so they can be managed.
Backlog management (BA): Continuously detailing, estimating, and prioritizing requirements so the team works on the highest-value items.
Affinity diagram: Grouping ideas or requirements into related clusters to organize and analyze them.
Interviews vs. surveys (when to use): Interviews suit deep, detailed input from a few; surveys suit broad input from many, dispersed stakeholders.
Mind mapping: A visual technique that branches ideas from a central concept to explore and organize requirements.
Benchmarking: Comparing practices, processes, or metrics against peers or standards to identify improvement opportunities.
Conflicting requirements: Reconciled through negotiation, prioritization, and stakeholder collaboration to reach an agreed, consistent set.
Requirements attributes: Metadata about each requirement (source, priority, owner, status, version) that supports tracing and management.

To find us again, just search “Career Employer CAPM”

By Career EmployerUpdated Jun 19, 2026

250+ free CAPM flashcards — 4 ways to study

CAPM Flashcard of the Day

The classic card. Do you know this one?

Click Study Flashcards above to open the flashcard hub — hundreds of CAPM cards you can flip, match, type, or quiz yourself on. Every card is drawn from PMI’s four official domains, so you study exactly what the exam tests.^[1] Pair them with our free practice test and study guide.

CAPM Flashcard Study Modes

Most flashcard sites give you one thing: a card to flip. Ours has four modes so you can both learn the material and prove you know it — the difference between recognizing an answer and recalling it under exam pressure.

Flip (Study) — the classic card. Flip term ↔ definition, shuffle the deck, and mark each card “Got it” or “Still learning.”
Match (Game) — a timed game: pair each term to its definition as fast as you can. Great for cementing EVM, agile, and requirements vocabulary.
Type (Recall) — read the definition and type the term. Typing forces true active recall instead of passive recognition.
Quiz (Test) — multiple-choice questions generated from the cards, so you self-test exactly like exam day.

Free CAPM flashcards from Career Employer — active recall for the Certified Associate in Project Management exam

Why Flashcards Work for the CAPM

Flashcards aren’t busywork — they’re built on active recall: pulling an answer out of memory strengthens it far more than re-reading notes. Pair that with spacing — short sessions across several days rather than one cram — and you retain more in less time.

The CAPM is dense with terminology — earned-value formulas, agile roles and ceremonies, requirement types, estimating techniques, and project concepts.^[2] Spaced flashcards are the most efficient way to keep it all fresh. Used alongside our practice test and study guide, they turn review time into measurable progress.

CAPM Flashcards by Domain

The cards are organized by PMI’s four official domains, plus a Foundations & Mindset deck. Drill the highest-weighted domains first — Fundamentals and Business Analysis make up 63% of the exam:^[1]

CAPM flashcards by domain and exam weight (current 2023 exam)
Domain / deck	Exam weight
Project Management Fundamentals	36%
Business Analysis Frameworks	27%
Agile Frameworks / Methodologies	20%
Predictive, Plan-Based Methodologies	17%
Foundations & Mindset	Cross-cutting (exam facts & core concepts)

How to Get the Most Out of These Flashcards

Lead with the heavy domains. Fundamentals (36%) and Business Analysis (27%) are 63% of the exam — start there.
Burn in the formulas. Drill the EVM cards (CPI, SPI, CV, SV) until you can compute and interpret them instantly.
Use Type and Quiz, not just Flip. Recognizing the right answer is easy; recalling and choosing it is the real test.
Drill your weakest domain. Pick a single domain deck and grind it until the Match time drops and the Quiz score climbs.
Then prove it. When the cards feel easy, confirm with a full practice test — aim comfortably above passing before exam day.

CAPM Flashcards FAQ

Hundreds of free CAPM flashcards, organized across all four PMI domains — fundamentals, predictive, agile, and business analysis — plus a Foundations & Mindset deck. They're free with no account required.

References

1.Project Management Institute. “CAPM Examination Content Outline (2023 ECO).” pmi.org. ↑
2.Project Management Institute. “A Guide to the Project Management Body of Knowledge (PMBOK Guide), 7th ed..” pmi.org. ↑
3.Project Management Institute. “Agile Practice Guide.” pmi.org. ↑

Career Employer

Career Employer is the ultimate resource to help you get started working the job of your dreams. We cover topics from general career information, career searching, exam preparation with free study materials, career interviewing, and becoming successful in your career of choice.

All Posts

Career Employer’s Editorial Process

Here at Career Employer, we focus a lot on providing factually accurate information that is always up to date. We strive to provide correct information using strict editorial processes, article editing, and fact-checking for all of the information found on our website. We only utilize trustworthy and relevant resources. To find out more, make sure to read our full editorial process page here.