CompTIA Project+ PK0-005 Cheat Sheet

Review a compact CompTIA Project+ (PK0-005) cheat sheet for lifecycle sequencing, project documents, stakeholders, change control, risk, governance, and IT project scenarios before PM Mastery practice.

Use this cheat sheet before a CompTIA Project+ practice set. Project+ questions usually test practical coordination: what to document, who to involve, and which governance path comes next.

Open Project+ practice when you are ready for timed mocks, topic drills, explanations, and the full PM Mastery question bank.

Exam snapshot

ItemProject+ cue
VendorCompTIA
ExamProject+
Exam codePK0-005
Main practice behaviorpractical project delivery, documentation, stakeholders, risk, and governance
PM Mastery statuslive practice available

Topic checklist

AreaWhat to knowCommon trap
Lifecycleinitiation, planning, execution, monitoring/control, and closeclosing or executing before acceptance and controls are complete
Delivery approachpredictive, agile, and hybrid fitusing agile language for every uncertain situation
Stakeholderscommunication needs, escalation, authority, and expectationsbroadcasting status instead of tailoring communication
Documentscharter, schedule, RAID log, change request, status report, and lessons learnedcreating artifacts without a decision purpose
Risk and issue handlingrisk response, issue ownership, escalation, and impact communicationleaving a realized risk in the risk register only
Governanceapprovals, compliance, change control, and decision recordsbypassing controls to move faster

Must-know distinctions

  • Risk versus issue: a risk may happen; an issue is already happening.
  • Change request versus defect: one changes approved scope; the other corrects expected work.
  • Charter versus scope statement: the charter authorizes; scope defines deliverables and boundaries.
  • Stakeholder register versus communication plan: one identifies people; the other defines information flow.
  • Baseline versus forecast: a baseline is approved reference; a forecast predicts future performance.
  • Escalation versus communication: escalation seeks authority or action, not just awareness.

Common traps

  • Rebaselining before corrective action and approval.
  • Approving vendor changes informally.
  • Treating stakeholder surprise as a reason to send more generic reports.
  • Skipping impact analysis because the request looks small.
  • Confusing risk response planning with issue resolution.

Practice strategy

After the free diagnostic, classify misses by lifecycle, document, stakeholder, change, risk, or governance. Then practice mixed scenarios until the next action feels tied to control and evidence, not just project-management vocabulary.

Revised on Monday, May 25, 2026