Project+ — CompTIA Project+ (PK0-005) Exam Cheat Sheet

Use the tables for a quick pre-exam check. Expand a topic’s notes for explanations, examples, and additional distinctions.

Project Lifecycle Quick Map

    flowchart TD
	    A[Need, opportunity, problem, or mandate] --> B[Business case / charter]
	    B --> C{Authorized?}
	    C -- No --> X[Do not execute project work]
	    C -- Yes --> D[Plan scope, schedule, cost, quality, resources, communications, risks, procurement]
	    D --> E[Execute work and manage team, vendors, and stakeholders]
	    E --> F[Monitor performance, risks, issues, changes, quality]
	    F --> G{Change requested?}
	    G -- Yes --> H[Analyze impact and submit through change control]
	    H --> I{Approved?}
	    I -- Yes --> J[Update baselines, plans, logs, and communicate]
	    I -- No --> K[Communicate decision and prevent scope creep]
	    J --> E
	    K --> E
	    G -- No --> L{Deliverables accepted?}
	    L -- No --> E
	    L -- Yes --> M[Close procurements, transition, archive, lessons learned]

Predictive, Adaptive, and Hybrid Selection

Core Roles and Responsibilities

Artifact Selection Reference

Document Type Distinctions

“What Should the Project Manager Do Next?” Decision Table

Change Control Cheat Sheet

    flowchart TD
	    A[Change requested] --> B[Document the request]
	    B --> C[Analyze impact]
	    C --> D{Affects scope, schedule, cost, quality, resources, or risk?}
	    D -- No --> E[Handle within project authority]
	    D -- Yes --> F[Submit to change control process]
	    F --> G{Approved?}
	    G -- No --> H[Record decision and communicate]
	    G -- Yes --> I[Update baselines, plans, logs, and stakeholders]
	    I --> J[Implement approved change]

Scope, Schedule, Cost, and Quality

Schedule and Estimating Reference

Earned Value and Performance Formulas

Core terms:

Communication Formulas and Methods

Number of communication channels with \(n\) participants:

Stakeholder Management

Risk, Issue, Action, and Decision Logs

Quality Management Cheat Sheet

Procurement and Vendor Reference

Resource and Team Management

RACI Meanings

Conflict and Leadership Responses

Exam pattern: choose collaboration/problem solving for important project conflicts unless the scenario clearly requires urgent direction, escalation, or compliance action.

Meetings and Status Controls

Governance and Escalation

IT and Operational Transition Focus

CompTIA Project+ candidates often see project scenarios tied to technology delivery, service transition, implementation, or vendor-supported work.

Common Exam Traps

Last-Minute Review Checklist

High-yield exam mindset

For CompTIA Project+ (PK0-005), many questions come down to disciplined project control.

Project basics you should know cold

Project vs. operations

Project life cycle quick review

CompTIA Project+ scenarios frequently ask what should happen next in the project life cycle.

Project documents and artifacts

High-yield document table

Scope management

Scope management prevents uncontrolled expansion and unclear expectations.

Scope terms

Scope decision rule

If a stakeholder requests additional work:

1. Determine whether the request is already in scope.
2. If unclear, review the scope statement, WBS, and requirements.
3. If it is new or changes approved work, create a change request.
4. Analyze impact on schedule, cost, quality, resources, and risk.
5. Submit for approval according to the change process.
6. Update baselines and communicate only after approval.

Do not accept “the customer asked for it” as automatic authorization to change the project.

Requirements review

Requirements define what the solution must do or achieve.

Common mistakes:

• Confusing requirements with design decisions
• Failing to validate requirements with stakeholders
• Missing nonfunctional requirements
• Accepting ambiguous terms such as “fast,” “easy,” or “secure” without measurable criteria
• Allowing requirements changes without change control

Cost and budget review

Project+ candidates should understand budgeting concepts and cost-control thinking.

Common trap: Continuing a bad project because money has already been spent. Sunk cost should not justify poor future decisions.

Risk management

Risk is one of the most important Project+ areas because scenarios often test the difference between a possible future event and a current problem.

Risk vs. issue

Issue management and escalation

An issue is a current condition affecting the project.

Good issue management process

1. Log the issue.
2. Categorize and assess impact.
3. Assign an owner.
4. Determine priority.
5. Identify resolution options.
6. Escalate if it exceeds authority or thresholds.
7. Track to closure.
8. Communicate status to affected stakeholders.

Escalation is appropriate when:

• The project manager lacks authority to resolve it
• The issue crosses defined thresholds
• A decision is needed from sponsor or governance group
• The issue affects major scope, schedule, cost, quality, or risk baselines
• A conflict cannot be resolved at the project level

Common trap: Escalation is not the first step for every problem. Use the issue process, but escalate when authority, impact, or urgency requires it.

Communication management

Communication questions usually test matching the message, audience, timing, and method.

Communication methods

Communication plan contents

A communication plan should define:

• Audience
• Information needs
• Format
• Frequency
• Owner/sender
• Distribution method
• Escalation path
• Confidentiality or access considerations

Common trap: More communication is not always better. The right answer is usually targeted, timely, and appropriate communication.

Agile, predictive, and hybrid concepts

CompTIA Project+ candidates should recognize different delivery approaches.

Agile terms to recognize

Common trap: Agile does not mean “no planning” or “no control.” Agile uses frequent planning, prioritization, review, and adaptation.

Governance, compliance, and organizational context

Governance defines how decisions are made and controlled.

High-yield governance concepts:

• Approval authority
• Escalation paths
• Change control board or decision body
• Compliance requirements
• Auditability
• Document retention
• Security and privacy expectations
• Organizational policies
• Project selection and prioritization

Common trap: Choosing a technically convenient action that violates governance, approval, security, or compliance expectations. In exam scenarios, the project manager should follow organizational processes.

Assumptions, constraints, and dependencies

These three are easy to confuse.

Decision rule:

• If it is believed but not guaranteed, it is an assumption.
• If it limits choices, it is a constraint.
• If one thing relies on another, it is a dependency.
• If uncertainty could affect objectives, track it as a risk.

Status reporting and performance review

Status questions often ask what information should be communicated.

Common status elements

Common trap: Reporting only good news. Effective status reporting is transparent and highlights risks, issues, and decisions needed.

Meeting types and when to use them

Common trap: Holding a meeting without a purpose. The best answer often names the meeting that matches the project need.

Security, privacy, and IT project awareness

Because CompTIA Project+ is often used in technology project contexts, expect practical awareness of IT project concerns.

High-yield IT project considerations:

• Access control for project tools and repositories
• Data sensitivity and confidentiality
• Change windows and maintenance windows
• Backup and rollback planning
• Testing environments versus production environments
• User acceptance testing
• Deployment communication
• Incident and problem escalation
• Vendor access management
• Documentation and knowledge transfer

Common trap: Deploying a change without stakeholder communication, approval, testing, or rollback planning.

Common “best next step” patterns

Common candidate mistakes

Mistake 1: Confusing risks and issues

• Risk: might happen.
• Issue: has happened.

If the scenario says “may,” “could,” or “potential,” think risk. If it says “is,” “has,” or “did,” think issue.

Mistake 2: Skipping change control

Stakeholder requests are not automatically approved changes. Analyze impact and follow the change process.

Mistake 3: Choosing escalation too quickly

Escalate when authority, impact, or policy requires it. Otherwise, log, analyze, assign, and manage the item first.

Mistake 4: Treating communication as one-size-fits-all

Executives, technical teams, vendors, customers, and end users need different levels of detail.

Mistake 5: Ignoring acceptance criteria

A deliverable is not done just because the team says it is done. It must meet agreed acceptance criteria and receive appropriate approval.

Mistake 6: Selecting tools before understanding the problem

A project management tool does not fix unclear scope, missing requirements, weak governance, or poor stakeholder alignment.

Mistake 7: Confusing quality with extra features

Quality means meeting requirements. Extra features can create scope creep, cost increases, risk, and maintenance burden.

Quick scenario decision checklist

Before answering a scenario question, ask:

1. What phase is the project in?
2. Is this a risk, issue, change, defect, or communication problem?
3. Is the event future uncertainty or a current fact?
4. Does it affect scope, schedule, cost, quality, resources, or risk?
5. Is there an approved process or plan that should be followed?
6. Who has authority to decide?
7. Who needs to be informed, consulted, or approving?
8. What documentation should be updated?
9. Is the question asking for the first step, best step, or final resolution?
10. Which answer is most controlled, professional, and process-aligned?

Mini review tables

Risk, issue, change, and defect

Final review before practice

Before moving into original practice questions, make sure you can explain these without notes:

• The purpose of a business case, charter, WBS, risk register, issue log, change log, communication plan, and RACI chart
• The difference between risk, issue, assumption, constraint, and dependency
• The correct response to a stakeholder change request
• How crashing differs from fast tracking
• Why formal acceptance matters during closure
• How to match communication method to audience and urgency
• When to escalate and when to manage within the project team
• Why quality means meeting requirements, not adding extras
• How predictive, Agile, and hybrid approaches differ
• How vendor contracts and scope clarity affect project risk

Put the review into practice