Who this Study Plan is for
This Study Plan is for candidates preparing for the real CompTIA Project+ (PK0-005) exam, exam code Project+. It is designed for people who need a practical schedule, not just a list of topics.
Use this plan if you need to turn available study time into daily work across project management concepts, project roles, governance, delivery approaches, planning documents, risk, change control, stakeholders, communication, agile, predictive, and hybrid project scenarios.
The main goal is to move from recognition of terms into scenario judgment: given a project situation, you should be able to choose the best next action, document, role, escalation path, or control process.
Which plan should you use?
| Your situation | Best path | Main goal | Watch out for |
|---|
| Exam is in 7 days and you have already studied | 7-day final review | Identify weak areas, review explanations, take timed practice | Do not try to relearn the whole exam |
| Exam is in 14 days and you know some project basics | 14-day focused plan | Build coverage quickly and practice mixed scenarios | Avoid spending all time reading |
| Exam is in 30 days and you can study most days | 30-day balanced plan | Complete topic review, then shift to scenario practice | Do not delay practice until the last week |
| Exam is 60 days away and you are newer to project work | 60-day full preparation path | Build concepts, documentation fluency, and decision judgment | Do not stay in passive note-taking mode |
| Exam is 90 days away or your schedule is irregular | 90-day extended path | Create three passes: learn, apply, refine | Keep weekly milestones so the plan does not drift |
Planning buckets for CompTIA Project+ preparation
Do not study Project+ as isolated vocabulary only. Organize each session around a practical project-management bucket.
| Planning bucket | What to know | What to practice |
|---|
| Project foundations | Project purpose, constraints, assumptions, deliverables, milestones, roles, responsibilities, governance, value, benefits | Identify the project role or document needed in a scenario |
| Delivery approach | Predictive, agile, iterative, incremental, and hybrid work | Decide which approach fits a scenario and what changes in communication, planning, and control |
| Planning documents | Scope, schedule, budget, resources, quality, communications, risk, stakeholder, procurement, requirements, and change-related documents | Choose the correct plan, log, register, baseline, or report |
| Execution and monitoring | Status tracking, issue management, risk response, team coordination, vendor coordination, stakeholder communication | Select the best next step when a project is off track |
| Risk, issue, and change control | Risk identification, risk response, issue escalation, change requests, impact analysis, approvals | Distinguish risk vs. issue vs. change request |
| Stakeholders and communication | Stakeholder needs, reporting level, meeting type, conflict, escalation, communication channels | Match the communication method to the stakeholder and situation |
| Tools and visual controls | Gantt-style schedules, task boards, dashboards, burn charts, RACI-style responsibility mapping, logs, reports | Interpret the tool and identify the management action |
| Closure and transition | Acceptance, handoff, lessons learned, documentation, release or transition activities | Identify what must happen before closing or transitioning work |
The daily practice rhythm
Use the same rhythm almost every study day. Consistency matters more than long, unfocused sessions.
If you have 45 minutes
| Time | Activity | Output |
|---|
| 5 minutes | Recall yesterday’s weak areas | 3 topics to watch |
| 15 minutes | Review one focused topic | Short notes or flashcards |
| 15 minutes | Answer practice questions on that topic | Mark every uncertain answer |
| 10 minutes | Review explanations | Add misses to error log |
If you have 90 minutes
| Time | Activity | Output |
|---|
| 10 minutes | Warm-up recall | Quick check of prior misses |
| 25 minutes | Topic review | One objective area strengthened |
| 30 minutes | Scenario practice | Mixed or targeted questions |
| 20 minutes | Explanation review | Error log updated |
| 5 minutes | Plan tomorrow | Next topic chosen |
If you have 2 to 3 hours
| Time | Activity | Output |
|---|
| 15 minutes | Review error log | Pick highest-value weak area |
| 40 minutes | Deep topic review | Notes, examples, document comparisons |
| 45 minutes | Timed practice set | Pace and accuracy data |
| 45 minutes | Explanation review | Corrected reasoning |
| 15 minutes | Flashcards or recall drill | Reinforced weak facts |
Diagnostic practice: what to do first
Take a diagnostic set before building your schedule, even if you feel unprepared. The diagnostic is not about proving readiness. It tells you where to spend time.
Use this review method after the diagnostic:
| Diagnostic result | What it usually means | What to do next |
|---|
| You miss basic terms | Foundation gap | Review project concepts, roles, documents, and lifecycle language |
| You know terms but miss scenarios | Judgment gap | Practice “best next action” questions and review explanations carefully |
| You confuse risk, issue, and change | Control-process gap | Build a comparison sheet and practice targeted scenarios |
| You miss agile vs. predictive questions | Delivery-approach gap | Review how planning, roles, cadence, and change differ by approach |
| You miss stakeholder questions | Communication gap | Review stakeholder analysis, reporting, escalation, and meeting purpose |
| You run out of time | Pacing gap | Use shorter timed sets before full timed mocks |
| Your score is uneven by topic | Prioritization needed | Study the weakest two buckets first, not the easiest topics |
Missed-question review method
A missed question is useful only if you convert it into a rule you can apply later.
For every missed or guessed question, log:
| Field | What to write |
|---|
| Topic | Example: change control, stakeholder communication, agile delivery, risk response |
| Scenario trigger | What wording should have alerted you? |
| Your mistaken reasoning | Why did the wrong answer look attractive? |
| Correct rule | The decision rule you should apply next time |
| Similar scenario | A short example of when the rule applies |
Missed-answer decision table
| If you missed because… | Do this before more questions |
|---|
| You did not know the term | Review the concept, then make a one-line definition |
| You confused two documents | Build a comparison table: purpose, owner, timing, output |
| You picked an extreme action too early | Review escalation, approval, and communication sequence |
| You treated a risk as an issue | Practice classifying events as risk, issue, assumption, or change |
| You skipped impact analysis | Review change control and baseline effects |
| You ignored stakeholder needs | Review communication level, audience, and timing |
| You answered from personal work habits | Re-anchor to exam-style project governance and documented process |
| You rushed the wording | Slow down on qualifiers like first, best, most likely, next, except |
What to practice next
Use your error log to choose the next study block.
| Your current weak area | Practice next | Key question to ask |
|---|
| Roles and responsibilities | RACI-style mapping, sponsor vs. project manager vs. team member vs. stakeholder | Who owns the decision or action? |
| Scope and requirements | Scope statement, requirements, deliverables, acceptance criteria | Is this about what is included, what is excluded, or how it is accepted? |
| Schedule and resources | Dependencies, milestones, resource conflicts, schedule updates | What changed, and what is the impact? |
| Budget and constraints | Cost limits, tradeoffs, approvals, constraint balancing | Which constraint is being affected? |
| Risk | Risk identification, probability/impact thinking, response planning | Is this a possible future event? |
| Issue management | Issue log, escalation, ownership, resolution tracking | Has the problem already happened? |
| Change control | Change request, impact analysis, approval, baseline update | Has the requested change been evaluated and authorized? |
| Stakeholder communication | Reports, meetings, escalation, stakeholder expectations | Who needs what information, when, and at what level? |
| Agile and hybrid | Backlog, iteration cadence, adaptive planning, team collaboration | Is the work being planned up front, adapted iteratively, or blended? |
| Governance and compliance | Policies, audit needs, security awareness, documentation discipline | What control or approval is required? |
| Closure | Acceptance, handoff, lessons learned, final documentation | What must be confirmed before closure? |
7-day final review plan
Use this path if your exam is in one week and you have already completed at least one pass through the material. If you have not studied at all, use the 7 days to triage the highest-value topics and practice explanations rather than trying to memorize everything.
| Day | Primary task | Practice task | Review task |
|---|
| 1 | Take a mixed diagnostic set | Identify top 3 weak buckets | Build or update your error log |
| 2 | Review project foundations, roles, constraints, and governance | Targeted questions on roles and project concepts | Write decision rules for missed items |
| 3 | Review planning documents: scope, schedule, budget, resources, quality, communications | Targeted questions on documents and planning scenarios | Compare similar documents side by side |
| 4 | Review risk, issue, change control, and escalation | Scenario set on “best next action” questions | Classify each miss: risk, issue, change, communication |
| 5 | Review agile, predictive, hybrid, tools, status reporting, and stakeholder communication | Mixed timed set | Review explanations for both wrong and guessed answers |
| 6 | Take a timed mock or the longest timed set available | Simulate exam pacing | Spend more time reviewing than testing |
| 7 | Light final review only | Short confidence set, not a new heavy mock | Review error log, key documents, and decision rules |
7-day rules
- Stop adding broad new material after Day 5 unless it is a repeated error-log topic.
- Do not take a full timed mock late on Day 7 if it will create fatigue.
- Review explanations for questions you got right by guessing.
- Prioritize scenario judgment over memorizing isolated definitions.
- Sleep and pacing matter in the final 24 hours.
14-day focused plan
Use this if you have two weeks and can study 60 to 120 minutes most days.
| Day | Focus | Study actions |
|---|
| 1 | Diagnostic and plan | Take a mixed diagnostic set, categorize misses, choose your weakest buckets |
| 2 | Project concepts and governance | Review project purpose, constraints, assumptions, deliverables, value, roles, approvals |
| 3 | Roles and stakeholders | Practice sponsor, project manager, team, customer, vendor, and stakeholder scenarios |
| 4 | Scope and requirements | Review scope, requirements, deliverables, acceptance, scope change |
| 5 | Schedule and resources | Review dependencies, milestones, resource conflicts, scheduling tools |
| 6 | Budget, quality, and procurement basics | Practice tradeoff and constraint questions |
| 7 | Planning documents review | Build a document comparison chart and answer targeted questions |
| 8 | Risk and issue management | Practice classifying risk vs. issue and choosing response or escalation |
| 9 | Change control | Review change request flow, impact analysis, approvals, baseline updates |
| 10 | Communication and conflict | Practice stakeholder reporting, meeting purpose, conflict, and escalation scenarios |
| 11 | Agile, predictive, and hybrid | Compare delivery approaches and practice mixed approach scenarios |
| 12 | Timed mock or long timed set | Simulate pacing; do not pause during the timed portion |
| 13 | Explanation review and weak-area repair | Rework every missed mock question and revisit repeated topics |
| 14 | Final readiness review | Light mixed set, error log, document comparison, exam-day pacing plan |
14-day priorities
| Priority | What to do |
|---|
| Highest | Review explanations deeply and fix repeated reasoning errors |
| High | Practice mixed scenarios after each topic review |
| Medium | Build quick-reference comparisons for documents and processes |
| Low | Rewrite long notes or reread chapters without practice |
30-day balanced plan
Use this if you want a complete preparation cycle with time for review, practice, and at least one full timed simulation.
Weekly structure
| Week | Main goal | Output by end of week |
|---|
| 1 | Build foundations | You can explain project roles, constraints, governance, lifecycle terms, and delivery approaches |
| 2 | Master planning documents | You can distinguish scope, schedule, budget, resource, quality, communication, risk, and change artifacts |
| 3 | Practice control scenarios | You can handle risk, issue, change, stakeholder, communication, and escalation questions |
| 4 | Simulate and refine | You can complete timed mixed practice and explain your missed answers |
30-day schedule
| Day | Focus | Required practice |
|---|
| 1 | Diagnostic set and study setup | Create error log and topic map |
| 2 | Project purpose, value, benefits, constraints | Targeted concept questions |
| 3 | Roles and responsibilities | Scenario questions on who does what |
| 4 | Governance, approvals, business context | Mixed questions on authority and control |
| 5 | Predictive, agile, hybrid overview | Compare planning and change handling |
| 6 | Review Week 1 topics | Timed mini-set |
| 7 | Catch-up and error-log repair | Re-answer missed-question concepts without looking |
| 8 | Scope, requirements, deliverables | Targeted planning questions |
| 9 | Schedule, milestones, dependencies | Practice schedule interpretation scenarios |
| 10 | Resources and team coordination | Resource conflict questions |
| 11 | Budget, procurement, vendor coordination | Constraint and approval scenarios |
| 12 | Quality and acceptance | Practice acceptance and quality-control questions |
| 13 | Communications and stakeholder planning | Reporting and audience scenarios |
| 14 | Planning document review | Build document comparison sheet |
| 15 | Risk identification and response | Risk scenario set |
| 16 | Issue management and escalation | Issue vs. risk classification |
| 17 | Change control | Change request and impact-analysis scenarios |
| 18 | Monitoring, status, reporting, dashboards | Timed mixed set |
| 19 | Conflict, meetings, team communication | Stakeholder and team scenarios |
| 20 | Tools, logs, registers, boards, charts | Tool interpretation practice |
| 21 | Week 3 review | Long mixed practice set and explanation review |
| 22 | Agile delivery scenarios | Backlog, iteration, collaboration, change scenarios |
| 23 | Predictive and hybrid scenarios | Baselines, approvals, adaptive elements |
| 24 | Governance, compliance, security awareness in project context | Scenario set on controls and documentation |
| 25 | Closure, handoff, lessons learned | Closure questions |
| 26 | Full timed mock or longest available timed set | Simulated exam conditions |
| 27 | Mock review | Review every missed, guessed, and slow question |
| 28 | Weak-area repair | Target top two error-log categories |
| 29 | Final mixed set | Confirm pacing and decision rules |
| 30 | Light review | Error log, document chart, rest, exam-day plan |
30-day checkpoints
| Checkpoint | You are on track if… |
|---|
| End of Week 1 | You can explain key project terms without reading notes |
| End of Week 2 | You know which document or plan fits a given scenario |
| End of Week 3 | You can choose the best next action for risk, issue, change, and stakeholder scenarios |
| End of Week 4 | Your practice results are stable and your misses are explainable |
60-day full preparation path
Use the 60-day path if you are newer to formal project management or want a stronger buffer for scenario practice.
| Phase | Days | Focus | Practice target |
|---|
| Phase 1 | 1-7 | Diagnostic, exam objective mapping, study setup | Short diagnostic and error log |
| Phase 2 | 8-18 | Project concepts, roles, lifecycle, governance, value | Topic-specific questions |
| Phase 3 | 19-30 | Planning documents and tools | Document comparison and planning scenarios |
| Phase 4 | 31-42 | Risk, issue, change, communication, stakeholders | Scenario-heavy targeted practice |
| Phase 5 | 43-50 | Agile, predictive, hybrid, execution, monitoring, closure | Mixed delivery-approach scenarios |
| Phase 6 | 51-57 | Timed mocks and explanation review | At least one full timed simulation or equivalent long timed set |
| Phase 7 | 58-60 | Final review and readiness check | Error log, weak topics, light mixed practice |
60-day weekly plan
| Week | Main work | End-of-week deliverable |
|---|
| 1 | Diagnostic, gather materials, build topic checklist | Error log and calendar |
| 2 | Foundations: project purpose, constraints, roles, governance | Role and constraint summary |
| 3 | Delivery approaches and lifecycle thinking | Agile/predictive/hybrid comparison |
| 4 | Planning: scope, schedule, budget, resources, quality | Planning document chart |
| 5 | Communications, stakeholders, procurement, vendor coordination | Stakeholder communication matrix |
| 6 | Risk, issue, change, escalation, monitoring | Control-process decision rules |
| 7 | Tools, reports, closure, transition, lessons learned | Tool and closure review sheet |
| 8 | Timed practice, mock review, final weak-area repair | Readiness checklist completed |
90-day extended path
Use this if you have a demanding work schedule, limited project-management background, or need more repetition before timed practice.
| Month | Goal | What to do |
|---|
| Month 1 | Learn the language | Complete first pass through project concepts, roles, lifecycle, delivery approaches, and core documents |
| Month 2 | Apply the concepts | Practice scenarios by topic; build comparison charts for documents, roles, risk, issue, and change |
| Month 3 | Refine under time | Use mixed timed sets, mock exams, explanation review, and final error-log repair |
90-day milestones
| Day range | Milestone | Required output |
|---|
| 1-10 | Baseline | Diagnostic completed and weak areas ranked |
| 11-30 | First content pass | Notes reduced to concise decision rules |
| 31-50 | Second pass with practice | Topic practice completed for every planning bucket |
| 51-65 | Scenario judgment | Mixed scenario sets across risk, change, stakeholders, and delivery approach |
| 66-78 | Timed practice | Timed sets and at least one full simulation or equivalent long timed session |
| 79-86 | Weak-area repair | Error-log categories reduced to a short final list |
| 87-90 | Final review | Light practice, no major new resources, exam-day plan |
How to review agile, predictive, and hybrid scenarios
Project+ preparation should include delivery approach judgment. Do not only memorize terms. Practice how the project context changes the correct action.
| Scenario clue | Likely focus | What to think about |
|---|
| Requirements are expected to change | Agile or hybrid judgment | How is work prioritized, reviewed, and adapted? |
| Scope and approvals are defined up front | Predictive judgment | How are baselines, change requests, and formal approvals handled? |
| Some work is fixed and some is iterative | Hybrid judgment | Which parts need formal control and which parts adapt? |
| Frequent stakeholder feedback is emphasized | Agile or iterative communication | How does feedback enter planning? |
| A formal change is requested after baseline | Predictive or governed hybrid control | Has impact analysis and approval occurred? |
| Team is blocked during execution | Any approach | Is the best action communication, escalation, risk response, or issue resolution? |
When to use timed mock exams
Timed mocks are most useful after you have enough coverage to learn from the results. Taking too many early mocks can waste questions and create false confidence.
| Study timeline | When to start timed mocks | How to use them |
|---|
| 7 days | Day 1 diagnostic, Day 6 timed mock or long timed set | Use results only to triage final review |
| 14 days | Around Day 12 | Spend Day 13 reviewing explanations |
| 30 days | Around Day 26 | Use Days 27-29 for weak-area repair |
| 60 days | Final 10 days | Take one full timed simulation, then targeted repair |
| 90 days | Final 3 to 4 weeks | Alternate timed sets with deep explanation review |
Timed mock rules
- Simulate the real testing mindset: no pausing, no notes, no checking answers mid-set.
- Mark questions you are unsure about, even if you answer correctly.
- Review the mock in two passes:
- Wrong and guessed questions.
- Slow questions and questions where you eliminated poorly.
- Do not judge readiness from a single score. Look for stable performance and fewer repeated error types.
- If your practice source provides timing guidance, follow that timing during mocks.
Final-week rules
| Rule | Reason |
|---|
| Stop broad new material 2 to 3 days before the exam | New resources can create confusion and fatigue |
| Keep practicing, but reduce volume | You want sharpness, not burnout |
| Review explanations more than questions | Explanation review improves scenario judgment |
| Revisit your error log daily | Repeated mistakes are the highest-value fixes |
| Practice document comparisons | Project+ scenarios often turn on choosing the correct artifact or control |
| Do not ignore guessed correct answers | A guess can become a miss on exam day |
| Sleep and logistics are part of readiness | Fatigue can turn known material into careless errors |
Exam-readiness checks
You are more ready for CompTIA Project+ (PK0-005) when the following are true:
| Readiness check | Yes/No |
|---|
| I can explain the difference between a risk, an issue, and a change request. | |
| I can choose the correct next action when scope, schedule, budget, or resources change. | |
| I can identify which stakeholder or role should approve, receive, or perform an action. | |
| I can distinguish agile, predictive, and hybrid scenario clues. | |
| I can match common project documents, logs, plans, and reports to their purpose. | |
| I can explain why the wrong answer choices are wrong, not just why the right answer is right. | |
| My recent timed practice is stable, not based on one lucky result. | |
| My error log has only a few repeated categories left. | |
| I have a pacing plan for the exam session. | |
| I have stopped adding major new resources and am reviewing final weak areas. | |
Practical next step
Choose the schedule that matches your exam date, take a diagnostic or mixed practice set, and build your error log today. Your next study session should be based on your weakest Project+ scenario category, not on the topic that feels easiest.