CompTIA Project+ PK0-005 remains the current Project+ exam in CompTIA’s latest published objective document. It validates the ability to manage a project life cycle, coordinate small-to-medium IT projects, establish communications, manage resources and stakeholders, maintain project documentation, and support larger projects in an information-technology environment.
The current PK0-005 objectives list a maximum of 95 questions, multiple-choice and performance-based items, a 90-minute test, and 6–12 months of hands-on experience managing projects in an IT environment as the recommended background. The four domains are Project Management Concepts at 33%, Project Life Cycle Phases at 30%, Tools and Documentation at 19%, and Basics of IT and Governance at 18%.
Project Management Concepts is the largest domain at 33%
This domain covers what makes a project different from ongoing operations, common methodologies/frameworks, organizational structures, roles, constraints, change control, risk, issue management, quality, communication, meetings, resource concepts, budgeting, procurement and basic performance measures.
The exam is vendor-neutral and combines traditional and agile thinking rather than requiring allegiance to one methodology.
Methodology questions are about fit, not slogans
Waterfall-style delivery emphasizes planned sequential phases and controlled change, while agile approaches emphasize iterative delivery, prioritized backlogs, frequent feedback and adaptation. The objectives also name frameworks or practices such as Scrum, Kanban, DevOps, DevSecOps, PRINCE2, SAFe and SDLC.
An agile project-management foundation helps candidates compare iterative and predictive approaches without treating either as universally better.
Constraints and scope connect directly to change control
Scope, schedule, cost, quality, resources and risk interact. A stakeholder request can improve business value while increasing time, budget or complexity. Good project management identifies the impact, follows the change process and updates baselines or plans only after appropriate approval.
A scope and WBS perspective helps separate what the project must deliver from how the work is decomposed and controlled.
Risk and issue management are separate but related
Risk describes uncertain future events or conditions, while an issue has already occurred. The objectives expect candidates to identify, analyze, prioritize, assign owners, plan responses, track status and escalate appropriately.
A risk-versus-uncertainty model is useful because scenario questions often ask whether the project manager should mitigate a potential problem or manage an active issue.
Project Life Cycle Phases accounts for 30%
This domain covers discovery/concept, initiation, planning, execution, monitoring/control and closure activities. Candidates should understand deliverables, stakeholder approvals, business case, charter, requirements, schedule, budget, risk, communication, quality, procurement, status, acceptance and transition.
The project life cycle is not merely a list of phase names; each phase exists because different decisions and artifacts are required as uncertainty decreases and work progresses.
Planning creates the working baseline
Planning includes requirements, WBS, schedule, milestones, dependencies, estimates, resource assignments, budget, communications, risk, quality and procurement. The plan becomes the reference for measuring execution and controlling change.
Schedule concepts such as dependencies, critical path, float/slack and milestones help candidates understand why one delayed task may or may not delay the entire project.
Execution and monitoring happen together
Teams perform work while the project manager monitors progress, cost, scope, quality, issues, risks, communications and stakeholder expectations. Status reports and meetings should communicate decisions and exceptions rather than merely restate task lists.
A status-reporting discipline is especially important in IT projects where technical work, vendor dependencies and business readiness change at different speeds.
Tools and Documentation represents 19%
The objectives include project-management software, collaboration tools, charts and diagrams, meeting records, schedules, budgets, risk/issue/change logs, responsibility matrices, requirements traceability, status reports, lessons learned and other project artifacts.
Candidates should know what information an artifact contains and when it helps. A RACI answers responsibility questions; a risk register tracks threats/opportunities; a change log tracks approved/rejected changes; a Gantt-style view helps communicate schedule.
Basics of IT and Governance is 18%
This domain connects project management with IT environments: infrastructure/cloud concepts, application/software lifecycles, security/privacy/compliance, data handling, governance, change/release practices, operational transition and common IT dependencies.
Project+ is designed for IT professionals, so a project manager should recognize how a cloud migration, software release, infrastructure change or compliance requirement affects planning and stakeholder coordination even without performing the engineering work.
The current blueprint describes an IT project from idea to closure
Within the broader CompTIA certification path, Project+ sits between pure technical support and specialist project-management credentials. The exam measures practical coordination: define value, plan work, communicate, control risk/change, use appropriate artifacts, understand IT context and close/transition the result cleanly.
The current objectives also emphasize that projects can exist inside programs and portfolios. A project creates a unique result; a program coordinates related projects for combined benefit; a portfolio groups investments according to strategy. Candidates should understand the distinction because governance and prioritization can occur above the individual project.
Organizational structure affects authority. In a functional organization, functional managers can hold more control over resources; in projectized structures, the project manager may have greater authority; matrix structures share authority. A scenario about resource conflict often depends on this context.
Project roles should be differentiated clearly. A sponsor champions the project and provides senior-level support, the project manager coordinates delivery, the project team performs work, product or business owners can prioritize requirements, the PMO supports standards/governance, and stakeholders influence or are affected by outcomes.
Communication planning includes audience, purpose, frequency, format, channel, sensitivity, and escalation. A status email that works for technical staff may be poor communication for an executive steering group. Project+ rewards communication as a management control, not an administrative habit.
Meeting types can include kickoff, planning, stand-up, status, retrospective, lessons-learned, steering or change-control meetings. The meeting should have a clear purpose, appropriate participants, agenda, decisions and actions. Repeated meetings with no decision path can become project waste.
Cost management includes estimates, budget, reserves, actual spend, forecasts and basic performance measures. The objective is not advanced finance; candidates should understand how project managers detect variance and explain whether a cost problem comes from scope, schedule, resources or vendor performance.
Procurement includes identifying a need, selecting the right solicitation or contract approach, evaluating vendors, managing deliverables, tracking obligations and closing contracts. A procurement perspective helps because vendor work remains part of the project baseline even when an external company performs the task.
Quality should be connected to requirements and acceptance. Quality assurance improves processes; quality control examines outputs; acceptance confirms the customer or authorized stakeholder agrees that requirements are met. A deliverable can be defect-free yet still fail acceptance if it does not satisfy the agreed need.
The life cycle begins with discovery or concept work, where need, feasibility and high-level value are explored. Initiation establishes authorization and key stakeholders. Planning turns the approved objective into scope, schedule, resources, budget, risk, quality, communications and procurement plans.
Execution produces deliverables while monitoring/control compares actual progress against the plan. This includes status, risk/issue handling, change control, quality, resources and stakeholder management. Closure confirms acceptance, transition, administrative completion, lessons learned and release of resources.
Agile projects still require planning and governance, but planning is iterative. Product backlogs, iterations/sprints, daily stand-ups, reviews, retrospectives, velocity or burn charts can replace or supplement predictive artifacts. Project+ expects candidates to recognize the purpose of agile tools without needing Scrum-master specialization.
Tools and documentation also include decision logs, action logs, issue/risk registers, communication artifacts, architecture or process diagrams, and collaboration systems. The best artifact is the one that answers a project question clearly and remains current enough for decisions.
The IT/Governance domain includes infrastructure, cloud, applications, security, privacy, compliance and software-lifecycle context because an IT project often depends on technical environments or governance gates outside the project manager’s direct control. The manager coordinates specialists, dependencies and approvals rather than replacing them.
Operational transition is especially important in IT. A project can deliver software successfully and still fail if support teams lack documentation, monitoring, training, licenses, access, runbooks or ownership. Closing the project requires confirming the deliverable can be operated after the project team leaves.
The current objective document lists a maximum of 95 questions and 90 minutes, which creates significant pacing pressure when performance-based items appear. Preparation should include scenario interpretation, artifact selection and prioritization rather than pure term recall.
For current-scope review, use the published objective percentages—33/30/19/18—to allocate time. Concepts and Life Cycle make up 63% of the exam, but Tools/Documentation and IT/Governance together still represent more than a third and can be decisive for candidates with informal project experience.
Project constraints should be read as a system rather than a triangle with only scope, time and cost. Quality, resources, risk and stakeholder expectations also shape delivery. Changing one constraint can create pressure elsewhere, which is why impact analysis and explicit trade-off decisions are recurring Project+ skills.
CompTIA also places communication and documentation throughout the exam because IT projects often involve technical specialists who see only part of the delivery. The project manager creates shared context across engineers, business owners, vendors, security, operations and sponsors so local decisions do not undermine the overall objective.
Performance-based items can present artifacts or scenarios rather than simple definitions. Candidates may need to interpret a schedule, assign roles, order lifecycle steps, select the right document, or decide what the project manager should do next. Applied practice is therefore more valuable than memorizing acronym expansions alone.
The strongest current-scope review is to take one IT project you have seen and map every objective to a real decision, document or meeting. If a concept cannot be attached to an actual project moment, it probably needs another pass.