CompTIA Project+ PK0-005 (V5) Exam Objectives
This page translates the CompTIA Project+ PK0-005 (V5) exam objectives into clear, practical language. You’ll see what each domain covers, realistic task themes, and a focused study plan that turns objectives into repeatable labs, PBQs, and job-ready skills. Test at a glance: up to 95 questions, 90 minutes, multiple-choice + performance-based, recommended 6–12 months project experience.
Last updated: November 9, 2025. Always verify against the official CompTIA blueprint before your exam.
TL;DR: Project+ validates hands-on fundamentals for planning, executing, and closing small-to-medium IT projects across both Agile and Waterfall contexts—plus tools, documentation, and IT governance basics. Domains and weights: 1) Project Management Concepts (33%), 2) Project Life Cycle Phases (30%), 3) Tools & Documentation (19%), 4) Basics of IT & Governance (18%).
Table of Contents
- What Is Covered on CompTIA Project+ PK0-005 (V5)?
- Objective-By-Objective Breakdown (with examples)
- Why Project+ for Early-Career PM/Ops Roles?
- Study Plan: How to Master the PK0-005 Objectives
- Free Checklist & Next Steps
- Frequently Asked Questions
What Is Covered on CompTIA Project+ PK0-005 (V5)?
Project+ proves you can manage the life cycle, coordinate stakeholders, establish communication, control changes, and keep artifacts current—while supporting larger initiatives inside IT environments. It explicitly includes Agile and Waterfall methods and scenario-style items.
Objective-By-Objective Breakdown (with examples)
1) Project Management Concepts (33%)
- Compare/contrast Agile vs. Waterfall and pick approaches based on tolerance for change, requirements clarity, and constraints (budget/schedule).
- Understand frameworks (Scrum, Kanban, SAFe, DevOps/DevSecOps, PRINCE2, SDLC), apply change control (request → impact → CCB decision → implement → validate), manage risk (qualitative/quantitative, negative vs. positive responses), handle issues (escalation, ownership, severity/urgency), build schedules (dependencies, critical path, buffers, story points), differentiate quality vs. performance management (KPIs/OKRs, UAT, regression/stress testing), drive communication plans (modalities, barriers, security/integrity/archiving), run effective meetings (agenda, roles, timeboxing, minutes), and manage team/resources.
2) Project Life Cycle Phases (30%)
- Initiation: define objectives, stakeholders, governance, high-level risks/constraints, kickoff prep.
- Planning: assess resources and procurement, train team, build comms plan and WBS/backlog, schedule with baselines/milestones, budget, QA plan, initial risk assessment, transition/release plan, and a complete project management plan.
- Execution/Control: manage work, vendors and deliverables, meetings/updates, tracking/reporting (risks, status, gaps), update budget/timeline, resolve conflict (smoothing/forcing/compromise/collaboration/avoiding), and coordinate phase-gate reviews.
- Closing: evaluate project, validate deliverables, close contracts, remove access, release resources, conduct closure meeting, archive artifacts, reconcile budget, capture lessons learned/feedback, and obtain sign-off.
3) Tools and Documentation (19%)
Use tracking charts (Gantt, PERT, network, milestone, org chart), logs (issue/defect/change), risk register/report, dashboards, knowledge bases, conferencing/surveys/calendaring, office tools (docs/sheets/presentations/diagramming), ticketing/case systems, and PM scheduling tools (cloud vs. on-prem; local installs).
4) 4) Basics of IT & Governance (18%)
Summarize IT basics (infrastructure, multi-tier, networking, storage, data warehouse, enterprise apps like ERP/CRM/EDRMS/CMS/financials; cloud models PaaS/IaaS/SaaS/XaaS). Apply operational change control (maintenance windows, notifications, rollback, validation), differences cloud vs. on-prem, CI/CD, staging vs. production, and understand privacy/compliance (PII/PHI, regional regs) that impact project plans and communications. The blueprint also lists acronyms you should recognize (e.g., CCB, CI/CD, ERP, CRM).
Why Project+ for Early-Career PM/Ops Roles?
Project+ shows you can run the fundamentals: plan, communicate, track, change-control, and close. It aligns with junior project manager, project coordinator, PMO associate, scrum team member, and IT operations roles where consistent communication and artifact hygiene matter.
Study Plan: How to Master the PK0-005 Objectives
- Build a one-page project charter Write goals, stakeholders, constraints, success criteria, risks, and approval path. Share it and get feedback.
- Create a living WBS/backlog and schedule
Model dependencies, identify the critical path, set milestones/buffers, and publish a cadence calendar. - Run a change-control simulation
Log a change, do an impact assessment, take it to a “CCB,” decide, implement, validate, and communicate the outcome. - Practice risk & issue management
Fill a risk register (probability/impact, response owner) and an issue log (severity/urgency, escalation). Review weekly. - Close properly
Draft a closure checklist: deliverable validation, financial reconciliation, access removal, archiving, sign-off, and lessons learned.
