Project+ Cheat Sheet

CompTIA Project+ Tests Practical Project Management — Without the PMBOK Overhead

Project+ covers the full project lifecycle but focuses on practical, applied scenarios rather than PMBOK process memorization.

Check Your Readiness →

Among the harder certs

Avg: Approximately 63–68%

Pass: 750 / 1000

Most candidates understand CompTIA Project+ concepts — and still fail. This exam tests how you apply knowledge under pressure.

Core Framework

Project+ Project Lifecycle Framework

CompTIA Project+ tests practical project management skills across the full lifecycle. The exam uses scenario-based questions that test judgment rather than terminology recall.

01
Initiating — Define the project, identify stakeholders, create the project charter
02
Planning — Scope, schedule, budget, risk, communications, quality planning
03
Executing — Coordinate team, manage stakeholders, produce deliverables
04
Monitoring & Controlling — Track progress, manage changes, report status
05
Closing — Obtain acceptance, release resources, document lessons learned

Scenario Traps

Wrong instinct vs correct approach

A team member is consistently underperforming on assigned tasks

✕ Wrong instinct

Escalate to HR immediately

✓ Correct approach

Address the performance issue directly with the team member first — understand the root cause, provide support or coaching, and only escalate if the direct approach fails

A stakeholder asks for a feature that wasn't in the original scope

✕ Wrong instinct

Implement it since it's a reasonable addition

✓ Correct approach

Log the request, assess impact on scope, schedule, and cost, present options to the project sponsor, and only implement after formal change control approval — scope creep is the most common project failure mode

The project is behind schedule at the midpoint

✕ Wrong instinct

Add more team members to speed up delivery

✓ Correct approach

Assess root cause first. Brooks' Law warns that adding people to a late project makes it later — address the cause, not the symptom

Quick Rules

Know these cold

▸ Triple constraint: scope, schedule, cost — changing one affects the others
▸ All changes go through formal change control — no exceptions for small changes
▸ Risk management is continuous — update the risk register throughout execution
▸ Conflict resolution — ollaborate → compromise → accommodate → avoid → force (worst)
▸ Lessons learned are documented throughout, not just at project close
▸ Project charter authorizes the PM — without it, the PM has no authority
▸ Stakeholder register must be maintained as stakeholders change throughout the project

Self Check

Can you answer these without checking your notes?

In this scenario: "A team member is consistently underperforming on assigned tasks" — what should you do first?

Address the performance issue directly with the team member first — understand the root cause, provide support or coaching, and only escalate if the direct approach fails

In this scenario: "A stakeholder asks for a feature that wasn't in the original scope" — what should you do first?

In this scenario: "The project is behind schedule at the midpoint" — what should you do first?

Assess root cause first. Brooks' Law warns that adding people to a late project makes it later — address the cause, not the symptom

Failure Patterns

Common Exam Mistakes — What candidates get wrong

Confusing project constraints without understanding their relationships

Scope, schedule, and cost are the triple constraint — changes to one affect the others. Candidates who evaluate constraint trade-offs in isolation miss the interconnected impact questions.

Treating risk identification as a planning-only activity

Risks must be identified and managed throughout the project lifecycle. New risks emerge during execution — candidates who stop updating the risk register after planning miss ongoing risk management questions.

Skipping formal change control for small changes

All changes must go through change control regardless of size. Informal changes create scope creep, budget overruns, and schedule delays. The exam penalizes any answer that approves changes outside formal change control.

Confusing the project manager's role in conflict resolution

Project managers use a conflict resolution hierarchy: collaborate (best), compromise, accommodate, avoid/withdraw, force (worst). Candidates who force decisions or avoid conflict miss situational judgment questions.

Misidentifying the purpose of lessons learned

Lessons learned capture what worked and what didn't for future project improvement. They are created throughout the project and finalized at closing — not just at the end.

Project+ tests practical project judgment. Test whether you'd make the right call in a real project scenario.

Start Diagnostic Test → View all exams