CompTIA PK0-005 30-, 60-, and 90-day study plan with topic order, review loops, and final-week priorities.
Use this study plan when you want a real route through PK0-005 instead of circling disconnected PM terms. Project+ rewards sequence, control, and documentation under pressure, so the best study plan mirrors that order.
| Domain | Weight | What to master before moving on |
|---|---|---|
| Project Management Concepts | 33% | methodology fit, change control, risk vs issue, schedule logic, quality, communication, meetings, and procurement |
| Project Life Cycle Phases | 30% | discovery, initiation, planning outputs, execution control, and closure evidence |
| Tools and Documentation | 19% | logs, charts, dashboards, collaboration tools, and quality visuals |
| Basics of IT and Governance | 18% | security, privacy, compliance, cloud and infrastructure basics, and IT change control |
Use this only if you already coordinate work, vendors, meetings, or status reporting in real projects.
| Week | Primary work | Secondary work |
|---|---|---|
| 1 | project characteristics, delivery methods, lifecycle phases, core artifacts | glossary cleanup on charter, baseline, WBS, issue, risk, and critical path |
| 2 | planning, scheduling, communication, meetings, team performance, and procurement | one mixed review block from the cheat sheet |
| 3 | execution, quality, change control, tools, charts, dashboards, and registers | scenario drills that force you to choose the right artifact first |
| 4 | IT governance, security, privacy, cloud basics, and final mixed sets | FAQ and resources review before booking |
This is the safer lane if you are newer to project terminology or formal controls.
flowchart LR
A["Read one lesson"] --> B["Write 3 decision rules"]
B --> C["Do a short mixed set"]
C --> D["Log misses by phase or artifact"]
D --> E["Review only the weak lane"]
Strong decision rules look like this:
current problem = issue log, not risk registerscope change = impact analysis plus approval pathfixed date + critical path slip = compression or scope trade-off, not denialYou are getting close when: