PMP 12-Week Study Plan

Build the plan around the July 2026 outline

This 12-week schedule is for candidates preparing for the PMP exam introduced on 9 July 2026. It follows People (33%), Process (41%), and Business Environment (26%) rather than the prior 42/50/8 weighting. The current outline covers predictive, adaptive, and hybrid approaches, and the exam includes interactive tasks in addition to conventional response items. Plan five study sessions a week if that fits your life; each session can be 45 to 75 minutes. If you have fewer hours, preserve the order and extend the calendar.

Before Week 1, download the July 2026 ECO, identify your likely appointment window, and gather your current notes and practice resources. Do not schedule around an assumed seat until PMI has approved your application and the delivery provider shows availability. A reasonable weekly rhythm is three learning sessions, one scenario session, and one review session. Keep at least one rest day and a catch-up block so one missed evening does not collapse the plan.

Week 1: diagnose and set up

Take a baseline set that samples all three domains. It is a diagnostic, not a pass prediction. For every missed or guessed item, record the ECO task, the decisive fact, the answer you chose, and why it failed. Separate knowledge gaps from reading mistakes, weak trade-off judgment, and unfamiliar item interactions. Make a tracker with 26 task rows and columns for first study, practice, confidence, and revisit date.

Read the exam format: 180 items, 170 scored and 10 unscored, 240 minutes, and two 10-minute breaks. Learn the current interaction types represented in your available resources. A text-based set may help you understand concepts, but it cannot reproduce every practicum or interface task. Reserve a short session this week for review of the task list and the exam clock.

Week 2: common vision, conflict, and leadership

Study People tasks on developing a common vision, managing conflict, and leading the project team. For each scenario, identify the goal, the people involved, the source of misunderstanding or conflict, and the project manager’s authority. Practice distinguishing a technical disagreement that needs evidence from harmful conduct that needs clear intervention. Write down when facilitation, coaching, a directive decision, or escalation fits the facts.

Complete one short set after each topic. Do not simply memorize “collaborate first.” A safety issue, urgent threat, or explicit governance rule may require immediate action. In your review, explain why your action addresses the cause and why the nearest distractor is premature, too broad, or outside the project manager’s authority.

Week 3: stakeholder engagement and communication

Cover stakeholder engagement, alignment and management of expectations, knowledge transfer, and communication planning. Map each stakeholder’s interest, influence, information needs, and appropriate involvement. Practice scenarios where a sponsor, customer, team, and operations group define success differently. Your response should surface the mismatch and establish a shared decision or communication path rather than letting incompatible expectations persist.

For knowledge transfer, think beyond a closeout document. Ask what the receiving person must be able to do, what context they need, and when transfer must happen. Practice choosing a communication channel based on urgency, confidentiality, language, and audience. Add missed questions to your tracker by task, not just under a broad People heading.

Week 4: integrated planning and scope

Study Process tasks for integrated planning, delivery approach, dependencies, project scope, and stakeholder agreement. Practice choosing predictive, adaptive, or hybrid methods from scenario conditions. Stable requirements and formal dependencies can support detailed baselines; uncertainty and frequent user feedback may support adaptive cycles. Neither method removes the need for planning. Scope should be clear enough to guide work and flexible only within its agreed governance.

Work one case in which a requested change affects multiple plans. Trace the effects on schedule, cost, resources, quality, procurement, and intended benefits. Do not change the baseline or backlog silently. Identify the person or group authorized to decide, gather needed impact evidence, and communicate the result.

Week 5: value, delivery, and resources

Study value-based delivery and resource planning. Identify who defines value, how it can be measured, what work could be delivered incrementally, and how stakeholder feedback changes priorities. Distinguish an output from a benefit: completing a feature is not proof that it improves an outcome. Practice a case where user feedback changes priority and a different case where a regulatory commitment limits available options.

For resources, estimate what skills and capacity are needed, then address availability and constraints. A schedule that assumes a scarce specialist is available without confirmation is not a reliable plan. Practice balancing resource optimization against burnout, quality, and delivery sequence. When a resource conflict exceeds your authority, prepare the decision information and use the governance route.

Week 6: procurement, finance, and quality

Cover procurement strategy, contract types, negotiations, supplier management, financial needs, reserves, quality requirements, regulatory compliance, and cost of quality. Use cases where a vendor offers a faster option with a different risk allocation, or where actual spending varies from forecast. Identify which party owns each obligation and what the agreement says before recommending a change.

For a financial variance, examine its cause and forecast rather than reporting only the amount spent. For a quality issue, determine acceptance criteria, severity, and whether the process or product needs correction. Quality is planned and reviewed throughout delivery, not added only in final inspection. Log any questions where you selected a response without checking the contract or requirement.

Week 7: schedule and project status

Study schedule preparation, dependencies, milestones, benchmarks, baselines, schedule variation, metrics, and project artifacts. Practice reading a chart or status report without assuming the trend explains its own cause. If scope increases while completed work remains steady, the gap may widen without a productivity decline. Identify what is measured, the time period, and any change to the denominator.

Make a one-page status brief from a fictional case: current progress, forecast, major variance, evidence, decisions needed, and owner. Keep the message accurate and tailored to its audience. Practice a case where you must decide whether to correct data, investigate a dependency, or escalate a material variance.

Week 8: closure and Business Environment foundations

Study project closure and the first Business Environment tasks: governance, compliance, and change control. Closure includes completion criteria, stakeholder acceptance, transition readiness, lessons, contracts, financials, and release of resources. A deliverable is not ready to transition merely because development is complete; confirm operational ownership and required acceptance.

For governance, map the decision rights and required reviews. For compliance, treat legal and policy obligations as constraints to understand and meet, not optional preferences. For a proposed change, assess impact and follow the defined authority. Write three short cases where the same request needs a different next action because one is an adaptive backlog choice, one requires formal approval, and one conflicts with compliance.

Week 9: issues, risk, improvement, and change

Cover impediments and issues, risk, continuous improvement, organizational change, and external business changes. Distinguish a risk, which may occur, from an issue that is already affecting work. Remove a blocker within your authority or escalate with evidence when it needs help. For risk, identify cause, probability, impact, owner, response, and trigger. For an external change, connect the new regulation, technology, geopolitical condition, or market shift to scope or backlog.

Practice organizational adoption cases. Resistance can signal poor readiness, training, incentives, or solution fit. Engage affected groups and test the cause instead of labeling all resistance as unwillingness. For continuous improvement, apply lessons to the current project and, where appropriate, update the process or organizational asset.

Week 10: timed mixed practice

Take a fresh mixed set spanning all domains and methods. If you have access to a full-length practice exam aligned with the July 2026 outline, use it to test endurance and section transitions. Do not call a text-only multiple-choice test a complete simulation of interactive and practicum formats. During practice, track time by section, not only a final total.

Review every wrong and guessed answer. For each, write the fact that should have controlled your decision and the reason the best alternative fails. Sort recurring errors into: content not known, question misread, wrong actor or authority, unsupported assumption, premature escalation, poor method fit, or time management. Choose the next week’s review from that list.

Week 11: targeted repair and original case drills

Spend most sessions on your three weakest task clusters. Use new scenarios so you are not recalling a memorized answer. Create one case that connects two or three domains, such as a supplier delay that threatens value and raises a compliance issue. State the decision, the evidence, who must be involved, and how you will communicate the outcome. Add one session for matching, ordering, multiple response, or graphic interpretation where your tools support them.

Review your notes with active recall. Close the outline and explain each weak task in a few sentences, then compare your explanation with the ECO. If it remains vague, return to the topic and produce a concrete example. Avoid spending the week rereading chapters you already understand because they feel reassuring.

Week 12: readiness, taper, and logistics

In the first part of the week, complete one final timed mixed set or representative case session. Review only the resulting errors and core task map. Confirm you can explain the current domain weights and item format, and that you have practiced the question interactions available to you. Do not use a single percentage as a pass guarantee; PMI does not publish a fixed passing percentage.

In the final days, reduce heavy new study. Confirm your Pearson appointment, delivery mode, identification requirements, travel or online setup, and any accommodations. The exam has two 10-minute breaks, and a section cannot be reopened after you review it and begin the break. Plan meals, sleep, and arrival around the appointment. If your final practice still reveals broad gaps, consider moving the exam within the rules rather than treating the 12-week schedule as proof of readiness.

How to adapt this calendar

If you have less time each week, keep the same sequence and extend the plan. If you already have a strong diagnostic in a topic, shorten the learning block but still test it with fresh questions. Do not remove Business Environment merely because it is less familiar or because your prior study used the old outline. If you have many years of project experience, keep practicing method choice and authority: familiar workplace habits can conflict with the facts in a question.

A missed week is a signal to revise the calendar, not to double every session. Preserve mixed practice and error review, then reduce low-value rereading or move the appointment. Candidates with accommodations may need additional scheduling lead time. Study time is personal; this plan supplies sequence and checkpoints rather than a universal hour requirement.

A weekly review template

At the end of each week, record four things: ECO tasks completed, fresh-question performance and timing, repeated error types, and the next two tasks to revisit. Add one sentence for what changed in your reasoning. For example, “I now check who owns the product backlog before choosing a scope action.” This is more useful than writing only “studied agile.” Carry one unresolved question into the next week rather than hiding it in a large notes file.