CAPM — PMI Certified Associate in Project Management Quick Review

Quick Review purpose

This Quick Review is for candidates preparing for the real PMI Certified Associate in Project Management (CAPM) exam from PMI, exam code CAPM. Use it to refresh high-yield concepts before working through topic drills, mock exams, and detailed explanations.

The CAPM rewards candidates who can do more than recognize terms. You need to connect project management vocabulary to realistic scenarios: which artifact is used, what the project manager should do next, which lifecycle fits the situation, and how to avoid common “sounds right but not best” answers.

This page is PM Mastery review support and companion practice guidance. It is not affiliated with PMI.

Exam identity

High-yield review map

Project management fundamentals

Project, program, portfolio, and operations

Core project constraints

CAPM questions often hide the real issue inside one constraint while distracting you with another.

Organizational structures

Project manager behavior that is usually favored

In scenario questions, the best project manager usually:

• Uses documented processes before acting informally.
• Communicates early and appropriately.
• Engages stakeholders instead of avoiding conflict.
• Uses data, baselines, and agreed criteria.
• Facilitates team problem solving.
• Protects value and quality.
• Tailors the approach to the project context.
• Escalates only after reasonable project-level action is insufficient.

Delivery approach decision rules

Choosing the lifecycle is a frequent decision point. Focus on uncertainty, change frequency, stakeholder involvement, and ability to define requirements early.

    flowchart TD
	    A[Start with product and project uncertainty] --> B{Requirements stable and well understood?}
	    B -- Yes --> C{Technology and work approach familiar?}
	    C -- Yes --> D[Predictive approach likely fits]
	    C -- No --> E[Hybrid may fit: plan governance, adapt technical work]
	    B -- No --> F{Frequent stakeholder feedback possible?}
	    F -- Yes --> G[Adaptive or agile approach likely fits]
	    F -- No --> H[Hybrid with discovery, prototypes, and staged decisions]

Predictive project management essentials

Initiating

High-yield idea: initiating authorizes the project and identifies key stakeholders. It does not create every detailed plan.

Planning

Planning defines how the project will be executed, monitored, controlled, and closed.

Executing

Executing is where the team performs the work and the project manager facilitates delivery.

Common executing activities:

• Direct and manage project work.
• Manage quality.
• Acquire, develop, and manage the team.
• Manage communications.
• Implement risk responses.
• Conduct procurements.
• Manage stakeholder engagement.

Exam trap: executing is not uncontrolled doing. Work should follow the approved plan, and problems should feed monitoring, controlling, or change control when needed.

Monitoring and controlling

Monitoring and controlling compares actual performance against the plan and recommends corrective action.

Closing

Closing confirms completion, acceptance, transition, records, lessons learned, and release of resources.

Common trap: closing is not only administrative. It includes formal acceptance, final reporting, procurement closure where applicable, archiving records, and capturing lessons learned.

Scope, requirements, and change control

Product scope vs project scope

WBS essentials

The work breakdown structure is a hierarchical decomposition of the total project scope.

Remember:

• The WBS organizes deliverables and work packages.
• The WBS dictionary gives detail about WBS components.
• The scope baseline includes the approved scope statement, WBS, and WBS dictionary.
• The WBS is not the same as the schedule; activities are developed from work packages.

Integrated change control

When a requested change could affect scope, schedule, cost, quality, risk, or baselines, do not simply “do the work.”

Typical sequence:

1. Document the change request.
2. Assess impact on scope, schedule, cost, quality, resources, risk, and stakeholders.
3. Submit to the appropriate change control authority.
4. Communicate the decision.
5. Update plans, baselines, and documents if approved.
6. Implement and verify the approved change.

Common trap: “The customer is important, so implement immediately” is usually wrong if the change affects approved baselines.

Schedule review

Dependencies

Leads and lags

Critical path and float

The critical path is the longest path through the network and usually determines the shortest project duration. Activities on the critical path generally have zero total float, but always rely on the data in the question.

Schedule compression

Cost and earned value review

Key cost terms

Earned value basics

Know the meaning before memorizing formulas.

High-yield formulas:

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

Fast interpretation rule:

• Variance: positive is generally good.
• Index: greater than 1 is generally good.
• If EV is lower than PV, the project has earned less value than planned.
• If AC is higher than EV, the project spent more than the value earned.

Quality review

Quality vs grade

Do not assume higher grade means higher quality.

Prevention, inspection, and cost of quality

Quality assurance vs quality control

Resource and team review

Team development

A common model describes team progression as forming, storming, norming, performing, and adjourning.

Conflict resolution

Exam trap: “Avoid the conflict” is seldom best when the conflict affects project objectives or team performance.

Responsibility assignment

A RACI chart clarifies roles:

Communications review

Communication questions often test the method, not just the message.

Communication channel formula:

\[ \text{Number of communication channels} = \frac{n(n-1)}{2} \]

Where \(n\) is the number of people.

Common trap: adding one stakeholder increases channels by more than one because that person can communicate with every existing person.

Risk review

Risk vs issue

Threat responses

Opportunity responses

Expected monetary value:

\[ \text{EMV} = \text{Probability} \times \text{Impact} \]

For decision trees, multiply each outcome by its probability and sum the results for each option.

Procurement review

Contract types

Common traps:

• Fixed price is not automatically best; unclear scope can cause disputes and change requests.
• Cost reimbursable does not mean uncontrolled spending; it still needs oversight.
• Procurement documents should match the type of work and the desired risk allocation.

Stakeholder review

Identify, analyze, engage

Stakeholder engagement levels

Exam trap: the best answer is often to engage, understand concerns, and communicate value—not ignore resistance or escalate immediately.

Agile and adaptive essentials

Agile mindset

Agile questions usually favor:

• Frequent delivery of usable value.
• Close customer or stakeholder collaboration.
• Welcoming change when it improves value.
• Self-organizing, empowered teams.
• Transparency through visual work and regular feedback.
• Continuous improvement through retrospectives.

Agile does not mean no planning. It means planning is continuous and adaptive.

Scrum review

Common trap: the daily Scrum is not a status meeting for the project manager. It is for the team to coordinate.

Kanban review

Common trap: adding more work to a clogged system usually worsens flow. Reduce WIP and address bottlenecks.

Agile estimation and tracking

User stories

A common user story pattern is:

“As a [user], I want [capability], so that [benefit].”

Good user stories are small enough to complete, testable, valuable, and understood by the team. Acceptance criteria clarify when the story satisfies the need.

Hybrid project management

Hybrid questions test tailoring. A project can use predictive planning for governance, funding, compliance, or major milestones while using agile delivery for uncertain product features.

Common trap: do not force every project into agile. The best approach depends on uncertainty, risk, stakeholder availability, and organizational needs.

Business analysis essentials

Need, requirement, and solution

Requirement types

Elicitation techniques

Verification vs validation

Common trap: a requirement can be documented clearly and still fail to solve the real business problem.

Formula quick sheet

PERT expected duration

\[ \text{Expected duration} = \frac{O + 4M + P}{6} \]

Where:

• \(O\) = optimistic estimate
• \(M\) = most likely estimate
• \(P\) = pessimistic estimate

Communication channels

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

Earned value interpretation

Common CAPM candidate traps

Trap 1: Memorizing terms without context

Many wrong answers use correct vocabulary in the wrong situation. Practice identifying the project phase, lifecycle, artifact, and decision point before choosing.

Trap 2: Skipping change control

If an approved baseline may change, use formal change control. Do not implement just because the sponsor, customer, or senior stakeholder requested it.

Trap 3: Confusing risks and issues

A risk may happen. An issue has happened. Risk responses are planned proactively; issue management is immediate and corrective.

Trap 4: Treating agile as unplanned work

Agile uses planning, prioritization, quality standards, reviews, and retrospectives. It is adaptive, not chaotic.

Trap 5: Choosing escalation too quickly

Escalation can be correct, but only when the matter exceeds the project manager’s authority or reasonable project-level action has failed.

Trap 6: Ignoring stakeholders

Stakeholder resistance usually calls for analysis, engagement, communication, and understanding—not avoidance.

Trap 7: Misreading “best,” “first,” and “next”

• First often means identify, document, assess, or understand before acting.
• Next means the immediate logical step in the process.
• Best means the most professional, proactive, and process-aligned answer.
• Most likely asks for diagnosis, not necessarily the ideal action.

Scenario-answering checklist

Use this quick mental sequence on practice questions:

1. Identify the lifecycle. Predictive, agile, or hybrid?
2. Find the moment. Initiating, planning, executing, monitoring/controlling, or closing?
3. Name the issue. Scope, schedule, cost, quality, risk, resources, communications, procurement, stakeholder, or business analysis?
4. Look for the artifact. Charter, plan, baseline, backlog, risk register, stakeholder register, requirements traceability matrix, etc.
5. Apply the rule. Change control, stakeholder engagement, risk response, team facilitation, or value delivery?
6. Eliminate weak answers. Ignore, blame, act without approval, gold-plate, over-escalate, or skip analysis.
7. Choose the most professional next step.

Practice focus before exam day

Use this Quick Review as a checklist, then move into PM Mastery practice:

A strong final review cycle is: read this Quick Review, complete focused topic drills, review detailed explanations, then sit for a mixed mock exam and update your error log.

Practical next step

Start with a short set of CAPM topic drills in your weakest area, then review every explanation carefully—especially for questions where two answers seemed plausible.

Continue in PM Mastery

Use this Quick Review as a final concept map, then move into PM Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original PM Mastery practice items; they are not official PMI questions, copied live-exam content, or exam dumps.