Study plan overview
This Study Plan is for candidates preparing for the PMI Project Management Professional (PMP) exam, exam code PMP. It is designed for practical execution: what to study, when to practice, how to review missed questions, and when to stop adding new material.
The PMP exam rewards scenario judgment more than memorized definitions. Your preparation should move from concept review into decision-making across:
- People, stakeholder, and team situations
- Predictive, agile, and hybrid delivery approaches
- Risk, issue, change, scope, schedule, cost, quality, procurement, and communications decisions
- Governance, business value, benefits, compliance, and organizational context
- Servant leadership, conflict resolution, coaching, escalation, and facilitation
Use the plan that matches your remaining time. If your exam is already scheduled, prioritize timed practice and explanation review over rereading large sections of material.
Which plan should you use?
| Time until exam | Best plan | Primary goal | Best for | Main risk |
|---|
| 7 days | Final review plan | Stabilize performance and reduce mistakes | Candidates who already studied | Trying to learn too much too late |
| 14 days | Focused plan | Close weak areas and build exam rhythm | Candidates with partial prep done | Skipping review of missed questions |
| 30 days | Balanced plan | Build knowledge and timed judgment | Most working professionals | Spending too long on notes |
| 60/90 days | Full preparation path | Learn, practice, review, and simulate | Candidates starting early | Losing momentum or delaying practice |
If you are unsure
| Your current situation | Use this approach |
|---|
| You have not taken any diagnostic questions | Take a mixed diagnostic set first, then choose a plan |
| You know the concepts but miss scenarios | Reduce reading and increase explanation review |
| You are weak in agile or hybrid questions | Add daily agile scenario practice for one week |
| You are weak in predictive process questions | Review planning, baselines, change control, risk, procurement, and quality decisions |
| You often choose between two close answers | Review the reason the correct answer is better, not just why your answer was wrong |
| You run out of time | Add timed sets immediately and practice pacing |
Core PMP study rhythm
Use this daily rhythm for any plan longer than one week.
| Block | Time | Action | Output |
|---|
| Warm-up review | 10-15 min | Review yesterday’s missed-question log | Revisit patterns, not random notes |
| Concept focus | 30-60 min | Study one PMP topic or decision area | Short notes, decision rules, examples |
| Scenario practice | 45-90 min | Answer mixed or topic-based questions | Timed practice, no pausing |
| Explanation review | 45-90 min | Review every missed and guessed question | Add causes and corrections to log |
| Recap | 5-10 min | Choose tomorrow’s weak-area target | Clear next session |
A strong PMP session usually has more practice and review than passive reading. If time is limited, protect the scenario practice and explanation review blocks first.
Diagnostic practice before you build the schedule
Before starting a 14-day, 30-day, or 60/90-day plan, complete a diagnostic set.
| Diagnostic step | How to do it |
|---|
| Use mixed questions | Include predictive, agile, hybrid, people, process, and business scenarios |
| Work under light time pressure | Do not research while answering |
| Mark confidence | Mark each answer as confident, uncertain, or guessed |
| Review immediately | Do not wait until the next day |
| Categorize misses | Topic gap, misread, wrong role, wrong delivery approach, poor elimination, timing |
| Set priorities | Study the highest-frequency miss patterns first |
Diagnostic results: what to do next
| Pattern you see | What it usually means | Next study action |
|---|
| Misses are spread across all areas | Foundation is incomplete | Use the 30-day or 60/90-day plan |
| Misses cluster in agile and hybrid | Delivery approach judgment is weak | Drill agile roles, ceremonies, backlog, servant leadership, and hybrid transitions |
| Misses cluster in predictive process areas | Process flow is weak | Review planning, baselines, change control, risk, quality, procurement, and stakeholder communications |
| You know facts but miss scenarios | Judgment gap | Practice scenario sets and compare answer rationales |
| You change correct answers often | Confidence and elimination issue | Write why each wrong option is less appropriate |
| You miss long questions | Reading strategy issue | Practice identifying role, problem, timing, and delivery approach first |
7-day PMP final review plan
Use this if your PMI PMP exam is within one week. This is not the time to rebuild your entire foundation. Your goal is to stabilize judgment, reduce careless errors, and rehearse exam pacing.
7-day schedule
| Day | Main focus | Practice | Review task |
|---|
| 7 days out | Diagnostic reset | Timed mixed set | Identify top 3 weak patterns |
| 6 days out | Agile and hybrid scenarios | Agile/hybrid question set | Review servant leadership, backlog, team decisions, change handling |
| 5 days out | Predictive process decisions | Predictive scenario set | Review baselines, change control, risk, quality, procurement |
| 4 days out | Stakeholders, team, conflict | People-focused set | Review escalation, coaching, communication, facilitation |
| 3 days out | Timed mock or long timed set | Full mock or extended timed block | Review explanations deeply; do not chase every topic |
| 2 days out | Weak-area repair | Short targeted sets | Rework missed questions without memorizing answers |
| 1 day out | Light final review | Short confidence set only | Review formulas, terms, mindset, and exam logistics |
Final-week rules
| Rule | Why it matters |
|---|
| Stop adding major new resources | New material can create confusion and reduce confidence |
| Review explanations more than notes | PMP improvement comes from decision correction |
| Practice under time pressure | Timing mistakes often appear only in mixed sets |
| Do not take a heavy mock the day before if it will exhaust you | The final day should sharpen, not drain |
| Rework missed questions by reasoning | Memorized answers do not transfer to new scenarios |
| Sleep and logistics are part of readiness | Fatigue causes misreads and poor elimination |
What to review in the final 48 hours
- Your missed-question log
- PMI PMP scenario decision patterns
- Agile, predictive, and hybrid differences
- Change control versus adaptive backlog refinement
- Risk response versus issue response
- Stakeholder engagement and communication choices
- Team conflict, coaching, empowerment, and escalation
- Benefits, value, compliance, and business alignment
- Key formulas and interpretation, if included in your materials
- Exam appointment requirements and pacing plan
14-day focused PMP plan
Use this if you have two weeks and at least some prior exposure to PMP content. This plan assumes you can study most days and complete several timed sets.
14-day schedule
| Day | Focus | Study action | Practice action |
|---|
| 1 | Baseline | Take diagnostic mixed set | Build missed-question log |
| 2 | PMP mindset and roles | Review project manager, sponsor, team, product owner, stakeholders | Short mixed set |
| 3 | Agile delivery | Review Scrum-style flow, backlog, iteration, servant leadership | Agile scenario set |
| 4 | Predictive planning | Review scope, schedule, cost, quality, resources | Predictive planning set |
| 5 | Risk and issues | Review risk identification, response, monitoring, issue escalation | Risk/issue set |
| 6 | Stakeholders and communications | Review engagement, conflict, communications strategy | People/stakeholder set |
| 7 | Timed mixed checkpoint | Complete longer timed set | Deep explanation review |
| 8 | Change and governance | Review integrated change control, baselines, approvals, tailoring | Change/governance set |
| 9 | Hybrid scenarios | Review when predictive and agile practices combine | Hybrid scenario set |
| 10 | Business value and benefits | Review value delivery, benefits, compliance, organizational change | Business context set |
| 11 | Quality, procurement, resources | Review decision points and responsibilities | Targeted weak-area set |
| 12 | Full mock or extended timed practice | Simulate pacing | Review all misses and guesses |
| 13 | Repair day | Revisit top weak patterns | Short targeted sets |
| 14 | Light final review | Review log, formulas, mindset, logistics | Short confidence set |
14-day priority order
If you cannot complete every task, use this order:
- Mixed diagnostic
- Missed-question log
- Agile, predictive, and hybrid scenario practice
- Stakeholder, risk, and change review
- Timed mock or extended timed set
- Final explanation review
Do not spend the full two weeks reading. The PMP exam requires selecting the best action in context, so scenario practice must start immediately.
30-day balanced PMP plan
Use this if you want a realistic plan while working full time. The 30-day plan balances concept review, scenario practice, missed-question review, and timed mock exams.
Weekly structure
| Week | Goal | Study emphasis | Practice emphasis |
|---|
| Week 1 | Build baseline and core framework | PMP mindset, roles, delivery approaches, project life cycles | Diagnostic and topic sets |
| Week 2 | Strengthen process and people decisions | Planning, risk, change, stakeholders, communications, team | Scenario sets by topic |
| Week 3 | Move to mixed judgment | Agile/predictive/hybrid, governance, value, quality, procurement | Timed mixed sets |
| Week 4 | Simulate and repair | Weak areas, mocks, final review | Mock exams and explanation review |
30-day schedule
| Day | Focus | Action |
|---|
| 1 | Diagnostic | Take mixed diagnostic and create your error log |
| 2 | PMP exam mindset | Review how to identify role, issue, delivery approach, and best next action |
| 3 | Delivery approaches | Compare predictive, agile, and hybrid decision patterns |
| 4 | Stakeholders | Practice engagement, expectations, conflict, and communication scenarios |
| 5 | Team leadership | Practice coaching, servant leadership, motivation, conflict, and escalation |
| 6 | Predictive planning | Review scope, schedule, cost, resources, quality, and baselines |
| 7 | Weekly review | Timed mixed set and missed-question review |
| 8 | Risk | Review risk identification, qualitative judgment, responses, monitoring |
| 9 | Issues and escalation | Distinguish risk, issue, impediment, and escalation choices |
| 10 | Change control | Review change requests, impact analysis, approvals, baselines |
| 11 | Agile roles and events | Practice product owner, team, backlog, iteration, review, retrospective decisions |
| 12 | Hybrid delivery | Practice mixed governance and adaptive execution scenarios |
| 13 | Business value | Review benefits, value delivery, compliance, organizational change |
| 14 | Checkpoint | Longer timed mixed set and explanation review |
| 15 | Quality | Review prevention, inspection, acceptance, continuous improvement |
| 16 | Procurement | Review vendor issues, contracts at a high level, procurement decisions |
| 17 | Communications | Review communication methods, stakeholder needs, reporting, transparency |
| 18 | Governance | Review tailoring, compliance, approvals, project board/sponsor interactions |
| 19 | Integrated scenarios | Practice multi-topic questions |
| 20 | Weak-area repair | Re-study top 3 error categories |
| 21 | Timed mock | Take a full mock or extended simulation |
| 22 | Mock review | Review every missed, guessed, and slow question |
| 23 | Agile/predictive split | Drill questions that require identifying the delivery approach |
| 24 | People scenarios | Drill conflict, team performance, stakeholder resistance |
| 25 | Process scenarios | Drill risk, change, quality, procurement, schedule, cost |
| 26 | Business context | Drill benefits, value, compliance, organizational priorities |
| 27 | Second mock or long timed set | Simulate exam pacing again |
| 28 | Explanation review | Convert mock results into final weak-area list |
| 29 | Final repair | Short targeted sets; review formulas and key decision rules |
| 30 | Light review | Confidence set, logistics, rest, and pacing plan |
30-day time budget
| Available time | Recommended daily plan |
|---|
| 45 minutes/day | 15 min review, 25 min practice, 5 min log update |
| 60-90 minutes/day | 20 min review, 40-50 min practice, 20 min explanation review |
| 2 hours/day | 30 min study, 60 min timed practice, 30 min explanation review |
| Weekend block | One long timed set plus full explanation review |
60/90-day full PMP preparation path
Use this if you are starting early or returning after a long break. The goal is to avoid cramming and build reliable scenario judgment.
Phase plan
| Phase | 60-day timing | 90-day timing | Goal |
|---|
| Foundation | Days 1-14 | Days 1-21 | Learn PMP structure, roles, delivery approaches, and core terms |
| Domain build | Days 15-30 | Days 22-45 | Review people, process, business context, agile, predictive, hybrid |
| Scenario conversion | Days 31-45 | Days 46-65 | Shift from notes to scenario judgment |
| Timed practice | Days 46-54 | Days 66-80 | Use mocks and timed mixed sets |
| Final review | Days 55-60 | Days 81-90 | Repair weak areas and reduce exam-day risk |
60-day schedule by week
| Week | Focus | Practice target |
|---|
| 1 | PMP orientation, exam style, roles, delivery approaches | Diagnostic and short topic sets |
| 2 | Predictive fundamentals: planning, baselines, change, governance | Predictive decision questions |
| 3 | Agile fundamentals: servant leadership, backlog, iteration, team ownership | Agile scenario questions |
| 4 | Stakeholders, communications, team, conflict, resources | People-focused scenario sets |
| 5 | Risk, issues, quality, procurement, compliance, business value | Process and business scenario sets |
| 6 | Hybrid and integrated scenarios | Mixed timed sets |
| 7 | First full mock or extended simulation | Deep explanation review |
| 8 | Weak-area repair and second mock | Final review and pacing |
90-day schedule by month
| Month | Focus | What to complete |
|---|
| Month 1 | Foundation | Read core materials, build glossary, take topic quizzes, start error log |
| Month 2 | Scenario development | Practice by domain and delivery approach; review explanations daily |
| Month 3 | Timed readiness | Complete mocks, repair weak areas, finalize pacing and exam strategy |
Weekly routine for 60/90 days
| Day type | Action |
|---|
| 3-4 weekdays | Study one topic and complete a short practice set |
| 1 weekday | Review missed questions only |
| 1 weekend day | Longer mixed set or mock segment |
| 1 rest/light day | Flash review, formulas, glossary, or no study |
Starting early does not mean delaying practice. Begin questions in week 1, even if your scores are low. Early mistakes are useful because they show how the exam frames decisions.
What to study by PMP area
Use this table to organize content review without turning preparation into memorization.
| Area | What to know | What to practice |
|---|
| PMP mindset | Best next action, proactive leadership, ethics, collaboration, value focus | Questions with two plausible answers |
| People and team | Conflict, coaching, motivation, virtual teams, stakeholder resistance | What the project manager should do first |
| Predictive delivery | Plans, baselines, change requests, risk register, issue log, quality control | Change, risk, and governance scenarios |
| Agile delivery | Servant leadership, backlog, iterations, impediments, product owner, team ownership | Adaptive planning and team empowerment |
| Hybrid delivery | Predictive governance with adaptive execution | Selecting the right approach for the context |
| Stakeholders | Identify, analyze, engage, communicate, manage expectations | Resistance, influence, communication gaps |
| Risk and issues | Future uncertainty versus current problem | Prevent, mitigate, escalate, or act |
| Change | Impact analysis, approvals, baselines, backlog refinement | Whether to use change control or adaptive reprioritization |
| Business environment | Value, benefits, compliance, organizational change | Aligning project decisions to business outcomes |
| Quality | Prevention, acceptance, inspection, continuous improvement | Root cause, quality standards, corrective action |
| Procurement | Vendor performance, contracts at a practical level, procurement decisions | What to do when a supplier affects delivery |
Agile, predictive, and hybrid decision practice
Many PMP questions require you to recognize the delivery context before choosing the best action.
| If the scenario emphasizes… | Likely context | Practice decision |
|---|
| Approved baseline, formal change request, control board, detailed plan | Predictive | Analyze impact before approving changes |
| Backlog, iteration, product owner, retrospective, self-organizing team | Agile | Facilitate, remove impediments, support team ownership |
| Fixed governance with iterative delivery | Hybrid | Respect governance while using adaptive execution practices |
| Stakeholder wants a new feature midstream | Depends on context | Use change control in predictive; backlog prioritization in agile |
| Team conflict blocks progress | Any context | Facilitate resolution before escalating unless policy or urgency requires escalation |
| Risk becomes real | Any context | Treat it as an issue and implement the appropriate response |
Missed-question review method
A missed-question log is one of the highest-value PMP study tools. Do not only record the topic. Record the decision error.
Missed-question log fields
| Field | What to write |
|---|
| Date | When you answered it |
| Topic | Risk, change, agile, stakeholder, quality, etc. |
| Delivery approach | Predictive, agile, hybrid, unclear |
| Question trigger | What made the question difficult |
| Your answer | The option you chose |
| Correct answer | The option supported by the rationale |
| Error type | Knowledge gap, misread, wrong role, wrong approach, timing, over-escalation |
| Rule to remember | One sentence you can apply to future questions |
| Recheck date | When you will retry or review the pattern |
Error categories and fixes
| Error pattern | Example | Fix |
|---|
| Wrong delivery approach | Applying formal change control to an agile backlog scenario | Identify context before reading answer choices |
| Over-escalation | Sending issues to sponsor before attempting team-level resolution | Prefer collaboration and problem-solving first when appropriate |
| Acting before analyzing | Approving a change without impact review | Look for assess/analyze/review before act/implement |
| Ignoring stakeholder engagement | Solving communication issues with documentation only | Consider engagement, facilitation, and expectation management |
| Confusing risk and issue | Treating an occurred problem as a future uncertainty | If it has happened, manage it as an issue |
| Choosing the most technical answer | Focusing on tools instead of project leadership | Choose the option that best supports project outcomes and team/stakeholder alignment |
| Memorizing terms only | Knowing vocabulary but missing scenarios | Write decision rules and practice mixed questions |
Review cycle
| When | What to review |
|---|
| Same day | Every missed and guessed question |
| Next day | Top 5 decision errors from the prior session |
| End of week | Repeated patterns and weak topics |
| Final week | Only high-yield patterns and frequently missed decisions |
Timed mock exam strategy
Timed mocks should be used after you have enough foundation to benefit from the results. Do not wait until the final day.
| Preparation length | When to use timed mocks |
|---|
| 7 days | One full mock or long timed set around day 3 or 4, if stamina allows |
| 14 days | One checkpoint set mid-plan and one full mock or long simulation near days 12-13 |
| 30 days | One mock around day 21 and another around day 27 |
| 60 days | First full mock around week 7, second in week 8 |
| 90 days | First full mock in month 3, then additional timed sets as needed |
How to review a mock
| Step | Action |
|---|
| 1 | Take a short break before reviewing |
| 2 | Review missed questions first |
| 3 | Review guessed correct answers next |
| 4 | Review slow questions even if correct |
| 5 | Group errors by pattern |
| 6 | Choose no more than 3 repair priorities |
| 7 | Do targeted practice before taking another mock |
A mock exam is only useful if you review it deeply. Taking multiple mocks without explanation review often repeats the same mistakes.
Pacing and question-handling routine
Use a consistent routine during practice so it becomes automatic on exam day.
For each PMP scenario question
- Identify your role.
- Identify the delivery approach: predictive, agile, hybrid, or unclear.
- Identify the problem timing: before it happens, happening now, or after it happened.
- Look for the best next action, not just a technically correct action.
- Eliminate answers that:
- Escalate too early
- Ignore stakeholder or team engagement
- Act without analysis
- Violate the delivery approach
- Are too passive when action is required
- Choose the option that best supports project value, team effectiveness, and appropriate governance.
If you are stuck between two answers
| Ask this | Why |
|---|
| Which answer happens first? | PMP questions often test sequence |
| Which answer fits the delivery approach? | Agile and predictive use different control mechanisms |
| Which answer solves the root problem? | Some options treat symptoms |
| Which answer keeps the project manager in the right role? | Avoid answers that abdicate responsibility |
| Which answer best protects value and stakeholders? | The exam often favors business-aware judgment |
When to stop adding new material
Stop adding major new resources when you enter your final review window.
| Time before exam | What to stop | What to continue |
|---|
| 14 days | Stop changing your main study source unless it is clearly failing | Practice, explanation review, weak-area repair |
| 7 days | Stop broad reading and new courses | Timed sets, missed-question log, final summaries |
| 48 hours | Stop heavy new topics and exhausting mocks | Light review, confidence questions, logistics |
| Day before | Stop cramming late into the night | Rest, pacing plan, light notes |
New material late in the process can lower confidence. Your final improvement usually comes from recognizing repeated mistakes and applying better decision rules.
Exam-readiness checks
Readiness is not guaranteed by any single practice score. Use several indicators together.
| Readiness indicator | What you want to see |
|---|
| Mixed practice consistency | Performance is stable across topic areas, not dependent on one question type |
| Explanation quality | You can explain why the correct answer is best and why your answer was weaker |
| Delivery approach recognition | You can quickly identify predictive, agile, and hybrid context clues |
| Timing | You can complete timed sets without rushing the final portion |
| Error trend | Repeated error categories are decreasing |
| Confidence | You are not relying on memorized question wording |
| Stamina | You can sustain focus through long timed practice |
| Final-week discipline | You can review without panic-adding new material |
Final-week checklist
| Task | Done |
|---|
| Review top missed-question patterns | |
| Complete one timed mock or long timed set early enough to review it | |
| Revisit agile, predictive, and hybrid decision differences | |
| Review stakeholder, risk, issue, and change scenarios | |
| Review key formulas and interpretation if included in your prep materials | |
| Practice reading long scenario questions efficiently | |
| Prepare exam appointment logistics | |
| Decide your pacing and break strategy | |
| Stop heavy new study before the final day | |
| Sleep adequately before the exam | |
Practical next step
Choose the schedule that matches your exam date, then start with a mixed PMP diagnostic practice set. Use the results to build your missed-question log, select your weakest three areas, and begin timed scenario practice with full explanation review.