CompTIA PK0-005 Project Management Concepts Guide

Study CompTIA PK0-005 Project Management Concepts: key concepts, common traps, and exam decision cues.

This chapter carries the most weight on PK0-005, and it earns that weight because these are the habits that keep every later phase under control. CompTIA keeps coming back to methodology fit, change control, risk and issue handling, schedule logic, communication, and procurement choices.

Mitigation: A response that reduces the probability or impact of a risk.

RACI: A role matrix that clarifies who is responsible, accountable, consulted, and informed.

Current weight in the objectives

CompTIA currently weights this domain at 33% of the Project+ exam.

Work this domain in order

Lesson Focus
1.1 Project Characteristics, Delivery Methods and Change Control Compare predictive, agile, and hybrid delivery, classify project characteristics, and protect controlled change.
1.2 Risk, Issue and Schedule Management Separate risks from issues, choose response strategies, and reason through milestones, dependencies, float, and critical path.
1.3 Quality, Communication and Meeting Management Understand how quality signals, communication paths, and meeting discipline protect execution.
1.4 Team, Resource and Procurement Management Work through resource gaps, role clarity, team performance, vendor selection, and contract-minded decisions.

Fast routing inside this chapter

If the question is really about… Go first to…
predictive vs agile vs hybrid 1.1 Project Characteristics, Delivery Methods and Change Control
risk, issue, response strategy, or schedule slip 1.2 Risk, Issue and Schedule Management
stakeholder updates, meeting discipline, or quality evidence 1.3 Quality, Communication and Meeting Management
staffing, role confusion, vendors, or procurement 1.4 Team, Resource and Procurement Management

What strong answers usually do

  • classify the scenario before reaching for a tool
  • keep changes governed even when the request sounds reasonable
  • choose the artifact or action that protects traceability
  • separate delivery pressure from authority to make baseline changes

If two answers both sound right in this chapter

Use these tie-breakers:

If the close answers differ on… Lean toward…
fast action vs controlled action the answer that preserves approval, ownership, and evidence
risk language vs issue language the answer that matches whether the problem is future or current
team preference vs project fit the answer that matches the actual work conditions
vendor convenience vs contract control the answer that keeps scope, cost, and approval disciplined

Common Project+ traps

  • choosing agile because it sounds modern rather than because uncertainty justifies it
  • treating a live blocker like a future risk
  • confusing more communication with better communication
  • letting vendor urgency override formal scope and change control

Late-stage review bias

When time is short, protect these lessons first:

  1. 1.1 Project Characteristics, Delivery Methods and Change Control
  2. 1.2 Risk, Issue and Schedule Management
  3. 1.3 Quality, Communication and Meeting Management

Where this chapter shows up later

Even when the exam moves into life cycle, tools, or IT governance, the reasoning still starts here. Treat this domain as the control layer for everything else.

In this section

Revised on Sunday, May 10, 2026