CAPM — PMI Certified Associate in Project Management Exam Blueprint

Last revised: June 29, 2026

Practical exam blueprint for PMI CAPM exam readiness, including project management foundations, predictive, agile, hybrid, business analysis, artifacts, and scenario judgment.

How to Use This CAPM Exam Blueprint

Use this checklist as a practical study map for the PMI Certified Associate in Project Management (CAPM) exam, code CAPM, from PMI. It is not an official scoring outline and does not claim exact weights. It translates the public CAPM exam identity into readiness tasks: what you should know, what you should be able to apply, and where candidates commonly lose points.

For each topic area, mark yourself ready only when you can:

Explain the concept in PMI-style project management language.
Recognize the concept inside a short scenario.
Choose the best next action, artifact, role, or technique.
Distinguish similar terms, such as risk vs. issue, quality assurance vs. quality control, or product backlog vs. work breakdown structure.
Apply basic calculations without relying on memorized wording alone.

A useful review pattern:

Scan the topic tables and mark weak areas.
Practice scenario decisions for each weak area.
Review artifacts and formulas until you can identify when and why they are used.
Finish with mixed practice so you can switch between predictive, agile, hybrid, and business analysis contexts.

CAPM Readiness Areas at a Glance

Readiness area	What to review	You are ready when you can…	Common weak signal
Project management foundations	Project vs. operations, programs, portfolios, PMO, governance, value, constraints, life cycles	Explain how projects create value and how the project manager supports outcomes	You memorize terms but cannot identify them in a scenario
Roles and responsibilities	Sponsor, project manager, team, customer, product owner, Scrum Master, stakeholders, business analyst	Identify who should act, approve, facilitate, escalate, or provide requirements	You assign all decisions to the project manager
Delivery approaches	Predictive, adaptive, agile, iterative, incremental, hybrid	Choose an approach based on requirement stability, uncertainty, stakeholder involvement, and change frequency	You assume agile is always better or predictive is always more controlled
Predictive planning	Charter, scope, WBS, schedule, budget, quality, resources, communications, risk, procurement, stakeholder planning	Connect planning artifacts to execution and control decisions	You know artifact names but not their purpose
Agile and adaptive work	Agile values, Scrum, Kanban, backlog, sprint, iteration, WIP, Definition of Done, servant leadership	Interpret agile scenarios and choose collaboration, transparency, and value-focused actions	You treat agile as “no planning” or “no documentation”
Hybrid delivery	Combining predictive governance with adaptive execution	Decide which parts should be fixed, flexible, staged, or iterated	You miss tailoring clues in the question
Business analysis	Needs assessment, requirements elicitation, analysis, traceability, acceptance criteria, solution evaluation	Link business need, requirements, solution features, and benefits	You confuse project outputs with business outcomes
Scope and requirements	Product scope, project scope, WBS, backlog, requirements documentation, acceptance	Prevent scope confusion and select the correct scope artifact	You mix up WBS work packages and agile backlog items
Schedule	Activities, dependencies, critical path, float, milestones, estimation, compression	Read a small network scenario and identify schedule impact	You confuse fast tracking with crashing
Cost and earned value	Budget, cost baseline, actual cost, earned value, CPI, SPI, variances	Interpret whether a project is over budget, under budget, ahead, or behind	You memorize formulas but misread what the result means
Quality	Quality planning, assurance, control, prevention, inspection, defects, continuous improvement	Choose whether to prevent, inspect, correct, or improve	You confuse quality assurance and quality control
Resources and teams	Resource planning, team development, conflict, motivation, leadership, virtual teams	Select collaboration and conflict responses that fit the situation	You escalate before attempting team-level resolution
Communications and stakeholders	Stakeholder identification, engagement, communication methods, feedback, reporting	Match information needs to stakeholders and communication channels	You treat communication as only status reporting
Risk and issues	Risk identification, qualitative analysis, responses, reserves, triggers, issue log	Distinguish uncertainty from realized problems and pick the next action	You update the wrong artifact after a risk occurs
Change control	Change request, impact analysis, baseline, approval, configuration control	Follow the change process instead of informally accepting changes	You implement changes just because a stakeholder asks
Procurement	Make-or-buy, contract types, seller selection, procurement documents, claims	Recognize buyer/seller responsibilities and contract risk	You ignore the contract or procurement plan in scenarios
Ethics and professionalism	Responsibility, respect, fairness, honesty, transparency, conflict of interest	Choose professional conduct even when under schedule or stakeholder pressure	You pick the fastest action rather than the ethical action

Project Management Foundation Checklist

Core Concepts to Know

Difference between a project, operation, program, and portfolio.
Why projects are temporary but can create long-term value.
How project objectives connect to business needs, benefits, products, services, or results.
The relationship among scope, schedule, cost, quality, risk, resources, and stakeholder satisfaction.
How governance, organizational strategy, and organizational process assets influence project work.
The purpose of a PMO and how it may support, control, or direct projects.
The difference between project success, product success, and business success.
Why tailoring matters across predictive, agile, and hybrid approaches.

Project Context Table

Concept	Exam-ready understanding	Scenario cue
Project	Temporary effort to create a unique product, service, or result	“New system implementation,” “facility move,” “product launch”
Operations	Ongoing, repetitive work that sustains the business	“Daily processing,” “routine support,” “continuous production”
Program	Related projects managed together for benefits not available separately	“Coordinated initiatives with shared benefits”
Portfolio	Projects, programs, and operations grouped to meet strategic objectives	“Prioritization of investments across the organization”
PMO	Organizational structure that standardizes or supports project management	“Templates, governance, coaching, methodology, oversight”
Business value	Benefits or outcomes created by the project or product	“Revenue, cost reduction, compliance, customer satisfaction”
Constraint	A limiting factor such as budget, deadline, resources, quality, or scope	“Must launch by date,” “fixed budget,” “limited staff”
Assumption	Something considered true for planning purposes	“Assume vendor will deliver by May”
Dependency	Relationship between activities, teams, suppliers, or external events	“Cannot test until build is complete”

Roles, Responsibilities, and Authority

The CAPM exam often tests whether you know who should do what. Do not assume the project manager owns every decision. Look for authority, accountability, and collaboration clues.

Role	Typical responsibility	Readiness prompt
Project sponsor	Provides authority, funding support, high-level direction, and escalation support	Can you identify when sponsor involvement is needed?
Project manager	Leads planning, coordination, execution, monitoring, communication, and integration	Can you choose facilitation before escalation when appropriate?
Project team	Performs project work, contributes estimates, identifies risks, solves problems	Can you recognize when the team should estimate or self-organize?
Customer/user	Receives or uses the deliverable; validates whether needs are met	Can you distinguish customer acceptance from internal completion?
Stakeholder	Person or group affected by or able to affect the project	Can you assess interest, influence, engagement, and communication needs?
Product owner	Prioritizes product backlog and represents product value in agile settings	Can you avoid assigning backlog priority to the project manager?
Scrum Master	Facilitates Scrum process and removes impediments	Can you distinguish facilitation from command-and-control management?
Business analyst	Helps identify needs, elicit requirements, analyze solutions, and support traceability	Can you connect requirements to business value?
Functional manager	Provides staff, expertise, or departmental authority in many organizations	Can you identify resource negotiation scenarios?
Vendor/seller	Provides contracted products, services, or results	Can you use contract terms and procurement documents in decisions?

Delivery Approach and Tailoring Checklist

Predictive, Agile, and Hybrid Readiness

Delivery approach	Best fit clues	Planning style	Change handling	Watch for
Predictive	Requirements are relatively stable; high need for upfront scope, cost, or schedule control	Detailed early planning with baselines	Formal change control	Do not ignore stakeholder feedback just because a plan exists
Agile/adaptive	Requirements are uncertain or evolving; frequent customer feedback is valuable	Progressive planning through backlog refinement and iterations	Change is expected and prioritized	Do not assume agile means no discipline
Iterative	Solution improves through repeated cycles and feedback	Plan enough to learn and refine	Feedback shapes future cycles	Distinguish iteration from simply repeating failed work
Incremental	Deliver usable pieces over time	Plan releases or increments	Scope can be sequenced by value	Distinguish increment from prototype
Hybrid	Some parts need predictability; others need adaptation	Mix of upfront planning and adaptive delivery	Change process depends on component	Tailoring is the key decision

Delivery Decision Prompts

Ask yourself:

Are requirements stable enough for detailed upfront planning?
Is early and frequent stakeholder feedback necessary?
Is the environment regulated, contract-driven, or safety-critical?
Is the product complex, innovative, or uncertain?
Can value be delivered in increments?
Are teams empowered to self-organize?
Is the organization using predictive governance with agile teams?
What artifact would be updated next: project management plan, backlog, roadmap, change log, risk register, or stakeholder register?

Scenario Cues

If the scenario says…	Likely exam focus	Better answer tendency
“Requirements are well understood and must be approved before construction”	Predictive planning and baselines	Define scope, build WBS, plan schedule/cost, control changes
“The customer wants frequent demonstrations and changing priorities”	Agile/adaptive delivery	Use backlog prioritization, reviews, feedback, and iterations
“The project has a fixed compliance deadline but uncertain solution details”	Hybrid tailoring	Keep governance and milestones visible while iterating the solution
“A stakeholder asks for a new feature after baseline approval”	Change control	Analyze impact and follow the change process
“The product owner changes item priority before the next sprint”	Agile backlog management	Reprioritize backlog before commitment to iteration work
“The team discovers a new technical risk”	Risk management	Document, analyze, plan response, and monitor triggers

Predictive Project Management Exam Blueprint

Integration and Governance

Topic	What to know	Ready check
Project charter	Authorizes the project and gives the project manager authority	Can you identify when work should not start without authorization?
Business case	Explains business need and justification	Can you connect project purpose to expected benefits?
Benefits management	Describes how and when benefits are expected	Can you distinguish deliverables from benefits?
Project management plan	Integrated plan for how the project will be managed	Can you identify when a subsidiary plan or baseline should be updated?
Baselines	Approved versions of scope, schedule, or cost used for comparison	Can you tell when a change request is needed?
Work performance data/information/reports	Raw observations become analyzed information and then reports	Can you place the right item in the right stage?
Change control	Evaluates and approves/rejects changes	Can you avoid implementing unapproved changes?
Lessons learned	Captures knowledge during and at the end of work	Can you update lessons learned throughout the project, not only at closure?

Scope and Requirements

Topic	Exam-ready distinction	Common trap
Product scope	Features and functions of the product/service/result	Confusing product scope with project work
Project scope	Work required to deliver the product/service/result	Treating all stakeholder requests as approved scope
Requirements documentation	Stakeholder needs and conditions to be satisfied	Skipping validation with stakeholders
Requirements traceability matrix	Links requirements to origin, deliverables, tests, and objectives	Losing sight of why a requirement exists
Scope statement	Describes project scope, deliverables, exclusions, and acceptance criteria	Forgetting exclusions and assumptions
WBS	Hierarchical decomposition of project scope into deliverables/work packages	Turning the WBS into a chronological schedule
Scope baseline	Approved scope statement, WBS, and WBS dictionary	Updating it without approved change control
Validate scope	Formal acceptance of completed deliverables	Confusing acceptance with quality inspection
Control scope	Monitoring scope and managing changes	Allowing scope creep

Schedule Management

Define activities from work packages.
Sequence activities using logical dependencies.
Estimate durations with input from knowledgeable people.
Identify milestones and constraints.
Determine critical path and float.
Develop the schedule using dependencies, resources, and constraints.
Control the schedule by comparing actual progress to the approved schedule baseline.
Know when to use crashing, fast tracking, re-estimation, or re-sequencing.

Schedule concept	Meaning	Scenario clue
Finish-to-start dependency	One activity must finish before another starts	“Testing starts after development is complete”
Lead	Allows a successor to start before predecessor fully finishes	“Begin documentation two days before build completion”
Lag	Waiting time between activities	“Wait three days after pouring concrete”
Critical path	Longest path through the network; shortest project duration	“Any delay delays the project”
Total float	Time an activity can slip without delaying project finish	“Can be delayed without affecting end date”
Crashing	Add resources to shorten duration, usually increasing cost	“Budget available to recover schedule”
Fast tracking	Perform activities in parallel that were planned in sequence	“Increases risk due to overlap”
Milestone	Significant point or event, often zero duration	“Approval received,” “phase complete”

Cost and Earned Value

Be ready to interpret both the calculation and the management meaning.

\[ SV = EV - PV \]\[ CV = EV - AC \]\[ SPI = \frac{EV}{PV} \]\[ CPI = \frac{EV}{AC} \]

Metric	Plain meaning	If result is unfavorable
Planned Value	Budgeted value of work planned by a point in time	The plan may be ahead of actual progress
Earned Value	Budgeted value of work actually completed	Low EV can indicate less work completed than expected
Actual Cost	Actual cost incurred for completed work	High AC can hurt cost performance
Schedule Variance	EV minus PV	Negative means behind planned value
Cost Variance	EV minus AC	Negative means over cost for earned work
Schedule Performance Index	EV divided by PV	Less than 1 indicates schedule efficiency concern
Cost Performance Index	EV divided by AC	Less than 1 indicates cost efficiency concern

Also review:

Difference between budget, cost estimate, cost baseline, and management reserve.
Order-of-magnitude vs. more detailed estimates.
Analogous, parametric, bottom-up, and three-point estimating.
Contingency reserve vs. management reserve.
Why poor scope definition can damage cost estimates.

Three-point expected estimate:

\[ TE = \frac{O + 4M + P}{6} \]

Where:

O = optimistic estimate
M = most likely estimate
P = pessimistic estimate

Quality Management

Quality topic	What to know	Ready check
Quality management plan	How quality will be planned, managed, and controlled	Can you identify prevention activities?
Quality assurance	Process-focused confidence that quality processes are appropriate	Can you separate process improvement from product inspection?
Quality control	Inspection/testing of deliverables against standards	Can you decide when a defect should be recorded and corrected?
Cost of quality	Prevention, appraisal, internal failure, external failure	Can you identify why prevention is usually preferred?
Continuous improvement	Ongoing improvement of processes and outcomes	Can you choose root cause analysis rather than blame?
Acceptance criteria	Conditions that must be met for acceptance	Can you connect acceptance to requirements and validation?

Common distinction:

Quality assurance asks: Are we following effective quality processes?
Quality control asks: Does the deliverable meet the required standard?

Agile and Adaptive Exam Blueprint

Agile Foundations

Understand agile as a value-driven, adaptive approach, not simply a set of meetings.
Know why transparency, inspection, adaptation, and collaboration matter.
Recognize iterative and incremental delivery.
Understand how agile handles changing priorities through backlog management.
Know why empowered teams and servant leadership are important.
Distinguish agile planning from lack of planning.
Connect frequent feedback to risk reduction and value delivery.

Scrum, Kanban, and Common Agile Concepts

Topic	What to know	Exam cue
Product backlog	Ordered list of product work, features, fixes, and improvements	“Product owner reprioritizes based on value”
Sprint/iteration backlog	Work selected for a timeboxed iteration	“Team commits or forecasts work for the iteration”
Increment	Usable product result completed during an iteration	“Potentially releasable product”
Definition of Done	Shared understanding of completion quality	“Work is not done until it meets agreed criteria”
Sprint planning	Team plans work for upcoming sprint	“Selects backlog items and plans how to deliver them”
Daily standup	Short coordination event for the team	“Inspect progress and surface impediments”
Sprint review	Demonstrate increment and gather feedback	“Stakeholders inspect product outcome”
Retrospective	Team improves process	“What should the team improve next sprint?”
Kanban board	Visualizes workflow	“Columns such as To Do, Doing, Done”
WIP limit	Limits work in progress to improve flow	“Too many items started, few completed”
Velocity	Amount of work completed in prior iterations	“Used for forecasting, not judging individual performance”
Burndown chart	Shows remaining work over time	“Work remaining trend”
Burnup chart	Shows completed work toward scope	“Progress against total scope”

Agile Scenario Judgment

Scenario	Better response
Stakeholders disagree on feature priority	Product owner works with stakeholders to order backlog by value, risk, and need
Team is blocked by an external dependency	Scrum Master or servant leader helps remove impediment; team makes blocker transparent
A sprint is underway and a stakeholder requests a new feature	Add to product backlog for prioritization unless it is an urgent exception handled by the team’s agreed process
Work repeatedly fails acceptance criteria	Review Definition of Done, quality practices, and acceptance criteria; improve process
Team velocity varies	Use historical data cautiously; inspect causes; avoid blaming individuals
Too many tasks are in progress	Apply WIP limits and focus on finishing work
Customer feedback changes direction	Reprioritize backlog and adapt future work
Team retrospective identifies recurring defects	Select improvement actions and make them visible in the next cycle

Business Analysis and Requirements Readiness

The CAPM exam identity includes project management foundations, but candidates should also be ready for business analysis concepts that connect needs, requirements, solutions, and value.

Business Analysis Checklist

Identify the business need or problem before jumping to a solution.
Distinguish stakeholder needs from documented requirements.
Understand elicitation techniques such as interviews, workshops, observation, surveys, document analysis, and prototypes.
Recognize functional and nonfunctional requirements.
Use acceptance criteria to define what “acceptable” means.
Trace requirements to business objectives, design, test cases, and deliverables.
Understand prioritization based on value, risk, urgency, dependency, and feasibility.
Recognize how backlog items, user stories, and product roadmaps support adaptive work.
Identify when requirements are ambiguous, conflicting, incomplete, or unverified.
Connect solution evaluation to whether the delivered result meets the business need.

Requirements and Value Table

Artifact or concept	Purpose	Readiness prompt
Needs assessment	Understand problem/opportunity	Can you avoid starting with a predetermined solution?
Business case	Justify investment	Can you connect project selection to value?
Requirements documentation	Record stakeholder and solution requirements	Can you spot missing or conflicting requirements?
Acceptance criteria	Define conditions for acceptance	Can you use them to validate completed work?
Traceability matrix	Link requirements through delivery and testing	Can you identify impact when a requirement changes?
User story	Express value from a user perspective	Can you explain who wants what and why?
Product roadmap	High-level product direction over time	Can you distinguish roadmap from detailed schedule?
Product backlog	Ordered work for the product	Can you identify who prioritizes it in agile settings?
MVP	Smallest useful product to validate value or learning	Can you distinguish MVP from unfinished low-quality work?
Benefits realization	Confirm expected value after delivery	Can you separate output delivery from outcome achievement?

Stakeholder, Communication, and Leadership Checklist

Stakeholder Readiness

Identify stakeholders early and update the list as the project changes.
Analyze interest, influence, power, expectations, and attitude.
Plan engagement based on stakeholder needs.
Communicate with the right level of detail for each audience.
Use feedback loops, not one-way reporting only.
Manage conflict professionally and constructively.
Escalate when authority, governance, ethics, or unresolved constraints require it.
Recognize cultural, geographic, and virtual-team communication challenges.

Communication Checks

Concept	What to know	Scenario clue
Communication management plan	Defines what, when, how, and to whom information is communicated	“Stakeholders complain they are not receiving the right updates”
Stakeholder engagement plan	Describes strategies for engaging stakeholders	“A resistant stakeholder has high influence”
Push communication	Sent to recipients, but receipt does not ensure understanding	Email, memo, report
Pull communication	Recipients access information when needed	Portal, repository, dashboard
Interactive communication	Real-time exchange	Meeting, call, workshop
Communication blocker	Anything that distorts understanding	Time zone, language, assumptions, noise
Feedback	Confirms message was received and understood	“Ask clarifying questions,” “confirm understanding”

Communication channels formula:

\[ \text{Channels} = \frac{n(n-1)}{2} \]

Where n is the number of people in the communication group.

Leadership and Team Scenarios

If the question describes…	Consider…
Team members disagree on technical approach	Facilitate discussion, use ground rules, seek data, resolve collaboratively
A conflict is escalating and affecting work	Address conflict directly; use appropriate conflict management approach
A team member lacks skill	Coach, train, pair, or adjust assignment depending on context
Virtual team misunderstandings	Improve communication norms, tools, working agreements, and clarity
Low trust or poor collaboration	Use servant leadership, transparency, team charter, and retrospectives
Stakeholder bypasses agreed process	Reconfirm governance and communication expectations
Ethical concern or conflict of interest	Act transparently and follow professional responsibility principles

Risk, Issue, and Change Decision Points

Risk Management Checklist

Identify threats and opportunities.
Record risks in a risk register or appropriate risk artifact.
Assess probability, impact, urgency, and proximity.
Select response strategies for threats and opportunities.
Assign risk owners.
Define triggers and contingency plans.
Monitor risks throughout the project.
Convert realized risks into issues when they occur.
Use reserves appropriately.

Risk response	Used for	Example cue
Avoid	Eliminate the threat	Change plan to remove risky activity
Mitigate	Reduce probability or impact	Add testing, training, backup supplier
Transfer	Shift ownership or financial impact	Insurance, warranty, contract
Accept	Acknowledge without proactive action beyond monitoring or reserve	Low-priority risk or no practical response
Escalate	Risk is outside project authority	Enterprise-level or sponsor-level decision
Exploit	Ensure opportunity occurs	Assign best resources to capture benefit
Enhance	Increase probability or impact of opportunity	Add support to improve chance of gain
Share	Partner to capture opportunity	Joint venture, shared incentive

Risk vs. Issue vs. Change

Situation	What it is	Likely artifact/action
“Vendor may be late”	Risk	Add or update risk register; plan response
“Vendor is late”	Issue	Update issue log; take corrective action
“Customer wants an additional feature”	Change request	Analyze impact; follow change control
“Approved scope baseline no longer matches requested work”	Scope change	Submit/evaluate change request
“Defect found during inspection”	Quality issue/defect	Record defect; correct or rework based on process
“A risk trigger has occurred”	Risk becoming active	Execute contingency plan or update issue log
“New regulation affects project objectives”	External change/risk	Analyze impact; escalate or request change as needed

Change Control Scenario Checks

When a change appears, ask:

Has the work been baselined or formally committed?
Who requested the change?
What is the impact on scope, schedule, cost, quality, risk, resources, procurement, and stakeholders?
Does the project management plan define a change process?
Who has approval authority?
Which artifacts must be updated after approval?

Avoid these weak answers:

Implementing the change immediately because the requester is important.
Rejecting the change without analysis.
Escalating every change to the sponsor without following the process.
Updating baselines before approval.
Ignoring impacts outside the obvious area.

Procurement and Contract Exam Blueprint

Topic	What to review	Ready check
Make-or-buy analysis	Whether work should be performed internally or acquired externally	Can you identify cost, risk, capability, and schedule factors?
Procurement management plan	How procurement will be conducted and controlled	Can you follow procurement governance in a scenario?
Procurement documents	RFPs, RFQs, IFBs, statements of work, selection criteria	Can you match document type to buying need?
Contract types	Fixed-price, cost-reimbursable, time-and-materials concepts	Can you identify who carries more cost risk?
Seller selection	Evaluation of proposals and vendor capability	Can you distinguish price from best overall fit?
Procurement control	Managing seller performance, changes, payments, and claims	Can you use the contract instead of informal promises?
Closure	Confirming work, resolving claims, and completing procurement records	Can you separate project closure from procurement closure?

Scenario cues:

If a seller is not meeting requirements, review the contract, procurement documents, and performance data.
If a buyer wants extra work from a seller, determine whether a contract change is needed.
If requirements are unclear, improve the statement of work or procurement documentation before expecting accurate proposals.
If risk allocation matters, compare contract type and incentives.

Artifact Readiness Checklist

Initiating and Planning Artifacts

Artifact	Purpose	Can you identify when to use it?
Business case	Justifies the project	When deciding why the project should exist
Benefits plan or benefits information	Describes expected value	When tracking outcome realization
Project charter	Formally authorizes the project	Before detailed planning and execution authority
Stakeholder register	Identifies stakeholders and key attributes	When new stakeholders appear or influence changes
Project management plan	Defines how the project is managed	When coordinating subsidiary plans
Scope baseline	Approved scope statement, WBS, WBS dictionary	When judging scope changes
Schedule baseline	Approved schedule model	When comparing actual schedule performance
Cost baseline	Approved time-phased budget	When measuring cost performance
Risk register	Risks, analysis, owners, responses	When uncertainty may affect objectives
Requirements documentation	Stakeholder and solution requirements	When defining what must be satisfied
Traceability matrix	Links requirements to objectives and deliverables	When assessing impact of requirement changes
Communications management plan	Communication needs and methods	When stakeholders lack useful information
Stakeholder engagement plan	Engagement strategies	When stakeholder support or resistance matters
Procurement management plan	How buying will be handled	When external sellers are involved
Quality management plan	Standards and quality approach	When preventing defects and planning inspections

Execution, Monitoring, and Closing Artifacts

Artifact	Purpose	Exam cue
Issue log	Tracks current problems	“The risk has occurred,” “problem needs resolution”
Change log	Tracks change requests and decisions	“Change submitted, approved, rejected, deferred”
Lessons learned register	Captures learning during the project	“Team discovered a better method”
Work performance data	Raw observations and measurements	“Actual hours, percent complete, defect counts”
Work performance information	Analyzed performance meaning	“Behind schedule due to supplier delay”
Work performance reports	Communicated performance summaries	“Status report to sponsor”
Quality reports	Quality findings and recommendations	“Defect trends, process issues”
Test results/inspection results	Evidence of deliverable quality	“Deliverable passed/failed acceptance criteria”
Accepted deliverables	Deliverables formally accepted by customer or authorized party	“Customer signs acceptance”
Final report	Summary of project performance and outcomes	“Project is being closed”
Procurement records	Contract and seller documentation	“Contract closure, claims, acceptance”

Can You Do This? CAPM Skills Checklist

Foundation and Terminology

Explain project, program, portfolio, operation, PMO, governance, and business value.
Identify the correct role in a scenario.
Distinguish project deliverables from business outcomes.
Recognize constraints, assumptions, dependencies, and risks.
Explain why tailoring changes the project management approach.

Predictive Project Work

Identify the purpose of the charter, project management plan, and baselines.
Build the logical flow from requirements to scope statement to WBS to schedule and budget.
Determine when formal change control is required.
Distinguish validate scope from control quality.
Interpret earned value results.
Identify schedule compression options and their tradeoffs.
Choose appropriate risk responses.
Recognize when to update issue log, risk register, change log, or lessons learned.

Agile and Hybrid Work

Explain product backlog, sprint backlog, increment, Definition of Done, review, retrospective, and daily standup.
Identify the product owner’s role in prioritization.
Identify the Scrum Master or servant leader role in facilitation and impediment removal.
Use WIP limits and visual boards to improve flow.
Interpret burndown, burnup, and velocity at a basic level.
Choose adaptive responses when requirements evolve.
Recognize hybrid cues where governance is predictive but delivery is iterative.

Business Analysis

Elicit, analyze, document, validate, and manage requirements.
Distinguish functional and nonfunctional requirements.
Write or interpret user-story-style requirements.
Use acceptance criteria to determine completion.
Trace requirements to objectives, design, testing, and deliverables.
Prioritize requirements based on value, risk, dependency, and stakeholder need.
Identify whether a solution actually addresses the business need.

Scenario Judgment

Decide what to do next, not just define a term.
Select the right artifact to update.
Know when to escalate and when to facilitate.
Analyze impact before acting on change.
Involve the team in estimates and technical decisions.
Communicate with stakeholders at the right level of detail.
Apply ethical and professional judgment under pressure.

Calculation and Metric Checks

Estimating and Scheduling

Be comfortable with small calculation scenarios and interpretation.

Calculation area	What to practice	Interpretation
Three-point estimate	Optimistic, most likely, pessimistic	Expected estimate balances uncertainty
Communication channels	Number of possible communication paths	More people can increase communication complexity
Critical path	Longest path through network	Delay on critical path delays project finish
Float	Schedule flexibility	Activities with zero float are usually critical
Cost variance	EV minus AC	Negative is over cost
Schedule variance	EV minus PV	Negative is behind planned value
CPI	EV divided by AC	Less than 1 is cost efficiency concern
SPI	EV divided by PV	Less than 1 is schedule efficiency concern

Formula Readiness Prompts

Can you calculate the result?
Can you explain what the result means?
Can you identify the best management response?
Can you avoid confusing schedule variance with time variance?
Can you tell whether the project is over budget, under budget, ahead, or behind?
Can you identify whether a corrective action, change request, or forecast update may be needed?

Common Weak Areas and Traps

Weak area	Why it causes mistakes	How to fix it
Risk vs. issue	A risk is uncertain; an issue has occurred	Look for “may happen” vs. “has happened”
Validate scope vs. control quality	Scope validation is acceptance; quality control is inspection/testing	Ask whether the customer is accepting or the team is checking
Corrective vs. preventive action	Corrective addresses current variance; preventive reduces future risk	Identify whether the problem exists now
WBS vs. schedule	WBS decomposes deliverables/work; schedule sequences activities over time	WBS is not a timeline
Product backlog vs. WBS	Backlog is ordered product work; WBS is scope decomposition	Match artifact to delivery approach
Sprint review vs. retrospective	Review inspects product; retrospective improves process	Ask whether stakeholders or team process is the focus
Sponsor vs. project manager	Sponsor authorizes and supports; PM manages day-to-day integration	Escalate only when authority is needed
Product owner vs. project manager	Product owner prioritizes product value in agile contexts	Do not assign backlog ordering to the PM by default
Fast tracking vs. crashing	Fast tracking overlaps work; crashing adds resources	Fast tracking raises risk; crashing often raises cost
Reserve types	Contingency is for known risks; management reserve is for unknowns or higher-level control	Match reserve to risk knowledge and authority
Work performance data vs. reports	Data is raw; reports are formatted communication	Follow data to information to report
Scope creep	Uncontrolled expansion of scope	Use change control or backlog prioritization
Agile misunderstanding	Agile still has planning, quality, roles, and discipline	Look for transparency, feedback, and value delivery
Business value confusion	Delivering output is not always realizing benefit	Ask what outcome the project supports
Over-escalation	Many scenarios expect analysis, communication, or facilitation first	Escalate when authority or governance requires it
Ethics shortcut	Fastest action may not be fair, honest, or responsible	Choose transparency and professional conduct

High-Value Scenario Decision Table

Scenario pattern	First thing to consider	Strong answer behavior
Stakeholder requests extra scope	Is scope baselined or backlog-managed?	Use change control or backlog prioritization
Team discovers a defect	Is it a quality control finding?	Record, analyze, correct, and prevent recurrence
Project is behind schedule	What is the cause and critical path impact?	Analyze options before changing baseline
Project is over budget	What do EV and actual costs show?	Determine root cause and corrective action
New risk identified	Has it been analyzed and assigned?	Update risk register and plan response
Risk occurs	Is it now an issue?	Execute response, update issue log, communicate impact
Stakeholder is resistant	What is their influence and concern?	Engage, listen, adjust communication strategy
Requirements conflict	Who owns priority and value decisions?	Facilitate clarification and document resolution
Agile team has too much work started	Is flow constrained?	Use WIP limits and focus on finishing
Vendor misses deliverable	What does contract say?	Review procurement documents and manage seller performance
Customer rejects deliverable	Did it meet acceptance criteria?	Determine gap, address quality/scope issue, follow process
Team repeats same mistake	Has learning been captured?	Update lessons learned and improve process

Final-Week CAPM Review Checklist

Timeframe	Focus	Actions
7 days out	Identify weak domains	Re-score this checklist; choose the weakest 3 to 5 areas
6 days out	Predictive artifacts	Review charter, baselines, WBS, risk register, issue log, change log, and plans
5 days out	Agile and hybrid	Drill Scrum/Kanban roles, events, artifacts, backlog decisions, and tailoring cues
4 days out	Business analysis	Practice requirements, traceability, acceptance criteria, prioritization, and value questions
3 days out	Calculations	Rework earned value, three-point estimating, communication channels, float, and critical path
2 days out	Scenario judgment	Practice “what should the project manager do next?” questions and review explanations
1 day out	Light review	Revisit traps, formulas, artifact table, and personal notes; avoid heavy new content
Exam day	Calm execution	Read for delivery approach, role, artifact, and next action before choosing an answer

Final Self-Test Prompts

Before you consider yourself ready, answer these without notes:

A stakeholder asks for a change after the scope baseline is approved. What happens next?
A risk becomes real. Which artifact is updated?
A deliverable passes internal testing but the customer has not accepted it. What process is still needed?
A Scrum team finishes work that does not meet the Definition of Done. Is it complete?
The CPI is below 1. What does that suggest?
The team wants to overlap two sequential activities to save time. What technique is this, and what risk increases?
Requirements are uncertain and customer feedback is frequent. Which delivery approach is likely?
A high-influence stakeholder is resistant. What should be analyzed or updated?
A requirement changes. How do you assess impact?
A vendor dispute occurs. What documents should you review?

Practical Next Step

Use this CAPM Exam Blueprint to choose your next study block. Start with the areas you marked weakest, then move into mixed practice questions that force you to identify the delivery approach, role, artifact, and best next action. For final review, combine short formula drills with scenario-based practice so you are prepared for both terminology and judgment questions on the PMI Certified Associate in Project Management (CAPM) exam.

Study Plan

Scenario Guide