FREE CompTIA Project+ Study Guide 2026: PK0-005

This free CompTIA Project+ study guide walks through every content domain the Project+ (PK0-005) exam tests, organized to the current CompTIA exam objectives.^[1]

It’s interactive, not a wall of text: every module has built-in checkpoint quizzes, flashcards, and practice questions, so you learn by doing — not just reading.

The Project+ tests four official domains, and we teach them as four study modules, leading with the heaviest-weighted content (Project Management Concepts and Project Life Cycle Phases together are nearly two-thirds of the exam). Read a module, test yourself at each checkpoint, then drill gaps with our free practice test and flashcards. This guide is a high-yield overview that maps the official content — not a full project management textbook.

CompTIA Project+ is one of the 14 CompTIA certifications — explore our CompTIA study guides to compare and prep across the whole family.

Project+ Exam Snapshot

The Project+ covers four domains. The first two — Project Management Concepts and Project Life Cycle Phases — together make up 63% of the exam, so that is where to invest first.^[1] Study by weight:

Module 1 · Project Management Concepts

One official domain, 33% of the exam — the single heaviest. This is the vocabulary and mechanics of project management: methodologies, the constraints every project balances, and how you control change, risk, schedule, quality, communication, teams, and procurement. Master this domain and the rest of the exam gets far easier.

1.1 Methodologies & Characteristics

A Project is a temporary effort to create a unique result — distinct from ongoing operations. Bigger structures group projects: a Program is related projects managed together, and a Portfolio is the whole collection aligned to strategy. Every project balances the Triple constraint: scope, time, and cost, with quality at the center.

The biggest methodology decision is predictive vs. adaptive. Waterfall is sequential and plan-driven — you define requirements up front and move through phases once. Agile is iterative: you deliver working increments in sprints and welcome change. Project+ tests when to choose each based on tolerance for change, team composition, and communication style.^[1]

Know the named frameworks: Scrum and Kanban (Agile), PRINCE2 (a structured, process-based method), the SDLC, and DevOps/DevSecOps. Agile work is organized in a Product backlog, estimated in story points, and forecast by Velocity.

1.2 Change, Risk & Issue Management

Uncontrolled change is Scope creep. The defense is integrated change control: every Change request is recorded in the Change control log, gets an Impact assessment, and is approved or rejected by the Change Control Board (CCB) before any work begins.^[1] Distinguish a product change (to the deliverable) from a project change (to how the work is done).

A Risk is an uncertain future event; an Issue is a problem happening now. Risks live in the Risk register; issues live in the issue log. For threats, the four responses are Avoid, Mitigate, Transfer, and Accept; opportunities mirror them with Exploit, Enhance, Share, and Accept.

Analyze risks qualitatively (rank by probability and impact) or quantitatively (model the numbers, e.g., Monte Carlo). Set aside a Contingency reserve for known risks. When an issue arises, prioritize it by severity, impact, and urgency, do root cause analysis, and escalate if it exceeds the team’s authority.

1.3 Schedule & Quality Management

Schedule development sequences activities using dependencies — the four types are finish-to-start (most common), start-to-start, finish-to-finish, and start-to-finish, and each is mandatory (hard) or discretionary (soft). The Critical path is the longest chain of dependent activities; its tasks have zero Float, so delaying any of them delays the whole project.^[1] You find it with the Critical Path Method (CPM).

Track progress against a Baseline using milestones; if approved change is large, you may rebaseline. On quality, know the difference between Verification vs. validation, and the metrics: SLA, KPIs/OKRs, Cost variance, and Schedule variance. Testing types — unit, smoke, regression, stress, performance, and user acceptance — verify the deliverable works.

1.4 Communication, Teams & Procurement

Communication is the project manager’s main job. Know the dimensions — synchronous vs. asynchronous, written vs. verbal, formal vs. informal, internal vs. external — and how to overcome barriers (language, time zones, culture). “Noise” is anything that distorts a message; active listening counters it.

Meetings have types and roles: a kickoff aligns the team, a stand-up surfaces blockers, a steering committee decides, and a retrospective captures improvement; use a facilitator, a scribe, timeboxing, and minutes with action items.^[1]

Teams sit in an org structure — functional (low PM authority), matrix (shared authority), or projectized (high PM authority) — and develop through the Tuckman model.

Know the roles cold: the Sponsor funds and champions the project, the project manager runs it, and the PMO sets standards; on Agile teams, a scrum master facilitates and a product owner prioritizes the backlog. For procurement, learn build vs. buy vs. lease vs. subscription, the request documents — RFI, RFP, RFQ, RFB — and contract types like fixed price, Time and materials (T&M), cost-plus, the Statement of work (SOW), MSA, and NDA.

Module 2 · Project Life Cycle Phases

One official domain, 30% of the exam. This is the journey every project takes from idea to close — and the artifacts and activities that belong to each phase. Knowing what happens when is the heart of this domain.

2.1 Discovery & Initiation

Before a project is approved, discovery justifies it: a business case, an ROI analysis, and a current-vs-future-state comparison, weighing capital (CapEx) against operating (OpEx) cost.

Once approved, initiation formally starts the project. Its central artifact is the Project charter, which authorizes the project and empowers the PM. The team also identifies and assesses stakeholders, builds a RACI chart, sets up communication channels, and holds the kickoff.^[1]

2.2 Planning

Planning turns the charter into an executable plan. The PM decomposes the work into a Work Breakdown Structure (WBS) (or, on Agile, a product backlog), writes the detailed scope statement, builds the schedule and budget, and drafts the risk, quality, and communication plans. These roll up into the Project management plan with its baselines and milestones. On Agile projects, planning also targets an MVP (Minimum Viable Product).^[1]

2.3 Execution

Execution is where the work gets done and the deliverables are produced. The PM manages vendors (rules of engagement, performance monitoring, approving deliverables), drives organizational change management (training, adoption, reinforcement), runs meetings, and reports progress against the baseline.

Conflict is inevitable — resolve it with collaboration where possible (the other approaches are smoothing, compromise, forcing, and avoiding). Between phases, a Phase gate review decides whether to proceed.^[1]

2.4 Closing

Closing makes the end official. The PM validates that deliverables meet requirements, obtains formal Project sign-off, closes contracts, removes access, and releases resources. The team holds a closure meeting, captures Lessons learned, reconciles the budget, and archives all documentation.^[1] Skipping closure is a common real-world failure — and a tested one.

Module 3 · Tools and Documentation

One official domain, 19% of the exam. This domain is about recognizing the right chart, log, register, or productivity tool for a given job — and reading what each one tells you.

3.1 Charts & Tracking Tools

Match the chart to the question. A Gantt chart shows the schedule as bars over a timeline; a PERT chart estimates duration from optimistic, most-likely, and pessimistic values; a Network diagram reveals dependencies and the critical path; a Burndown chart shows Agile work remaining; and a milestone chart shows key dates only.^[1]

For quality and analysis, learn the chart family: a Pareto chart ranks causes by frequency (the 80/20 rule), a histogram shows a distribution, a run chart shows a trend over time, a scatter diagram shows a relationship, a control chart shows whether a process is in control, and a Fishbone diagram finds root causes.

3.2 Logs, Registers & Productivity Tools

Documents are the project’s memory. The Risk register holds risks; the Issue log holds problems; the Change log holds change requests; and the Requirements Traceability Matrix (RTM) links each requirement to its deliverables and tests so nothing is missed. A project dashboard and status report communicate it all.^[1]

Module 4 · Basics of IT & Governance

One official domain, 18% of the exam. Because Project+ targets IT projects, you need the governance, security, compliance, and IT fundamentals that shape them — not deep technical skill, but the vocabulary and considerations a PM must account for.

4.1 ESG, Security & Compliance

ESG — Environmental, Social, and Governance — asks you to weigh a project’s broader impact: its effect on the environment, applicable regulations, the company’s mission and values, and brand value. Information security spans physical, operational, and digital controls — including MFA, least privilege, need-to-know, and Data classification by sensitivity. All of it serves the CIA triad: Confidentiality, Integrity, and Availability.^[1]

Compliance and privacy protect sensitive data: PII (personal data) and PHI (health data), governed by regulations that vary by country, state, and industry (for example GDPR, HIPAA, and PCI DSS). A project that touches this data must plan for confidentiality from the start.

4.2 IT Concepts & Operational Change Control

Know the cloud service models: IaaS (raw infrastructure), PaaS (a build/run platform), SaaS (ready-to-use apps), and the umbrella term XaaS. Recognize common business systems — ERP, CRM, CMS, and EDRMS — and basic infrastructure concepts like multitiered architecture, networking, and storage.^[1]

Finally, operational change control governs changes to live systems: schedule them in a Maintenance window, notify customers, run validation checks, and always have a Rollback plan. Software changes flow through requirements, risk assessment, testing, approval, and release — often automated with CI/CD and tested in a staging or beta environment before production.

How to Use This Project+ Study Guide

This guide is built to be worked, not just read. The most efficient path to a pass:

• Study by weight. Project Management Concepts (33%) and Project Life Cycle Phases (30%) are nearly two-thirds of the exam — master methodologies, change control, the critical path, and the phase artifacts first.
• Check off as you go. Use the Study Guide Contents to mark each section done; it raises your exam-readiness score.
• Take every checkpoint. The end-of-module quizzes show you exactly which domains need another pass.
• Drill the weak domain. Send your weak area into the flashcards and a practice test until the score climbs.
• Practice the PBQs. Performance-based questions reward applied skill — order the change-control steps, match charts to jobs, and walk the life cycle until it’s automatic.

Project+ Glossary

The high-yield Project+ terms in one place — hover any dotted term in the guide, or flip the whole deck here as a self-grading flashcard set.

Agile

An iterative, adaptive approach that delivers work in short increments (sprints) and welcomes changing requirements.

Baseline

The approved version of the scope, schedule, or cost plan against which performance is measured.

Burndown chart

A chart showing work remaining in a sprint or release over time against an ideal line.

Change Control Board (CCB)

The group that reviews change requests and approves, rejects, or defers them.

Change control log

A document recording every change request along with its review status and decision.

Change log

A record of all change requests and their decisions.

Change request

A formal proposal to alter a project's scope, schedule, cost, or quality.

CI/CD

Continuous Integration / Continuous Delivery — automating the build, test, and release of software.

CIA triad

The core information-security goals: Confidentiality, Integrity, and Availability.

Communication plan

A document defining what information is shared, with whom, how, and how often.

Contingency reserve

Time or budget set aside for identified (known) risks if they occur.

Cost variance

The difference between the budgeted and actual cost for the work performed; negative means over budget.

Critical path

The longest sequence of dependent activities; it determines the shortest project duration. Its tasks have zero float.

Critical Path Method (CPM)

A technique that calculates the critical path and each activity's float from a dependency network.

CRM

Customer Relationship Management — software for managing customer interactions and data.

Data classification

Labeling data by sensitivity (e.g., Public, Internal, Confidential) to apply the right controls.

DevOps

A culture and practice uniting development and operations to deliver software faster and more reliably.

ERP

Enterprise Resource Planning — integrated software managing core business processes.

ESG

Environmental, Social, and Governance — a framework for evaluating a project's broader impact.

Fishbone diagram

A cause-and-effect (Ishikawa) diagram used to identify the root causes of a problem.

Fixed-price contract

A contract for a set total price in which the vendor bears the cost risk.

Float

The amount of time an activity can be delayed without delaying the project; critical-path tasks have zero float.

Functional organization

An org structure where staff report to functional managers and the PM has limited authority.

Gantt chart

A horizontal bar chart showing tasks against a timeline, with durations, dependencies, and milestones.

IaaS

Infrastructure as a Service — cloud-provided compute, storage, and networking.

Impact assessment

An analysis of how a proposed change affects scope, schedule, cost, quality, resources, and risk.

Issue

A problem that has already occurred and needs resolution now; tracked in the issue log.

Issue log

A document tracking issues, their severity, owners, and resolution status.

Kanban

An Agile method that visualizes work on a board and limits work in progress to improve flow.

KPI

Key Performance Indicator — a measurable value showing how effectively an objective is being met.

Lessons learned

Documented insights captured (often at closure) so future projects can improve.

Maintenance window

A scheduled period for performing changes or maintenance with planned downtime.

Matrix organization

An org structure where staff report to both a functional manager and a project manager.

MFA

Multi-Factor Authentication — requiring two or more verification factors to grant access.

Milestone

A significant point or event in a project with zero duration, used to mark progress.

MVP (Minimum Viable Product)

The smallest usable version of a product that delivers value and enables feedback.

Network diagram

A diagram of activities and dependencies, used to find the critical path.

PaaS

Platform as a Service — a cloud environment to build, test, and deploy applications.

Pareto chart

A bar chart ordering causes by frequency, illustrating the 80/20 principle (the vital few).

PERT chart

Program Evaluation and Review Technique — estimates duration from optimistic, pessimistic, and most-likely values.

Phase gate review

A checkpoint between phases where stakeholders decide whether to proceed, hold, or cancel.

PHI

Protected Health Information — health-related data protected by regulations such as HIPAA.

PII

Personally Identifiable Information — data that can identify an individual, such as a name, address, or SSN.

PMO

Project Management Office — a group that standardizes and supports project management practices.

Portfolio

A collection of projects, programs, and operations managed as a group to achieve strategic objectives.

PRINCE2

PRojects IN Controlled Environments — a structured, process-based project management methodology.

Product backlog

A prioritized list of features, requirements, and work items for an Agile product.

Program

A group of related projects managed together to gain benefits not available from managing them individually.

Project

A temporary endeavor undertaken to create a unique product, service, or result; it has a defined start and finish and a specific purpose.

Project charter

The document created during initiation that formally authorizes the project and empowers the PM.

Project management plan

The integrated plan covering baselines, milestones, and how the project is executed and controlled.

Project sign-off

Formal acceptance by the customer or sponsor that the project is complete.

Projectized organization

An org structure built around projects, in which the PM has high authority over resources.

RACI chart

A responsibility matrix labeling each role Responsible, Accountable, Consulted, or Informed for a task.

Requirements Traceability Matrix (RTM)

A grid linking each requirement to its source, deliverables, and tests to ensure coverage.

RFI

Request for Information — gathers general information about vendors and their capabilities.

RFP

Request for Proposal — asks vendors to propose a complete solution, evaluated on best value.

RFQ

Request for Quotation — asks vendors for pricing on clearly defined goods or services.

Risk

An uncertain future event that may help or hurt the project; tracked in the risk register.

Risk register

The central document recording risks with their probability, impact, owner, response, and status.

Rollback plan

A documented procedure to restore a system to its prior working state if a change fails.

SaaS

Software as a Service — complete applications delivered over the internet.

Schedule variance

The difference between planned and actual progress; negative means behind schedule.

Scope

The total work required to deliver a product, service, or result with its specified features and functions.

Scope creep

The uncontrolled expansion of project scope without adjusting time, cost, or resources; prevented by change control.

Scrum

An Agile framework using fixed-length sprints, a product backlog, daily stand-ups, and defined roles.

SDLC

Software Development Life Cycle — the phased process for planning, building, testing, and deploying software.

SLA

Service Level Agreement — a contract defining the expected level of service and its performance metrics.

Sponsor

The person who champions and funds the project and holds ultimate authority over it.

Sprint

A short, fixed time-box (often 1–4 weeks) in which an Agile team delivers a working increment.

Stakeholder

Anyone affected by, or who can affect, the project.

Statement of work (SOW)

A document detailing the work, deliverables, and timeline a vendor will provide.

Story point

A relative unit estimating the effort of a backlog item, rather than estimating in hours.

Time and materials (T&M)

A contract paying for actual labor time and materials used; the buyer bears the cost risk.

Triple constraint

The balance of scope, time (schedule), and cost — with quality at the center; changing one forces a change in at least one other.

Tuckman model

The five stages of team development: Forming, Storming, Norming, Performing, and Adjourning.

Velocity

The amount of work an Agile team completes per sprint, used to forecast future capacity.

Verification vs. validation

Verification confirms the product was built to spec; validation confirms it meets the real need.

Waterfall

A predictive, sequential methodology where each phase completes before the next begins; best when scope is stable.

Work Breakdown Structure (WBS)

A hierarchical decomposition of total project scope into manageable deliverables and work packages.

Work package

The lowest level of the WBS — small enough to estimate cost and duration reliably.

XaaS

Anything as a Service — the umbrella term for cloud delivery models.

Project+ Study Guide FAQ

References

1. 1.CompTIA. “Project+ (PK0-005) Certification Exam Objectives.” comptia.org. ↑
2. 2.CompTIA. “CompTIA Project+ — Certification Overview.” comptia.org. ↑

Career Employer

Career Employer is the ultimate resource to help you get started working the job of your dreams. We cover topics from general career information, career searching, exam preparation with free study materials, career interviewing, and becoming successful in your career of choice.

Follow Us:

All Posts