CompTIA Project+ (PK0-005) FAQ

Project+ rewards controlled delivery thinking more than methodology trivia. The best answer is usually the one that keeps scope, approvals, communication, and evidence of decision-making intact under pressure.

What does Project+ (PK0-005) actually test?

Project+ tests project management fundamentals in real delivery contexts, especially technology work. CompTIA’s current PK0-005 objectives emphasize project management concepts, risk, issue handling, scheduling, communication, governance, and delivery-method choices. The exam is less about memorizing a single methodology and more about recognizing the most disciplined next step.

Is Project+ more IT or more project management?

It is project management first, but framed for practical business and technology work. You do not need deep engineering detail, yet you do need to understand how change control, risk, communication, procurement, and scheduling affect technical delivery.

How long is the exam and what score do I need?

CompTIA lists the current Project+ PK0-005 exam as 90 minutes, up to 90 questions, with multiple-choice and performance-based items. The published passing score is 710 on a 100-900 scale, and CompTIA currently positions it as version V5.

Which documents matter most on Project+?

The documents that appear repeatedly are the ones that control authority, scope, coordination, and change:

• Project charter for authorization
• Scope statement for boundaries
• WBS for decomposition
• Schedule for sequencing and milestones
• Risk register for uncertain threats and opportunities
• Issue log for current problems
• Communication plan for stakeholder updates
• Change log for approved and rejected changes
• RACI for role clarity

If you cannot distinguish those, the exam feels harder than it really is.

What is the difference between a risk and an issue?

A risk is uncertain and may happen later. An issue has already happened and now requires action. Project+ will often show you a problem that has become real and then tempt you with “update the risk register” when the better answer is “log the issue, assign ownership, and resolve it.”

How should I think about change control?

Project+ wants you to protect the baseline without becoming rigid for its own sake.

The safe pattern is:

1. Capture the request.
2. Assess impact on scope, schedule, cost, risk, and quality.
3. Send it through the right approval path.
4. Update the baseline and communications if approved.
5. Implement and monitor.

“Just do it and update later” is almost always a trap.

Do I need to know predictive, agile, and hybrid delivery?

Yes, but at the decision level:

• Predictive fits stable scope and heavier governance.
• Agile fits high uncertainty and frequent feedback.
• Hybrid fits mixed environments where some work is stable and some is exploratory.

The exam wants a reasonable match between delivery approach and project conditions, not ideology.

What do critical path and float really mean?

The critical path is the longest path through the schedule and determines finish date. Float or slack is the amount of time a task can move before it affects a later milestone or final completion. If a task has float, the right answer may be “monitor and re-sequence” rather than “escalate immediately.”

What is a common communication mistake on Project+ questions?

Under-communicating because the team thinks everyone already knows what changed. Project+ strongly prefers:

• planned stakeholder communication
• documented decisions and action items
• escalation through agreed paths
• status updates that explain impact, not just activity

What are the most common Project+ traps?

• confusing the charter with the full project plan
• mixing up risks and issues
• skipping change approval because the request came from a sponsor
• assuming schedule pressure automatically means overtime or more people
• treating a retrospective like a stakeholder acceptance review
• escalating before documenting impact and options

How should I study efficiently?

A focused 3-4 week plan works well for many learners:

• Week 1: lifecycle, documents, roles, communication, governance
• Week 2: scheduling, dependencies, critical path, resource planning
• Week 3: risk, issue, change control, quality, procurement, delivery methods
• Week 4: scenario drills, mock sets, and miss-log review

Keep a one-line decision log from missed questions, such as “real problem = issue log, not risk register” or “scope change needs approval before execution.”

What is a smart next step after Project+?

That depends on the role. If you are moving deeper into formal project management, PMP or CAPM may be the next move. If you are staying close to delivery operations, continue building actual project coordination habits: maintain schedules, logs, action items, and change records in real work instead of only studying the concepts.

Quiz