Project+ — CompTIA Project+ (PK0-005) Exam Quick Review

Quick Review purpose

This Quick Review is for candidates preparing for CompTIA Project+ (PK0-005), exam code Project+. It is designed to help you refresh the most testable project management ideas before moving into PM Mastery practice, topic drills, mock exams, and detailed explanations.

CompTIA Project+ questions often test whether you can choose the best project management action in a realistic scenario. The exam is not only about definitions. Expect questions that require you to recognize project constraints, stakeholder issues, documentation needs, change control, risk responses, communication problems, and project life cycle decisions.

Use this page to quickly review:

• What project documents are used for
• How scope, schedule, cost, quality, resources, and risk interact
• How to choose the right action when a project changes
• How to distinguish issues, risks, assumptions, constraints, and dependencies
• How to avoid common scenario-question traps

High-yield exam mindset

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

A strong test-taking rule: do not jump straight to execution when the correct answer is to document, analyze, communicate, or follow the approved process first.

Project basics you should know cold

Project vs. operations

A common trap is treating a temporary initiative as routine operations. If the work has a defined beginning, end, scope, and deliverables, treat it as a project.

Core project constraints

Project decisions often involve tradeoffs among:

• Scope — what is included and excluded
• Schedule — when work and deliverables are due
• Cost — budget, funding, and financial limits
• Quality — degree to which deliverables meet requirements
• Resources — people, equipment, tools, and facilities
• Risk — uncertainty that may affect objectives

If one constraint changes, at least one other constraint usually changes too. For example, increasing scope without changing schedule may require more resources, higher cost, lower quality, or higher risk.

Project life cycle quick review

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

Initiation

Initiation answers: Should this project exist, and who authorizes it?

Key concepts:

• Business case: explains why the project is valuable.
• Project charter: formally authorizes the project and gives the project manager authority.
• Stakeholder identification: determines who can affect or be affected by the project.
• High-level scope: describes major deliverables, boundaries, and objectives.

Common exam trap: Starting detailed planning or execution before authorization. If the project has not been formally approved, the better answer often involves business case approval or project charter creation.

Planning

Planning answers: How will the project be delivered and controlled?

Important plans and baselines:

Common exam trap: Choosing a communication or execution action before confirming the plan, baseline, or approval process.

Execution

Execution answers: How is the work performed and coordinated?

High-yield execution activities:

• Assigning work according to roles and responsibilities
• Managing team performance
• Coordinating vendors and external resources
• Holding status meetings
• Producing deliverables
• Performing quality assurance activities
• Communicating with stakeholders
• Updating logs and reports

Common exam trap: Ignoring the project plan. Execution should align with approved scope, schedule, budget, quality, and communication expectations.

Monitoring and controlling

Monitoring and controlling answers: Are we on track, and what must be adjusted?

High-yield activities:

• Compare actual progress to the baseline
• Track issues, risks, changes, and defects
• Analyze schedule and budget variances
• Validate deliverables against acceptance criteria
• Escalate according to thresholds
• Report status to stakeholders
• Manage approved changes

Common exam trap: Making informal changes. If a change affects scope, schedule, cost, quality, or risk, it should go through change control.

Closure

Closure answers: Is the project formally complete?

Key closure steps:

1. Verify deliverables against acceptance criteria.
2. Obtain formal acceptance.
3. Close contracts and vendor obligations.
4. Release project resources.
5. Archive project documents.
6. Capture lessons learned.
7. Communicate final status.

Common exam trap: Treating work completion as project closure. A deliverable being finished is not the same as formal acceptance and administrative closure.

Project documents and artifacts

High-yield document table

RACI review

RACI is commonly tested because it clarifies roles.

Common trap: More than one person may be responsible, but accountability should be clear. If everyone owns the result, no one owns the result.

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

Schedule management

Schedule building blocks

Dependency types

Most scenario questions use finish-to-start dependencies, but do not assume every dependency is the same.

Schedule compression

Common trap: If the question says the budget cannot increase, crashing may not be best. If the question says quality/rework risk is unacceptable, fast tracking may not be best.

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.

Quality management

Quality is about meeting requirements and acceptance criteria, not simply adding premium features.

Quality vs. grade

A low-grade product can still be high quality if it meets requirements. A high-grade product can be low quality if it fails to meet requirements.

Common exam trap: Choosing “add more features” when the problem is quality. Quality means conforming to requirements, not gold-plating.

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

If the event has already occurred, it is no longer a risk; it is an issue.

Risk register essentials

A useful risk entry usually includes:

• Risk description
• Cause
• Potential impact
• Probability
• Impact rating
• Risk owner
• Response strategy
• Trigger
• Status
• Contingency plan

Negative risk response strategies

Positive risk response strategies

Common trap: Transferring a risk does not make it disappear. It shifts responsibility for some consequences, often through a contract or insurance mechanism.

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.

Change control

Change control is a major exam decision point.

Change request workflow

    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]

What to analyze before approval

Common trap: Implementing a change because it sounds small. Even small changes may affect baselines, dependencies, budget, or risk.

Stakeholder management

Stakeholders are people or groups that can affect, be affected by, or perceive themselves to be affected by the project.

Stakeholder analysis

Consider:

• Level of influence
• Level of interest
• Expectations
• Communication preferences
• Decision authority
• Support or resistance
• Impact on project success

Common stakeholder traps

• Ignoring quiet but powerful stakeholders
• Communicating the same level of detail to every audience
• Failing to document approvals
• Assuming the sponsor and end users have identical expectations
• Not managing resistance to change
• Waiting until closure to validate acceptance criteria

For scenario questions, identify whose approval, input, or awareness matters before choosing the communication action.

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.

Team and resource management

Resource types

Team development stages

Conflict resolution approaches

Common exam trap: Avoiding conflict when the scenario needs active resolution. For important project conflicts, collaboration/problem solving is usually stronger than ignoring the issue.

Procurement and vendor management

Project+ scenarios may include vendors, contracts, statements of work, and service expectations.

Procurement terms

Contract type decision review

Common trap: Choosing fixed-price when the scope is vague. Fixed-price works best when requirements are stable and well understood.

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

Charter vs. plan

Sponsor vs. project manager

Lessons learned timing

Lessons learned are not only for the end. They are most useful when captured throughout the project.

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

How to use this with question-bank practice

Use this Quick Review first, then move into PM Mastery practice:

1. Start with topic drills on weak areas such as risk, change control, project documents, schedule concepts, and stakeholder communication.
2. Answer original practice questions in timed sets so you learn how CompTIA Project+ (PK0-005) scenarios are phrased.
3. Read detailed explanations for every missed or guessed question, including why the wrong answers are tempting.
4. Keep a short error log organized by concept: risk vs. issue, change control, closure, communication, schedule, procurement, or quality.
5. Re-test with mixed question bank sets until you can identify the project management problem before looking at the answer choices.

Practical next step: choose one weak topic from this Quick Review and complete a focused set of original practice questions with detailed explanations before attempting a full mock exam.

Continue in PM Mastery

Use this Quick Review as a final concept map, then move into PM Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original PM Mastery practice items; they are not official CompTIA questions, copied live-exam content, or exam dumps.