RoleMath Study Track for CompTIA Project+ (PK0-005)
A free study companion keyed to the officially published exam domains of CompTIA Project+ (PK0-005): what each domain covers in plain language, clearly labeled free resources, a guided lab outline for every domain, and interactive self-checks from our own question bank. CompTIA Project+ (PK0-005) exam objectives
A free, source-cited study companion built on CompTIA's published Project+ (PK0-005) exam objectives - for independent study only, not official training, not affiliated with or endorsed by CompTIA, and not a pass guarantee. Project+ is an entry-level certification with NO prerequisites that tests project process and documentation rather than technical implementation, making it a strong fit for career changers moving into IT project coordination from administrative, operations, education, healthcare, or retail backgrounds. Every lab here is a worksheet or template you complete with hypothetical practice data in free tools. Verify the current objectives on the official page before your exam.
A complete free CompTIA Project+ (PK0-005) program pinned to the currently published exam objectives, sequenced the way projects are learned - concepts first, then the life-cycle phases, then the tools and documents you produce, then the IT and governance frame around them - with every hands-on lab a RoleMath-owned worksheet or template you complete in free tools using only hypothetical, invented practice data, an integrated capstone that carries one hypothetical project end to end, and an explicit recheck of the official objectives and the current continuing-education renewal terms before any exam scheduling. Project+ is entry-level with NO prerequisites and tests project process and documentation rather than technical implementation, so it is a strong fit for career changers from administrative, operations, education, healthcare, or retail backgrounds moving into IT project coordination.
This draft exposes RoleMath’s authored sequence and evidence plan. The current labs are guided outlines, not yet a fully fixture-backed course, and objective-leaf coverage has not passed the gold-standard gate. Completion does not predict an exam result.
Modules
4
Labs
4
Concept checks
8
Resource mix
2 official / 5 community
Choose an outcome
Three routes through the same evidence
Choose provisionally. Change routes when the work tells you something new about fit, time, or readiness.
Certification-focused
Learners who want one current, dependency-ordered PK0-005 sequence across all four domains, with every worksheet completed in free tools on hypothetical data and a recheck of the official objectives and the current CE renewal terms before scheduling.
Completion emphasis: Complete every module, finish each domain worksheet with invented practice data, correct every missed check against its cited source, finish the integrated capstone that carries one hypothetical project through concepts, phases, documents, and governance end to end, and diff the current objectives and renewal terms before booking - never inferring a score from coverage.
Required phases: Project management concepts and vocabulary, Project life cycle phases and gates, Tools and documentation - the artifacts you produce, Basics of IT and governance, and the integrated capstone
Coordination skills first
Career changers from administrative, operations, education, healthcare, or retail roles who want reviewable evidence that they can frame a project, walk it through its phases, and produce a charter, WBS, risk register, and change-and-governance paperwork, whether or not they sit the exam soon.
Completion emphasis: Retain a labeled artifact per domain - a triple-constraint and stakeholder analysis, a phase-gate plan with a swimlane, a charter plus a three-level WBS plus a scored risk register, and a change request plus a governance checklist - all built on hypothetical data, plus the capstone project packet.
Required phases: Project management concepts and vocabulary, Project life cycle phases and gates, Tools and documentation - the artifacts you produce, Basics of IT and governance, and the integrated capstone
Career-fit sprint
Learners deciding whether IT project coordination - the concepts, life cycle, and documentation of running projects - is a direction worth deeper investment before committing to the full PK0-005 exam, especially those exploring a first move into tech from a non-technical background.
Completion emphasis: Complete the diagnostic, the concepts foundation, and the life-cycle phase with their worksheets on hypothetical data, then choose a next step or a full exam commitment rather than inferring job readiness or a pass from partial coverage.
Required phases: Project management concepts and vocabulary, Project life cycle phases and gates
Start safely
Prerequisite diagnostic
Confirm you are set up to study effectively; Project+ itself has NO prerequisites, so this diagnostic is about study readiness, not eligibility, and it is not a CompTIA requirement, a cost promise, or an exam prediction. Project+ is an entry-level, cross-industry certification that tests project process and documentation, not technical implementation.
Do you understand that Project+ has no prerequisites and that CompTIA's suggested 6-12 months of project-coordination experience is helpful context, not a requirement to sit the exam?
Ready when: Yes - you can start from zero project background and use this program to build the concepts, and you will not let the suggested experience discourage you.
If not yet: Read the exam facts in the Study Track and the official certification page to confirm there is no barrier to entry, then begin with the concepts foundation.
Can you use a plain-text editor and a free spreadsheet (Google Sheets or LibreOffice Calc), and open draw.io (https://app.diagrams.net/) in a browser with no account, since every lab is a worksheet or template in these free tools?
Ready when: Yes - you have a text editor and can reach a free spreadsheet and draw.io, all at no cost and with no paid software.
If not yet: Install a free editor and use the browser-based free spreadsheet and draw.io; no lab needs paid software, an account, or a payment.
Do you understand that every worksheet uses only HYPOTHETICAL, invented practice data and must never contain a real employer project, client, budget, person, or any real compliance record?
Ready when: Yes - you will invent a small practice project (or use each worksheet's scenario) and keep all names, figures, and data made up.
If not yet: Re-read each lab's safety note; if you are tempted to use a real project, invent a fictional one instead - the learning is identical and your (and others') data stays private.
Are you comfortable reading documentation and writing short structured explanations in your own words, since Project+ rewards describing and placing concepts rather than technical configuration?
Ready when: Yes, or you will use the worked examples in each worksheet and the free foundations courses to build the vocabulary as you go.
If not yet: Start with the PMI Kickoff and Google Foundations free courses to build project vocabulary before the concepts worksheet.
Have you chosen a pace whose weekly hours you can realistically protect across roughly 40 to 50 total hours on the free path?
Ready when: Yes, with a pace selected and the objective recheck, the domain worksheets, and the capstone left uncompressed.
If not yet: Pick the steady pace if project work is new to you and reserve the intensive pace if you already coordinate work; never compress the capstone or the objectives-and-renewal recheck to save time.
Plan, then adapt
Pace options
Steady
8 weeks 5-6 hours/week
A planning estimate of roughly 40-50 hours for a learner new to project work: one domain block at a time, each domain's worksheet completed on hypothetical data, plus the integrated capstone and a recheck of the official objectives and the current CE renewal terms before scheduling.
Standard
6 weeks 7-8 hours/week
A planning estimate for learners with some exposure to organizing work that pairs the CompTIA-cited domain study with one retained artifact per domain and preserves the integrated capstone, the missed-check corrections, and an objectives-and-renewal-diff block before any exam logistics.
Intensive
4 weeks 10-12 hours/week
Roughly 40 focused hours for a learner who already coordinates work day to day; do not compress the documentation labs (charter, WBS, risk register), the change-and-governance worksheet, or the capstone's end-to-end consistency review.
Evidence-gated sequence
Program roadmap
1
Project management concepts and vocabulary
Build the vocabulary and mental models the whole exam assumes (Domain 1, 33%): the triple constraint, project versus program versus portfolio, organizational structures, project roles and stakeholder analysis, and the predictive-versus-Agile spectrum - turned into a triple-constraint analysis, a stakeholder register, and a RAID entry for a hypothetical project.
Complete the Domain 1 worksheet: a triple-constraint table showing scope, time, and cost trading off with quality at stake, a five-row stakeholder register with interest and influence ratings and a communication approach, and one RAID entry (risk, assumption, issue, dependency), all for a hypothetical project you invented.
Be able to distinguish a project from a program and a portfolio, name the three organizational structures and how each changes a coordinator's authority, and describe when predictive versus Agile delivery fits.
Complete the study-readiness, free-tools, hypothetical-data, reading-and-writing, and study-time diagnostics and choose a pace you can protect.
Attempt every authored Project management concepts check and correct each miss against its cited source before moving to the life-cycle phases.
2
Project life cycle phases and gates
Walk a project through its phases (Domain 2, 30%): initiation, planning, execution, monitoring and controlling, and closing, with the go/no-go gate decisions between them and how an Agile life cycle reframes the flow - turned into a phase-gate plan, a swimlane diagram, and a predictive-versus-Agile comparison for a hypothetical rollout.
Complete the Domain 2 worksheet: the five phases mapped to activities, deliverables, gate criteria, and approvers, an exported draw.io swimlane across Sponsor / Coordinator / Team / Vendor, and a predictive-versus-Agile comparison, all for a hypothetical rollout.
Be able to place an activity in the right phase, explain why monitoring and controlling overlaps execution, and say what a phase gate protects and who approves it.
Retain the phase-gate plan and swimlane as a labeled artifact built on hypothetical data.
Attempt every authored Project life cycle phases check and correct each miss against its cited source before moving to tools and documentation.
3
Tools and documentation - the artifacts you produce
Produce the core project documents (Domain 3, 19%): the charter that authorizes the project, the work breakdown structure that decomposes scope under the 100% rule, the schedule and its critical path, the risk register scored by probability times impact, and the communication and documentation set - turned into a charter, a three-level WBS, and a scored risk register for a hypothetical project.
Complete the Domain 3 worksheet: a complete one-page charter, a three-level WBS of 15-20 nodes obeying the 100% rule, and a six-row risk register with probability-times-impact scores, response strategies, and owners, coherent with each other for a hypothetical project.
Be able to explain what belongs in a charter versus detailed planning, how the WBS feeds the schedule and cost estimate, and why probability-times-impact scoring directs limited attention to the risks that matter most.
Retain the charter, WBS, and risk register as a labeled artifact set built on hypothetical data.
Attempt every authored Tools and documentation check and correct each miss against its cited source before moving to IT and governance.
4
Basics of IT and governance, and the integrated capstone
Frame project work inside the IT and organizational controls (Domain 4, 18%): basic IT literacy, integrated change control against scope creep, compliance and security considerations, and the project-governance-versus-IT-governance distinction - turned into a change-request form, a change log, and a governance checklist - then integrate all four domains in the capstone by carrying one hypothetical project end to end.
Complete the Domain 4 worksheet: a change-request form with a four-constraint impact analysis and a decision, a two-row change log, and a six-area IT-governance and compliance checklist (data privacy, regulatory, security review, access control, vendor risk, audit trail) with actions, all on hypothetical data.
Be able to explain how integrated change control defends against scope creep and how a project sits inside both project governance and IT governance at once.
Complete the integrated capstone: carry one hypothetical project through concepts, the life cycle, the charter/WBS/risk register, and change-control/governance end to end as one coherent packet.
Attempt every authored Basics of IT and governance check, correct each miss against its cited source, then diff the current CompTIA objectives and CE renewal terms and record a continue, practice, defer, or exam-scheduling next decision.
Before a lab
Environment, access, and safety
Required and optional setup
Required
A browser plus a plain-text editor and a free spreadsheet (Google Sheets or LibreOffice Calc) for reading the CompTIA-cited objectives and for filling in each domain's worksheet or template with hypothetical practice data
draw.io (https://app.diagrams.net/) in the browser for the Domain 2 swimlane diagram - no account and no cost, and replaceable by a text outline if a diagram is impractical
A habit of using ONLY hypothetical, invented practice data in every worksheet - never a real employer project, client, budget, person, or any real compliance record
A simple artifact folder to retain, per domain, the completed worksheet or template as reviewable evidence built on hypothetical data
Optional
The free PMI Kickoff course and templates and the free-to-audit Google 'Foundations of Project Management' and Infosec CompTIA Project+ courses as alternate explanations after the official CompTIA objectives (verify the free label and audit option before relying on them)
The free OpenExamPrep Project+ practice bank (208+ questions, no signup) to check familiarity with the question style - community-produced, so cross-check answers against the official objectives
A free Google account only if you choose Google Sheets or Looker-style tools; no lab requires it, since a local spreadsheet or text editor works offline
Accounts and accessibility routes
Accounts
The core path requires no account and no payment: every worksheet and template is completed in a local text editor or a free spreadsheet, and draw.io runs in the browser with no sign-in.
Some optional resources may require a free account or a free audit enrollment (Coursera audit, PMI Kickoff); verify the free label before relying on them, since paid tiers and certificates exist.
No lab requires a paid subscription, a card, or CompTIA's paid CertMaster products; if an optional resource ever moves a needed exercise behind a paywall, the free worksheet route already covers the objective.
Equivalent routes
Every lab is a text or spreadsheet worksheet, so the whole program is keyboard-operable and screen-reader friendly; the fixtures are plain Markdown with labeled headings, fields, and tables.
The one diagram step (the Domain 2 swimlane) has a documented text-outline alternative that reaches the same outcome and evidence without any pointer-only interaction.
In low-bandwidth conditions, complete every worksheet in a local file; only the objectives page and optional courses need the network, and they are lightweight text pages.
Safety baseline
Use ONLY hypothetical, invented practice data in every worksheet and template - never a real employer project, client, budget, person's name, or any real organization's privacy, regulatory, security, access-control, vendor, or audit data.
No lab touches a live system, requires a paid tool, or needs a card; if a worksheet ever tempts you to paste real data, invent a fictional equivalent instead - the learning is identical.
Treat the governance and compliance worksheet as awareness practice, not legal or compliance advice; it exercises recognizing which controls apply, not implementing them on any real system.
Confirm the current CompTIA Project+ objectives and the continuing-education renewal terms (3-year CE, 30 CEUs, CE fee, effective 2025-10-01 for new earners) before relying on any fact or scheduling the exam.
There is nothing to clean up: keep or delete your practice worksheets as you wish; none of them persist anywhere beyond local files you own.
Show your work
Module evidence and missed-check protocol
Module exit evidence
A labeled artifact per domain tied to its module: a triple-constraint and stakeholder analysis with a RAID entry; a phase-gate plan with a swimlane and a predictive-versus-Agile comparison; a charter plus a three-level WBS plus a scored risk register; or a change-request form plus a change log plus a governance and compliance checklist - all built on hypothetical data.
A plain-language explanation of the concept, why the artifact is structured the way it is, and how it connects to the other domains (for example how the WBS feeds the schedule, or how a change request protects the triple constraint).
All authored checks for the domain attempted, with each miss corrected against its cited source and re-applied to a fresh hypothetical scenario.
After a missed check
Identify whether the question tests project management concepts, the project life cycle phases, tools and documentation, or basics of IT and governance before reviewing the answer.
Write why the distractor was plausible and which concept - a triple-constraint trade-off, a phase or gate, a specific document, or a change-control or governance step - distinguishes the correct answer.
Change one hypothetical detail - the scope, the phase, the organizational structure, or the constraint under pressure - and explain whether the correct answer changes.
Completing this policy demonstrates current-objectives Project+ coverage and hands-on practice producing project artifacts on hypothetical data inside RoleMath; it does not predict an exam score, confer real project-management experience or authority, or serve as a RoleMath credential. Project+ earned on or after 2025-10-01 is a 3-year continuing-education certification, not a lifetime credential.
Integrated practice
Integrated hypothetical project carried end to end: concepts, phases, documents, and governance
Carry ONE hypothetical project through all four Project+ domains as a single coherent packet - frame it with the concepts, walk it through the life-cycle phases and gates, produce its charter, WBS, and risk register, and run a change through integrated change control against a governance and compliance check - integrating everything into one reviewable evidence packet built entirely on invented data.
Workflow
Invent a single hypothetical project (for example a small nonprofit's website redesign or a community tool rollout) and frame it with the Domain 1 concepts: a triple-constraint analysis, a five-row stakeholder register with interest and influence, and a RAID entry, all with invented data.
Map the project through the five life-cycle phases with go/no-go gate criteria and approvers, and draw a swimlane (or text outline) of the flow across Sponsor, Coordinator, Team, and Vendor, noting where a predictive and an Agile approach would differ.
Produce the scope documents: a one-page charter that authorizes the project and a three-level WBS of 15-20 nodes obeying the 100% rule, kept consistent with the charter's stated scope.
Produce the risk documentation: a six-row risk register scored by probability times impact with response strategies and owners, tying each high-scoring risk back to a specific WBS work package.
Introduce one scope change (for example adding a feature mid-project), run it through a change-request form with an impact analysis across scope, time, cost, and quality, record it in a change log, and decide it via an invented approver.
Complete the IT-governance and compliance checklist for the project (data privacy, regulatory, security review, access control, vendor risk, audit trail) and write how the project sits inside both project governance and IT governance at once.
Assemble the packet so the concepts, phases, documents, change, and governance all describe the SAME one project consistently - the stakeholder register, the phases, the WBS, the risk register, and the change all reference each other coherently.
Diff the current CompTIA Project+ objectives and the continuing-education renewal terms, flag any uncovered topic as an explicit gap, and record a continue, practice, defer, or exam-scheduling next decision rather than inferring a pass from coverage.
Retained artifacts
A concepts packet for one hypothetical project: a triple-constraint analysis, a five-row stakeholder register, and a RAID entry
A life-cycle packet: a five-phase plan with gate criteria and approvers plus a swimlane (or text outline) and a predictive-versus-Agile note
A documentation packet: a one-page charter, a three-level 15-20-node WBS obeying the 100% rule, and a six-row scored risk register
A change-and-governance packet: a change-request form with a four-constraint impact analysis, a change log, and a six-area IT-governance and compliance checklist
A one-page consistency note showing the four packets describe the same project, plus an objectives-and-renewal diff and a next-step decision
Review checklist
The concepts, phases, documents, change, and governance all describe ONE consistent hypothetical project, with the stakeholder register, phases, WBS, risk register, and change referencing each other coherently.
Every value in the packet is hypothetical and invented - no real employer project, client, budget, person, or real compliance data appears anywhere.
The charter reads as high-level authorization, the WBS has three levels and 15-20 nodes obeying the 100% rule, and the risk register scores risks by probability times impact with response strategies and owners.
The change request analyzes impact across scope, time, cost, and quality and is recorded in the change log with a decision, demonstrating integrated change control against scope creep.
The governance checklist marks all six areas with actions and the reflection distinguishes project governance from IT governance.
The current CompTIA Project+ objectives and the continuing-education renewal terms were rechecked, and any changed objective or renewal rule invalidates the affected mapping or claim.
All four current PK0-005 domains map to at least one artifact; uncovered topics remain explicit gaps rather than implied completion.
The packet does not claim exam success, official CompTIA approval or training beyond linked sources, real project-management experience, a lifetime credential for new earners, or a RoleMath credential.
Safety boundary: Build the entire capstone on ONE invented, hypothetical project - never a real employer project, client, budget, person, or any real organization's privacy, regulatory, security, access-control, vendor, or audit data. No step touches a live system, requires a paid tool, or needs a card; the governance work is awareness practice, not legal or compliance advice. Confirm the current objectives and the 3-year CE renewal terms before scheduling; there is nothing to clean up beyond local files you own.
Finish honestly
Completion, portfolio, and maintenance
Completion evidence
All four current PK0-005 domain modules have been covered and checked against the official CompTIA Project+ objectives, including a recheck of the current objectives and the continuing-education renewal terms before any exam scheduling.
Every domain worksheet has been completed on hypothetical, invented data and its artifact retained.
Every authored knowledge check has been attempted and each miss has a cited correction plus a fresh hypothetical scenario.
The CompTIA objectives and the free foundations, practice, and diagram resources have been used within their current free-access terms, with any community resource reconciled to the official objectives.
The integrated capstone passes its consistency, hypothetical-data, document-quality, change-control, governance, currency, and four-domain coverage review.
The learner has recorded remaining objective gaps and a next decision; completion is not represented as an exam result, a credential, real project-management experience, a lifetime credential for new earners, or job readiness.
Portfolio candidates
A concepts artifact: a triple-constraint analysis, a stakeholder register, and a RAID entry for a hypothetical project
A life-cycle artifact: a five-phase plan with gates and a swimlane or text outline
A documentation artifact set: a one-page charter, a three-level WBS, and a scored risk register
A change-and-governance artifact: a change-request form with a four-constraint impact analysis, a change log, and a governance and compliance checklist
The integrated capstone packet with a consistency note and an objectives-and-renewal diff
Present the packet as self-directed Project+ study - hands-on practice producing project artifacts on hypothetical data. Do not call it real project-management experience, CompTIA approval, a lifetime credential for post-2025-10-01 earners, or a RoleMath credential, and never publish real projects, organizations, or compliance data.
Freshness controls
Objective source checked 2026-07-11. Recheck objectives every 30 days and resources every 90 days.
Stop and re-verify when
CompTIA changes the Project+ objectives, domain set, weights, exam code, format, passing score, languages, prerequisites, or fee context.
CompTIA changes the Project+ lifecycle or renewal terms (for example the 3-year continuing-education model, the 30-CEU requirement, the CE fee, or the 2025-10-01 effective date, or the treatment of pre-2025-10-01 Good-for-Life earners).
A free resource (PMI Kickoff, Google Foundations audit, Infosec Project+ audit, OpenExamPrep) or the draw.io tool changes URL, access, its free tier, or its terms.
A worksheet or template can no longer be completed in the free tools on hypothetical data, or its hypothetical-data-only and no-live-system guarantees no longer hold.
A project-management-concepts, life-cycle, documentation, or IT-and-governance concept materially changes in the objectives.
Any module, worksheet, check, phase, capstone step, account instruction, safety guardrail, or objectives-and-renewal diff fails technical, source, entry-level, safety, privacy, accessibility, currency, or claims review.
For Project+ we recommend studying the four domains in their published order, because that order builds the vocabulary and then applies it. CompTIA weights the domains as Project management concepts 33%, Project life cycle phases 30%, Tools and documentation 19%, and Basics of IT and governance 18%, so the weights descend from the heaviest to the lightest and the learning order happens to descend with them. We open with Project management concepts (Domain 1, 33%) because it is both the heaviest domain and the conceptual foundation: the triple constraint, the difference between a project, a program, and a portfolio, organizational structures, project roles, and the predictive-versus-Agile spectrum are the words every later domain reuses, so time here pays off everywhere. Project life cycle phases (Domain 2, 30%) comes next because once you know the vocabulary you can walk a project through its phases - initiation, planning, execution, monitoring and controlling, and closing - with the gate decisions between them, plus how an Agile life cycle reframes that flow. Tools and documentation (Domain 3, 19%) then makes the phases concrete: the charter, the work breakdown structure, the schedule, the risk register, and the communication plan are the artifacts you actually produce, and they only make sense once you know which phase each belongs to. We close with Basics of IT and governance (Domain 4, 18%), the lightest domain, because it frames project work inside the IT and organizational controls - change control, compliance, security, and governance - that a coordinator must respect, and it lands most clearly once the project mechanics from the first three domains are in place. This is sequencing advice based on the published weights and how the topics build on each other, not a claim about the science of learning; if a different order fits how you think, use it, but Domain 1's vocabulary is worth front-loading either way.
Study this first. At 33% it is the heaviest domain and the conceptual foundation of the whole exam: the triple constraint, project versus program versus portfolio, organizational structures, project roles, and the predictive-versus-Agile spectrum are the vocabulary every later domain reuses.
This is the 'learn the language of projects' domain, and CompTIA weights it at 33% - the largest slice of Project+. It is where you build the vocabulary and mental models that the rest of the exam assumes, so it is both the heaviest domain and the one we study first. For a career changer with no formal project background, this is the friendliest place to start, because it is about ideas and definitions - what a project is, who does what, and how the core trade-offs work - rather than any technical implementation. Nail this domain and the later material turns from memorization into recognition.
The triple constraint is the heart of the domain, so internalize it early. Every project balances scope (the work to be done), time (the schedule), and cost (the budget), and these three are interdependent: change one and at least one other must flex, or quality suffers - which is why the model is often drawn as a triangle with quality in the middle. The practical skill the exam rewards is reasoning about the trade-off: if a sponsor adds features (scope) without moving the deadline or the budget, something has to give. A coordinator's daily job is protecting this balance and making the trade-offs visible rather than silently absorbing them.
The project-program-portfolio distinction is a classic exam trap worth getting crisp. A project is a temporary effort that produces a unique result and has a definite start and end. A program is a group of related projects managed together to gain benefits that would not come from running them separately. A portfolio is the whole collection of projects and programs an organization runs to meet strategic goals, chosen and prioritized for business value. The through-line is scale and intent: projects deliver outputs, programs coordinate related projects for shared benefit, and portfolios align everything to strategy. When a question describes managing several related efforts for a combined benefit, 'program' is the answer, not 'project'.
Organizational structures shape how much authority a project coordinator actually has, and the exam expects you to recognize the three classic types. In a functional organization, staff report to department managers and the coordinator has little formal authority. In a projectized organization, teams are organized around projects and the project manager has strong authority. A matrix organization sits between them - weak, balanced, or strong - sharing authority between functional managers and the project manager. The examinable insight is that your influence, your access to resources, and even who owns your team members change with the structure, so a coordinator reads the structure before assuming they can direct work.
Roles and the predictive-versus-Agile spectrum round out the domain. Key roles recur throughout: the sponsor (who authorizes and funds the project and champions it), the project manager or coordinator (who plans and drives the work), the team (who do the work), and stakeholders (anyone affected by or interested in the outcome), whom you analyze by interest and influence. Alongside roles, the exam contrasts predictive (plan-driven, phase-gated, 'waterfall') delivery - where scope is defined up front and change is controlled - with Agile delivery - iterative, adaptive, delivering working increments and welcoming change - plus hybrid approaches that blend the two. You are expected to describe when each fits, not to run a specific framework.
Study this domain by turning the concepts into artifacts you built yourself, because that is how the vocabulary sticks. The lab below uses a triple-constraint and stakeholder worksheet: for a hypothetical nonprofit member-portal project you invent, you fill in a triple-constraint table (what flexes if each of scope, time, and cost changes), build a five-row stakeholder register rating interest and influence, and write one RAID entry (a risk, an assumption, an issue, and a dependency) - all in free tools with made-up data. As always, read the official Project+ objectives for CompTIA's authoritative topic list; this explanation paraphrases its scope in our own words rather than reproducing it.
Learn it free
Official · Official exam objectives
CompTIA Project+ (PK0-005) exam objectivesThe exam's own topic list for this domain - read its project-management-concepts section directly rather than relying on any summary, including ours. (captured 2026-07-11)
Official · Free official foundations course (PMI)
PMI Kickoff - free 45-minute project management basicsA free, official Project Management Institute mini-course and templates covering the core concepts and life-cycle vocabulary this domain builds on; verify the free label on the page before relying on it. (captured 2026-07-11)
Coursera: Foundations of Project Management by Google (free audit)A deeper foundations course on project roles, the triple constraint, and organizational context; free to audit (the certificate is paid). Verify the audit option before relying on it. (captured 2026-07-11)
Projectplus Concepts Worksheet Lab
Build a triple-constraint analysis for a hypothetical project showing how scope, time, and cost trade off Produce a five-row stakeholder register with interest/influence ratings and one RAID entry
Free tools
Any operating system with a text editor or a free spreadsheet
A web browser to read the official CompTIA Project+ objectives
Steps
Open the triple-constraint-stakeholder-register.md worksheet, read its top note that all data is hypothetical, and pick a small hypothetical project (or use the nonprofit member-portal scenario).
Fill in Part A (the triple-constraint table: what scope, time, and cost mean and what flexes if each changes) and Part B (the five-row stakeholder register with interest, influence, and a communication approach each).
Fill in Part C (one RAID entry: a risk, an assumption, an issue, and a dependency) and write the reflection on how the triple constraint and stakeholder register would change a decision if online payments were added, then save the worksheet.
What you should see
Confirm the worksheet has a triple-constraint table showing scope/time/cost trade-offs, a five-row stakeholder register with interest and influence ratings, one RAID entry covering all four RAID types, and a reflection - all with hypothetical data.
Practice evidence maps to exam_domain_comptia_project_plus_pk0_005_01
Stay safe & legal: This lab is filling in a local worksheet with invented data only; it touches no live system, needs no account and no payment, and creates, changes, or deletes nothing anywhere. Account required: no; payment required: no; maximum designed cost: $0.
Check yourself
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 2 of 4 · domain 2 · 30% of the exam
Project life cycle phases
Study this second, after the concepts. At 30% it is the second-heaviest domain, and it walks a project through its phases - initiation, planning, execution, monitoring and controlling, and closing - with the gate decisions between them, plus how an Agile life cycle reframes that flow.
This is the 'walk a project from start to finish' domain, and CompTIA weights it at 30% - the second-largest slice of Project+. Where Domain 1 gave you the vocabulary, this domain gives you the timeline: how a project moves through recognizable phases, what happens in each, and how you decide whether it is ready to move on. It is a natural second study because the phases are the skeleton that the tools and documents in Domain 3 hang on. For a career changer, this domain is very learnable because it mirrors common sense - you define, then plan, then do, then check, then wrap up - dressed in project vocabulary.
The five predictive phases are the core, so learn them cleanly. Initiation is where the need is identified, a sponsor is named, and a high-level charter authorizes the project. Planning is where the detailed roadmap is built - scope, schedule, budget, resources, risks, and communication. Execution is where the team does the work and produces the deliverables. Monitoring and controlling runs alongside execution rather than strictly after it: it tracks progress against the plan, manages changes, and keeps scope, schedule, and cost in bounds. Closing formally finishes the project - final acceptance, lessons learned, releasing resources, and documenting the result. The exam expects you to place an activity in the right phase and to know why monitoring and controlling overlaps execution.
Phase gates are the decision points that make a life cycle disciplined, and they are examinable. Between phases, a gate (sometimes called a stage gate or a kill point) is a go/no-go review: has the phase produced what it should, is the business case still valid, should the project continue, change, or stop? A gate has criteria that must be satisfied and an approver with the authority to decide. The professional insight the exam rewards is that a gate protects the organization from pouring money into a project that no longer makes sense - it is cheaper to stop at a gate than to discover the problem at the end. Recognizing what belongs at a gate, and who signs off, is a recurring skill.
The planning phase deserves extra attention because it is where most examinable artifacts originate. From planning come the scope definition, the work breakdown structure, the schedule, the budget, the risk register, and the communication plan - the documents Domain 3 then details. A recurring theme is that time spent planning reduces churn later: a well-defined scope prevents scope creep, an honest schedule prevents crises, and an early risk register prevents surprises. The exam expects you to connect a planning activity to the phase it belongs to and to the document it produces, so keep the phase-to-artifact links straight as you study.
The Agile life cycle reframes the same journey, and the exam contrasts it with the predictive flow. Instead of moving once through five big phases, an Agile life cycle delivers value in short, repeating iterations (sprints), each producing a working increment, with the plan adapted as you learn. Requirements live in a prioritized backlog rather than a fixed up-front specification; change is welcomed rather than tightly controlled; and roles, ceremonies, and cadence differ from predictive delivery. Hybrid life cycles blend the two - for example, planning predictively at a high level but executing iteratively. You are expected to describe how an Agile life cycle handles requirements, change, and delivery differently, not to run a specific framework.
Study this domain by mapping a project's phases and gates yourself and drawing how the work flows, because seeing the life cycle cements it. The lab below uses a phase-gate plan worksheet for a hypothetical library ticketing-tool rollout: you fill in the five phases with their activities, deliverables, gate criteria, and approvers, build a draw.io swimlane diagram across Sponsor / Coordinator / Team / Vendor, and write a short predictive-versus-Agile comparison - all in free tools with invented data. As always, read the official Project+ objectives for CompTIA's authoritative topic list; this explanation paraphrases its scope in our own words rather than reproducing it.
Learn it free
Official · Official exam objectives
CompTIA Project+ (PK0-005) exam objectivesThe authoritative topic list for this domain's life-cycle-phases coverage - read it directly rather than relying on any summary, including ours. (captured 2026-07-11)
Coursera: CompTIA Project+ by Infosec (free audit)A roughly five-hour, four-module course aligned to the PK0-005 objectives, useful for the life-cycle and process material; free to audit (the certificate is paid). Verify the audit option before relying on it. (captured 2026-07-11)
Projectplus Lifecycle Worksheet Lab
Map the five predictive life-cycle phases to activities, deliverables, gate criteria, and approvers for a hypothetical project Build a swimlane diagram of the flow and contrast the predictive life cycle with an Agile one
Free tools
Any operating system with a text editor
A web browser for draw.io and to read the official objectives
Steps
Open the phase-gate-plan.md worksheet, read its top note that all data is hypothetical, and fill in Part A: the five phases with activities, deliverable, gate criteria, and approver each, plus the note on why monitoring and controlling overlaps execution.
Open https://app.diagrams.net/ with no sign-in, create four swimlanes (Sponsor, Coordinator, Team, Vendor), place 6-10 boxes showing the rollout flowing across the phases in the owning lane, export the diagram, and describe it in the worksheet.
Fill in Part C: write the predictive-versus-Agile comparison (requirements, change, when working software appears) and a one-sentence recommendation for the hypothetical library, then save the worksheet and diagram.
What you should see
Confirm the worksheet maps all five phases to activities, deliverables, gate criteria, and approvers, includes an exported swimlane diagram with four lanes, and contrasts the predictive and Agile life cycles across requirements, change, and delivery.
Practice evidence maps to exam_domain_comptia_project_plus_pk0_005_02
Stay safe & legal: This lab is filling in a local worksheet and building a no-account browser diagram with invented data only; it touches no live system, needs no paid software or payment, and creates, changes, or deletes nothing on any external system. Account required: no; payment required: no; maximum designed cost: $0.
Check yourself
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 3 of 4 · domain 3 · 19% of the exam
Tools and documentation
Study this third, after the phases. At 19% it is the third-weighted domain, and it makes the phases concrete: the charter, the work breakdown structure, the schedule, the risk register, and the communication plan are the artifacts you actually produce, each tied to the phase it belongs to.
This is the 'produce the artifacts that run the project' domain, and CompTIA weights it at 19%. Where Domain 2 gave you the phases, this domain gives you the documents and tools that make each phase real - the charter that authorizes the project, the work breakdown structure that decomposes the scope, the schedule that sequences the work, the risk register that tracks threats, and the communication plan that keeps stakeholders informed. Its official name is 'Tools and documentation' - note that it is not called 'Tools and communication,' though communication artifacts live inside it. Studying it after the life cycle works because each artifact belongs to a specific phase you already understand.
The project charter is where the domain starts, because it is where a project formally begins. The charter is a short, high-level document - typically produced in initiation - that authorizes the project, names the sponsor and coordinator, states the business need and objectives, sketches the high-level scope, milestones, budget, and risks, and gives the coordinator authority to use organizational resources. The examinable insight is that the charter is authorization, not a detailed plan: it is deliberately high-level, and its value is that it makes the project official and gives the coordinator a mandate. Recognizing what belongs in a charter (and what belongs later in detailed planning) is a recurring skill.
The work breakdown structure (WBS) is the backbone of scope, and the exam expects you to understand it. A WBS decomposes the total project scope into progressively smaller, deliverable-oriented pieces, usually shown as a hierarchy: the project at the top, major deliverables or phases beneath, and work packages at the lowest level - small enough to estimate and assign. Two ideas matter: the 100% rule (the WBS should capture 100% of the scope, no more and no less) and the work package as the estimating and assignment unit. The WBS feeds nearly everything downstream - the schedule, the cost estimate, and resource assignments all build on it - so a solid WBS is what keeps scope honest and prevents scope creep.
Scheduling and risk documentation are the next artifacts, and each has examinable structure. From the WBS you build a schedule by estimating durations, sequencing activities, and finding the critical path (the longest chain of dependent activities that sets the shortest possible finish); Gantt charts and network diagrams are the common tools. The risk register logs identified risks with a probability and an impact, a score (often probability times impact) to prioritize them, a response strategy (avoid, mitigate, transfer, or accept for threats), and an owner. The recurring skill the exam rewards is turning a scattered set of concerns into a scored, prioritized, owned list - so limited attention goes to the risks that matter most, not to every worry equally.
Communication and the wider documentation set close the domain. A communication plan defines who needs what information, how often, in what format, and through which channel - because a large share of project failures trace back to poor communication, this artifact is more important than it looks. Around it sit other documents the exam references: the stakeholder register, status reports, meeting agendas and minutes, issue and change logs, and the project management plan that ties them together. The unifying idea is that documentation is not bureaucracy for its own sake - each artifact answers a real question (who owns this scope, when is it due, what could go wrong, who needs to know) and makes the project auditable and repeatable.
Study this domain by drafting the core artifacts yourself, because producing them is exactly what the performance-based questions probe. The lab below has you draft three documents for a hypothetical food-bank website redesign: a one-page project charter (from the charter template), a three-level work breakdown structure of 15-20 nodes (from the WBS template), and a six-row risk register with probability-times-impact scores and response strategies (from the risk-register template) - all in free tools with invented data. As always, read the official Project+ objectives for CompTIA's authoritative topic list; this explanation paraphrases its scope in our own words rather than reproducing it.
Learn it free
Official · Official exam objectives
CompTIA Project+ (PK0-005) exam objectivesThe authoritative topic list for this domain's tools-and-documentation coverage - read it directly rather than relying on any summary, including ours. (captured 2026-07-11)
Vetted independent · Free community practice questions
OpenExamPrep: free CompTIA Project+ practice questions (208+, no signup)A free bank of 208+ practice questions with explanations and no signup, useful across the documentation and process material; community-produced, so cross-check any answer against the official objectives. (captured 2026-07-11)
Projectplus Documents Worksheet Lab
Draft a one-page project charter and a three-level WBS of 15-20 nodes for a hypothetical project Produce a six-row risk register with probability-times-impact scores and response strategies coherent with the WBS
Free tools
Any operating system with a text editor or a free spreadsheet
A web browser to read the official CompTIA Project+ objectives
Steps
Open the three templates, read each top note that all data is hypothetical, and draft the one-page project charter (business need, objectives, scope, deliverables, milestones, made-up budget, stakeholders, risks, success criteria, and a one-line authorization).
Draft the three-level WBS: Level 1 the project, Level 2 major deliverables/phases, Level 3 work packages, landing on 15-20 total nodes, and answer the 100%-rule and work-package prompts.
Draft the six-row risk register: rate probability and impact 1-3, compute probability-times-impact, choose a response strategy and action and owner for each, list the top two by score, and tie a high-scoring risk back to a WBS work package, then save all three documents.
What you should see
Confirm the charter fills every field at a high level, the WBS has three levels and 15-20 nodes obeying the 100% rule, and the risk register scores six risks by probability times impact with response strategies and a link from a high-scoring risk to a WBS work package.
Practice evidence maps to exam_domain_comptia_project_plus_pk0_005_03
Stay safe & legal: This lab is filling in three local templates with invented data only; it touches no live system, needs no account and no payment, and creates, changes, or deletes nothing anywhere. Account required: no; payment required: no; maximum designed cost: $0.
Check yourself
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Module 4 of 4 · domain 4 · 18% of the exam
Basics of IT and governance
Study this last. At 18% it is the lightest domain, and it frames project work inside the IT and organizational controls - change control, compliance, security, and governance - that a coordinator must respect; it lands most clearly once the project mechanics from the first three domains are in place.
This is the 'work within IT and organizational rules' domain, and CompTIA weights it at 18% - the lightest slice of Project+. It reframes everything you have learned inside the guardrails an IT project must respect: basic IT concepts a coordinator should recognize, integrated change control, compliance and regulatory considerations, security awareness, and the difference between project governance and IT governance. We study it last because it makes the most sense once the project mechanics are in place - governance is the frame around the picture, not the picture itself. For a career changer, the reassuring news is that this domain tests awareness and process, not deep technical implementation: you need to recognize why a control matters, not configure it.
Basic IT literacy is the domain's foundation, pitched at a coordinator's level. Project+ is a cross-industry certification, but it lives under CompTIA's IT umbrella, so it expects you to recognize common IT vocabulary and delivery contexts - hardware and software, networks and the cloud, environments (development, test, production), and the idea that IT work moves through controlled stages before it reaches users. You are not expected to be a technician; you are expected to coordinate technical work intelligently, which means understanding enough of the landscape to ask the right questions, schedule realistically, and know when a security or compliance review belongs in the plan.
Integrated change control is the operational heart of the domain, and it is heavily examinable. Because the triple constraint means any change ripples through scope, time, cost, and quality, a disciplined project does not simply 'say yes' to new requests - it routes them through a formal process: a written change request, an impact analysis across the constraints, a decision by someone with authority (often a change control board), and a record in a change log. The examinable insight is that change control protects the project from scope creep - the slow, unmanaged accumulation of 'small' additions that quietly blows the budget and schedule. Recognizing the steps of the process, and why each exists, is a recurring skill.
Compliance, regulatory, and security considerations are the governance obligations a coordinator must build into the plan. Depending on the industry and the data involved, a project may have to respect data privacy rules (collecting and protecting personal data responsibly), regulatory or legal requirements, security reviews before a system goes live, access control (who may see or change what), vendor and third-party risk, and an audit trail so decisions and changes can be traced later. The exam does not ask you to implement these; it asks you to recognize when they apply and to know that ignoring them is itself a project risk. A coordinator's job is to make sure the right reviews are scheduled and the right approvals are obtained, not skipped for speed.
Project governance versus IT governance is the distinction that ties the domain together. Project governance is the decision rights, gates, oversight, and escalation paths that keep this particular project on track - the steering committee, the phase gates from Domain 2, and the change control board all belong here. IT governance is broader: the organization-wide framework of policies, standards, and controls (security, compliance, data management, access) that any IT initiative must operate within, regardless of which project it belongs to. The insight the exam rewards is that a project sits inside both at once - governed as a project and constrained by the organization's IT governance - and a coordinator has to satisfy both without letting either become an excuse to skip the other.
Study this domain by practicing the change and governance paperwork yourself, because that process discipline is exactly what the exam probes. The lab below has you, for a hypothetical food-bank website redesign where the sponsor asks to add online donations mid-project, fill in a change-request form with an impact analysis across the constraints plus a two-row change log (from the change-request template), and complete an IT-governance and compliance checklist covering data privacy, regulatory, security review, access control, vendor risk, and audit trail (from the governance-checklist template) - all in free tools with invented data. As always, read the official Project+ objectives for CompTIA's authoritative topic list; this explanation paraphrases its scope in our own words rather than reproducing it.
Learn it free
Official · Official exam objectives
CompTIA Project+ (PK0-005) exam objectivesThe authoritative topic list for this domain's IT-basics-and-governance coverage - read it directly rather than relying on any summary, including ours. (captured 2026-07-11)
Official · Official free sample questions
CompTIA Project+ (PK0-005) practice questionsCompTIA's own public sample questions for Project+, useful across all four domains to check familiarity with the question style; verify the page is live and free before relying on it. (captured 2026-07-11)
Projectplus Governance Worksheet Lab
Complete an integrated change-request form with a four-constraint impact analysis and a change log for a hypothetical project Complete an IT-governance and compliance checklist and distinguish project governance from IT governance
Free tools
Any operating system with a text editor
A web browser to read the official CompTIA Project+ objectives
Steps
Open both templates, read each top note that all data is hypothetical (including no real compliance data), and fill in the change-request form: the requested change, justification, and an impact analysis across scope, time, cost, and quality, then options, a recommendation, and a decision.
Fill in the two-row change log (CR-001 plus an invented CR-002), then complete the IT-governance checklist: for data privacy, regulatory, security review, access control, vendor risk, and audit trail, mark applicability and write one action line each.
Write the two reflections (why a donor-data change triggers both a change request and a security/governance review; how the project sits inside both project governance and IT governance) and save both documents.
What you should see
Confirm the change-request form analyzes impact across scope, time, cost, and quality with a recorded decision, the change log has two rows, the governance checklist marks all six areas with actions, and the reflection distinguishes project governance from IT governance.
Practice evidence maps to exam_domain_comptia_project_plus_pk0_005_04
Stay safe & legal: This lab is filling in two local templates with invented data only; it touches no live system, needs no account and no payment, and creates, changes, or deletes nothing anywhere. It uses no real organization's privacy, regulatory, security, access, or audit data. Account required: no; payment required: no; maximum designed cost: $0.
Check yourself
2RoleMath-original concept checks for this domain — written by us against cited public sources, never taken from any exam. They confirm understanding; they don’t predict a pass.
Before you book the exam
Work through the modules above, then get a personalized read on where you stand: the readiness check maps your background against these same published domains and suggests what to study first — no score, no pass prediction.
Exam code: PK0-005 - the current Project+ exam. The prior version, PK0-004, retired on 2023-05-09; no successor to PK0-005 has been announced. Official CompTIA Project+ certification page
Exam format: Up to 90 questions, a mix of multiple-choice and performance-based (PBQ) items, in 90 minutes, delivered through Pearson VUE (test center or online proctoring). Official CompTIA Project+ certification page
Prerequisites and recommended experience: No prerequisites. CompTIA recommends roughly 6 to 12 months of project-coordination experience as helpful context, but nothing is required to sit the exam - it is designed as an entry-level, cross-industry certification. Official CompTIA Project+ certification page
Certification validity and renewal: As of 2025-10-01, Project+ is a continuing-education (CE) certification: it is valid for three years and is renewed by earning 30 continuing-education units (CEUs) per cycle plus a periodic CE fee of about $150. This CE model applies to everyone who earns Project+ on or after 2025-10-01. Candidates who earned it BEFORE 2025-10-01 retain the legacy 'Good for Life' status. Confirm the current renewal terms in CompTIA's official continuing-education documentation before relying on them. Official CompTIA help article: Server and Project transition to CE certifications
Version currency: PK0-005 launched 2022-11-08 and is the current version; PK0-004 retired 2023-05-09. The one material recent change is the lifecycle move to a CE certification effective 2025-10-01 (see the validity fact). Always diff the current objectives and renewal terms on CompTIA's page before you schedule. Official CompTIA Project+ certification page
A free, source-cited study companion built on CompTIA's published Project+ (PK0-005) exam objectives - for independent study only, not official training, not affiliated with or endorsed by CompTIA, and not a pass guarantee. Project+ is an entry-level certification with NO prerequisites that tests project process and documentation rather than technical implementation, making it a strong fit for career changers moving into IT project coordination from administrative, operations, education, healthcare, or retail backgrounds. Every lab here is a worksheet or template you complete with hypothetical practice data in free tools. Verify the current objectives on the official page before your exam.
Certification and vendor names are used only to identify the program this independent study companion refers to. RoleMath is not affiliated with, endorsed by, or sponsored by CompTIA.