Start with the July 2026 PMP exam—not an old study calendar
PMI introduced the current PMP examination on 9 July 2026. The public certification page lists 180 questions in 240 minutes, with two 10-minute breaks. Its domain blueprint weights People at 33%, Process at 41% and Business Environment at 26%. Those percentages describe emphasis, not isolated chapters. A scenario about an unhappy sponsor may require stakeholder judgment, change control, governance awareness and value thinking at the same time.
The Exam Content Outline is the most useful planning source because it identifies what a candidate is expected to do. Use the domain tasks and enablers to test whether your material covers the current examination. Avoid building a calendar around chapter counts from an older book, a recalled question bank or a provider's marketing labels. Your goal is not to consume the most content. It is to make defensible project-leadership decisions across predictive, adaptive and hybrid situations.
This page assumes you are checking or have confirmed the application route and formal training requirement. Use the complete PMP certification roadmap for eligibility, training evidence, application, audit and payment steps. Then return here to plan the learning and practice work.
Build a schedule from evidence, not enthusiasm
Eight weeks is a planning frame, not a promise. It works best for an eligible candidate who has completed appropriate training, can reserve focused weekly time and has enough project context to connect the concepts. If your diagnostic reveals broad gaps or your calendar cannot support deliberate practice, extend the plan. A twelve-week plan completed consistently is more useful than an eight-week plan that repeatedly slips.
Choose a real weekly capacity
Budget roughly eight to twelve focused hours each week. Count work that produces learning evidence: explaining a concept, solving a scenario, reviewing distractors, updating an error log or completing a simulation. Passive video playback while multitasking is exposure, not automatically mastery. Put recurring sessions on the calendar now, including the full simulations in weeks seven and eight. Those long blocks are hardest to create at the last minute.
Create four preparation tools
Exam map
List the three domains, their current weights and major tasks. Add predictive, adaptive and hybrid signals across the map so delivery approach remains visible.
Error log
Record the decision you made, why it failed, the missing concept, the distractor pattern and the action that will repair it. Do not copy only the right letter.
Decision sheet
Keep concise sequences for conflict, change, risk, quality, stakeholder resistance and governance. Rewrite it as your reasoning improves.
Assessment record
Track fresh-set accuracy, time, domain balance, delivery approach and confidence calibration. Separate a correct explanation from a lucky guess.
Take a diagnostic correctly
Use a mixed, unseen set of 40–60 questions under light time pressure. Do not pause to research, and do not interpret the result as a predicted exam outcome. Mark confidence before reviewing. A high-confidence wrong answer exposes a stronger misconception than a low-confidence miss. A low-confidence correct answer may be a guess that needs the same review. The result should determine where week two and week three need emphasis.
If you have not studied project management recently, begin with the eight-chapter PMP course material and the PMP training curriculum. These resources organize the learning path; they do not themselves award a credential or substitute for formal training evidence.
What to learn, practise and produce each week
Each week has five parts: a goal, targeted learning, scenario practice, a tangible output and a checkpoint. Preserve the structure when you change the pace. If you stretch the plan to twelve weeks, split demanding weeks rather than dropping mixed practice or review.
Map the exam and establish a truthful baseline
Goal: Understand what the current exam measures, then identify the reasoning gaps that deserve your time.
Read the July 2026 Exam Content Outline at domain, task and enabler level. Do not turn the outline into a memorization list. Translate each task into a question: What evidence would a project leader review, whom would they involve, and what should happen before action?
Take a short, mixed diagnostic without looking up answers. Record the domain, delivery approach, decision type and confidence for every miss. A low first score is useful data; it is not a verdict on your ability.
Refresh the project life cycle, value delivery, tailoring and the difference between predictive, adaptive and hybrid work. Build one page that connects principles, people, delivery work and business outcomes rather than treating them as separate books.
Practice: Complete 40–60 mixed questions in two sessions. Review all answers, including correct guesses. For every item, write the problem state, the best next action and why the attractive distractor acts too early, skips analysis or ignores collaboration.
Weekly output: A baseline table with domain accuracy, timing, confidence and three repeated reasoning errors; a calendar containing every study and simulation block for the next seven weeks.
Move forward when: You can explain the exam blueprint in plain language and name your top three gaps without saying only that you need to study everything.
Build People-domain judgment
Goal: Move from generic leadership slogans to situation-specific choices about teams, conflict, stakeholders and performance.
Compare servant, situational and directive leadership. The exam rarely rewards a single style in every context. Ask whether the team is capable, whether a safety or compliance emergency exists, and whether the project manager has enough information to intervene.
Study conflict sources and responses: collaborate or problem-solve for durable resolution, compromise when a workable middle ground is appropriate, accommodate when the relationship or other party's need matters more, force when urgent authority is justified, and avoid only when delay is deliberate and safe.
Connect stakeholder identification, engagement assessment, communications planning, emotional intelligence, mentoring, knowledge transfer, team ground rules and virtual-team needs. Separate sending information from gaining participation and commitment.
Practice: Work through 60–80 People scenarios. Before viewing options, state the humane and professionally responsible sequence: listen, investigate, facilitate, agree, act and verify. Then check whether the question changes that sequence because of urgency, regulation or an already-completed analysis.
Weekly output: A one-page leadership decision map plus five rewritten examples from your error log showing how the correct response changes when urgency, authority or team maturity changes.
Move forward when: You can distinguish coaching from directing, communication from engagement, and conflict diagnosis from conflict resolution without relying on keywords alone.
Connect Process decisions across delivery
Goal: Understand how scope, schedule, cost, quality, resources, communications, risk, procurement and integration influence one another.
Trace a predictive change from request through impact analysis, change control, authorized plan updates, communication, implementation and verification. Contrast a change request with corrective action, preventive action and defect repair. The label matters less than the controlled sequence.
Practise schedule networks, critical path, total float, schedule compression and resource effects. Calculate only after identifying the decision the number supports. A formula result is evidence, not the final management action.
Connect risk identification, qualitative analysis, response ownership, reserves, triggers and issue management. An uncertain event belongs in the risk process; a problem that has occurred needs issue ownership and action. Review quality planning, process assurance and deliverable control using the same evidence-first approach.
Practice: Complete 80 Process questions in topic clusters, then finish with a 25-question mixed set so you cannot predict the subject from the order. Explain when to update the risk register, issue log, change log, lessons learned register and stakeholder information.
Weekly output: One end-to-end change-control flow, one risk-to-issue example, one schedule-recovery calculation and a document-purpose table created from your own words.
Move forward when: Given a new request or performance problem, you can identify what to assess, which plan or evidence source matters, who authorizes action and what should be updated afterward.
Choose predictive, adaptive and hybrid responses
Goal: Recognize the delivery context and reason within it instead of applying agile vocabulary to every scenario.
Compare uncertainty, requirement stability, feedback frequency, release options, regulatory constraints, contracting model and cost of change. These signals help explain why a team chooses predictive, adaptive or hybrid work; no single signal decides the entire approach.
Review product vision, roadmap, product backlog, refinement, iteration planning, daily coordination, review, retrospective, Definition of Done, acceptance criteria and release planning. Separate the ordered product work from the team's selected iteration work and from the standard that makes completed work releasable.
Study hybrid governance as intentional tailoring, not an accidental mixture. A program may retain funding gates, milestones or regulated evidence while delivery teams use short feedback cycles. The right answer preserves necessary governance and still enables learning.
Practice: Complete 80 adaptive and hybrid scenarios. For each miss, label whether you misunderstood the approach, the role, the artifact, the event or the response sequence. Re-answer the question after changing one condition—for example, make the requirement regulated or the release reversible—and explain whether your choice changes.
Weekly output: A delivery-approach decision table and four worked scenarios: stable construction scope, uncertain digital product, regulated hybrid delivery and an operational improvement flow.
Move forward when: You can explain why a response fits the scenario's uncertainty, governance and feedback needs rather than saying only that agile is flexible or predictive is planned.
Link Business Environment to measurable value
Goal: Connect compliance, governance, organizational change, sustainability and external conditions to project decisions and outcomes.
Study benefits, value measures, business cases, benefits-management responsibilities and outcome verification. A delivered output is not automatically a realized benefit. Ask who owns adoption, how value is measured and when the organization can observe it.
Compare project governance with day-to-day management. Review escalation thresholds, decision rights, audit evidence, regulatory obligations, organizational policies and external changes. Compliance is not a reason to bypass collaboration; it changes the constraints and evidence the team must respect.
Review organizational change, stakeholder adoption, operational transition, sustainability and responsible use of technology, including AI. Treat an AI-generated forecast or summary as an input that requires appropriate data controls, human judgment, transparency and verification—not as an unquestionable decision.
Practice: Complete 60–80 Business Environment and mixed value scenarios. Explicitly identify the expected benefit, the affected stakeholders, the governance constraint and the evidence used to confirm success.
Weekly output: A benefits traceability example, a compliance escalation example, an adoption plan and a responsible AI decision checklist tied to a fictional project.
Move forward when: You can move from output to outcome, recognize when governance must be consulted and explain how a project leader responds to an external change without inventing authority.
Integrate domains through mixed scenarios
Goal: Stop studying chapters in isolation and practise the cross-domain decisions that make situational questions difficult.
Review only the gaps supported by your error log. If risk questions are weak because you confuse a threat with an issue, repair that distinction. If stakeholder questions are weak because you act before understanding resistance, practise engagement diagnosis—not another broad reread.
Build decision sequences for recurring situations: team conflict, a late scope request, an emerging risk, a failed quality check, a vendor problem, declining stakeholder support, a regulatory change and benefits that are not materializing.
Practise pace without sacrificing comprehension. Read the final question first when a stem is long, identify the current state and notice whether analysis or authorization has already happened. Eliminate options that solve a different problem or perform a later step prematurely.
Practice: Complete two 60-question timed mixed sets on separate days. Use the same breaks, workspace and interruption controls planned for the full simulation. Spend at least as long reviewing as answering.
Weekly output: A ranked remediation queue with no more than five active gaps, each linked to a concept source, a practice task and a date for retest.
Move forward when: Your misses are becoming specific and correctable—such as missing that impact analysis was already complete—rather than broad statements such as bad at Process.
Run a full simulation and remediate precisely
Goal: Test knowledge, pacing, endurance, break use and decision consistency under realistic conditions.
Choose a fresh 180-question practice set. Block 240 minutes plus break and setup time. Remove notifications, use the identification and calculator approach you expect on exam day, and practise two 10-minute breaks without reviewing closed sections.
Record time at the end of each 60-question section. Do not chase a universal minute target; find a pace that leaves enough review time without rushing the final section. Mark uncertain items selectively rather than flagging most of the exam.
After the simulation, separate knowledge, interpretation, sequence, approach, calculation, confidence and fatigue errors. Review explanations and source concepts before retesting. A score without diagnosis does not tell you what to do next.
Practice: Take one complete simulation early enough in the week to allow repair. Use the next sessions for targeted 15–30 question sets, then retest with new questions rather than memorizing the same answers.
Weekly output: A simulation report containing section timing, domain patterns, approach patterns, confidence calibration, fatigue observations and the exact repair plan for week eight.
Move forward when: You finish within time, can maintain a stable decision process after the second break, and understand why every high-priority miss occurred.
Validate readiness and protect exam-day performance
Goal: Confirm stable reasoning, close only high-value gaps and arrive rested with logistics under control.
Retest the limited gaps from week seven. Use short mixed sets and one final substantial assessment only if it will inform a decision and leave recovery time. Avoid cramming a new source because it uses different terminology or promises secret questions.
Review concise personal notes: decision sequences, document purposes, formulas with interpretation, delivery-approach signals, common traps and exam logistics. Your notes should trigger reasoning, not reproduce a textbook.
Confirm the current appointment rules, acceptable identification, check-in time, route or system requirements, workspace, breaks and rescheduling policy with PMI and the exam provider. Protect sleep, food, hydration and a calm arrival buffer.
Practice: Use 30–60 fresh mixed questions to verify stable performance. Stop intensive practice early enough to rest. On the final day, review only your short decision sheet and logistical checklist.
Weekly output: A go/no-go decision supported by multiple assessments, balanced domain evidence, pacing, reasoning quality and confirmed logistics—not by hope or one unusually high score.
Move forward when: You can explain unfamiliar scenarios, maintain pace and identify your assumptions. If evidence remains inconsistent, rescheduling can be a professional risk decision rather than a failure.
Three weekly schedule patterns
The right pattern is the one you can repeat. Keep concept study close enough to practice that you can apply it, but leave enough time between a diagnostic and retest to complete genuine remediation. Protect breaks and sleep; fatigue can make a good study plan look ineffective.
Working professional: 9 hours
Tuesday: 75 minutes of one concept cluster. Thursday: 75 minutes of scenario practice. Friday: 60 minutes of error review. Weekend: two hours of connected learning and three hours of assessment plus review. Use commute or lunch time only for light recall, not difficult scenario decisions.
Weekend-led: 10 hours
Weekdays: three 45-minute sessions for retrieval and targeted questions. Saturday: three hours of concept work with practical examples. Sunday: four to five hours for a timed set and review. Split the Sunday block when concentration quality falls.
Intensive learner: 14 hours
Use four two-hour weekday blocks and one six-hour weekend block. Increase fresh scenarios and explanation work, not repeated videos. Keep at least one low-load day. More hours help only while attention and reasoning remain deliberate.
Twelve-week extension
Split People, Process and adaptive or hybrid study into two weeks each. Keep Business Environment connected to value and governance, then preserve the final three weeks for integration, simulations and readiness. Do not delay all timed practice until the end.
Do not double the next week's workload automatically. Preserve the highest-value outputs: current outline coverage, mixed scenarios, detailed review and full simulation. Move the target date or extend the calendar when compressing would remove validation.
Use a repeatable decision process instead of searching for magic keywords
Many PMP questions provide several actions that sound professional. The challenge is identifying the best response for the current state. Use the following sequence during practice until it becomes natural. It is a reasoning aid, not a rule that overrides an urgent safety, legal or compliance obligation.
Identify the present state
What has already happened? Is the situation an uncertain risk, a current issue, a requested change, a quality failure, a conflict, a stakeholder-engagement gap or a governance decision? Notice which analysis or authorization the stem says is already complete.
Name the delivery context and constraint
Is the work predictive, adaptive or hybrid? What authority, contract, regulation, team agreement or organizational policy limits the response? The same problem can require a different next step in a self-managing product team and a regulated predictive program.
Choose the correct sequence
Unless urgent protection is required, understand before solving, collaborate before imposing, follow the agreed process before bypassing it, and verify after acting. Reject options that jump to escalation, replacement, scope change or communication before the situation is understood.
Test each distractor
Ask whether it is too early, too late, outside the project manager's authority, solving a different problem, ignoring a stakeholder, bypassing governance or merely recording without acting. This creates an explanation you can transfer to a new question.
Original scenario 1: late scope request
A sponsor asks the predictive project team to include an additional reporting feature after the scope baseline is approved. The feature is valuable, and the sponsor says the schedule cannot move. The project manager should not quietly direct the team to add it, reject it without analysis or update the baseline immediately. The useful next step is to clarify and document the request, assess impacts and move it through the agreed change-control process. Authorization determines whether the plans and baseline change. The sponsor's seniority does not erase integrated decision making.
Original scenario 2: recurring iteration defects
An adaptive team repeatedly discovers similar defects during review. Adding more final inspection may detect defects later but does not address the recurring cause. The team should make the problem visible, investigate the process and use the retrospective or an appropriate improvement activity to strengthen working agreements, automated checks or the Definition of Done. The product owner may clarify acceptance, but quality remains a shared delivery responsibility.
Original scenario 3: stakeholder resistance to adoption
A department manager attends status meetings but discourages staff from joining transition workshops. Sending more status reports treats a participation problem as an information problem. The project manager should understand the manager's concerns, assess engagement, connect the change to operational impacts and work on a tailored involvement plan. Escalation may become necessary if agreed responsibilities remain blocked, but listening and analysis usually precede it.
Turn every mistake into a testable repair
An error log should shorten preparation by revealing repeated patterns. It should not become a transcript of hundreds of questions. One row per important decision is enough. Review the log weekly, merge duplicates and retire a gap only after you can solve fresh examples.
| Field | What to record | Useful example |
|---|---|---|
| Situation | The actual management problem, without option wording | Approved predictive scope; sponsor requests a late feature |
| Your decision | Why your selected action seemed right | Implement because sponsor has authority and value is clear |
| Reason it failed | The missed process, evidence or sequence | Skipped impact analysis and integrated change control |
| Distractor pattern | Too early, too late, wrong authority or wrong problem | Too early and outside the agreed authorization sequence |
| Repair action | Specific study and new practice work | Draw change flow; solve five fresh change scenarios Friday |
| Retest evidence | Date and result on unseen situations | 5/5 with explanations; verify again in next mixed set |
Classify errors by knowledge (you did not know the concept), interpretation (you misread the state), sequence (you chose a valid later action), approach (you applied predictive logic to adaptive work or the reverse), authority (you acted outside the role), calculation, confidence or fatigue. Different errors need different repairs. Another chapter may fix knowledge; it will not automatically fix rushing or overconfidence.
Use five full sets without memorizing them
ITCertPath provides five independently written 180-question practice sets. They are learning resources based on the public outline, not official, copied, recalled or confidential PMI questions. Preserve their diagnostic value by assigning a purpose to each set.
Set 1 · baseline
Use selected mixed questions in week one or take the full set if you already completed formal learning. Capture time, confidence and domain patterns.
Open PMP mock 1Set 2 · integration
Use after People, Process and delivery-approach study. Confirm that concepts transfer when the topic is not announced.
Open PMP mock 2Set 3 · first simulation
Reserve for a complete 240-minute run with planned breaks. Review pacing and fatigue as carefully as the score.
Open PMP mock 3Set 4 · remediation check
Use fresh sections to confirm that week-seven repairs work on unfamiliar wording and connected scenarios.
Open PMP mock 4Set 5 · final validation
Keep the last set unseen until readiness evidence is stable. Take it early enough to review and rest before the real exam.
Open PMP mock 5Review rule
Review every wrong answer, every guess and every correct answer with weak reasoning. Return to the concept, then retest using a different scenario.
Review course materialThird-party scores are not an official PMI pass prediction. Question style, difficulty, coverage and scoring vary. Use several signals: fresh-set stability, domain balance, pacing, confidence calibration, unfamiliar-scenario explanations and the ability to recover after a difficult section.
What makes an eight-week plan fail
Collecting sources instead of learning
Switching among books, videos and question banks creates activity without a stable mental model. Choose one current primary learning route, use PMI's outline as the map and add a second explanation only when a defined gap remains.
Chasing memorized questions
Repeated wording can produce confidence without transferable judgment. Use original scenarios, explain distractors and change scenario conditions. Do not use copied dumps or confidential exam content.
Applying one rule everywhere
Advice such as never escalate or always collaborate ignores urgency, safety, law, authority and completed analysis. Learn the default sequence and the conditions that legitimately change it.
Ignoring Business Environment
Its current 26% weight is substantial, and value, governance, compliance, adoption and external change connect with other domains. Do not postpone it to the final weekend.
Reviewing only wrong answers
A correct guess can preserve a misconception. Review low-confidence correct items and high-confidence misses, then calibrate whether your confidence matches your reasoning.
Taking simulations without recovery
A full mock is mentally demanding. Schedule review and remediation before the next one. Back-to-back scores without repair mainly measure the same gaps and growing fatigue.
Leaving logistics until exam day
Identification, check-in, travel, system requirements, workspace and appointment policies affect performance. Confirm them from current official instructions during week eight.
Treating study hours as a guarantee
Time is an input, not evidence of mastery. Track explanations, fresh scenarios, balanced performance and controlled pace. Formal training hours and personal study time also serve different purposes.
Make the exam decision with multiple signals
No practice provider can guarantee a pass, and PMI does not publish a single third-party mock percentage that proves readiness. Use a balanced decision. One strong score after repeated exposure is weaker evidence than several stable results on unseen questions with clear explanations.
| Signal | Useful evidence | Warning sign |
|---|---|---|
| Concept coverage | Current outline mapped; weak tasks repaired and retested | Entire domains or approaches postponed |
| Scenario reasoning | Can explain the state, sequence and distractor failures | Depends on remembered keywords or answer patterns |
| Fresh performance | Stable across multiple unseen timed sets | High only on repeated questions |
| Balance | No persistent domain or delivery-approach collapse | Overall score hides a major weak area |
| Pace and endurance | Completes 180-question simulation with controlled breaks | Final section becomes rushed or random |
| Confidence | High confidence usually matches sound reasoning | Many high-confidence errors remain |
| Logistics | Identification, check-in and appointment rules confirmed | Relies on assumptions or old instructions |
If fresh performance remains unstable, timing consistently fails or a major life event removes the final preparation window, review the current rescheduling policy and make an informed decision. Protecting a well-supported attempt is not the same as avoiding the exam indefinitely.
PMP study-plan questions, answered clearly
Is eight weeks enough to prepare for the PMP exam?
Eight weeks can be workable for an eligible candidate who has completed suitable training, understands core project-management concepts and can protect roughly eight to twelve focused hours each week. It is not a guarantee or a universal duration. Extend the plan when the diagnostic shows broad gaps, work or family commitments make the schedule unrealistic, or timed scenario practice remains inconsistent.
How many hours should I study for PMP each week?
This plan uses about eight to twelve focused hours per week, divided among concept learning, scenario practice and detailed review. Someone with strong recent training may need less, while a candidate returning after a long gap may need more. Track useful outputs and corrected reasoning rather than counting passive reading time as proof of readiness.
Should I study People, Process and Business Environment separately?
Use focused blocks to repair specific concepts, but add mixed practice every week. Current PMP scenarios often connect a people issue, a delivery process and a business constraint. By week six, most practice should be mixed so that the subject is not revealed by the order of the questions.
How many full PMP mock exams should I take?
Quality of review matters more than collecting a large number of scores. This plan uses a baseline assessment, timed mixed sets and at least two full simulations when time permits. ITCertPath provides five independent 180-question practice sets, so candidates can preserve fresh sets for validation instead of repeating one bank until the answers feel familiar.
What score do I need before scheduling the PMP exam?
PMI does not publish a simple universal passing percentage for candidates to reproduce with third-party mock scores, and practice products differ in difficulty and scoring. Look for stable results across fresh timed sets, balanced performance across domains, sound explanations for unfamiliar scenarios, controlled pacing and fewer high-confidence errors. Treat any provider score threshold as guidance, not an official PMI rule.
How should a working professional use this plan?
Protect shorter weekday sessions for one defined task and a longer weekend block for integrated practice. For example, use two 75-minute weekday concept sessions, one 60-minute error-review session and a three-to-four-hour weekend assessment and review block. Put full simulations on the calendar before starting the plan so routine work cannot quietly consume them.
Are ITCertPath mock questions official PMI exam questions?
No. ITCertPath practice questions are independently written learning scenarios based on the public Exam Content Outline. They are not copied, recalled, confidential or official PMI exam items. Use them for diagnosis and decision practice alongside official PMI information and genuine project-management learning.
What should I do if my first mock score is low?
Do not immediately repeat the same mock. Classify each miss by domain, delivery approach and error type, then repair the smallest underlying concepts with a trusted source. Practise new targeted scenarios, explain why the distractors fail and retest with fresh items. A low diagnostic is valuable when it produces a specific remediation plan.
Does this study plan provide the 35 PMP training hours?
No. Reading this guide, using free course material and taking mock exams do not by themselves award formal training hours or a credential. Confirm that your selected training route meets PMI's current education requirements and retain the completion evidence that PMI may request.
Verify final exam details with PMI
This independent guide was published and reviewed by ITCertPath on 30 August 2026. Exam policies, appointment rules and provider materials can change. Check PMI's current instructions before applying, scheduling, paying or sitting the examination.
ITCertPath wrote this guide as a preparation framework using public PMI information and original learning examples. PMI does not sponsor, endorse or author this page. PMP is a registered mark of Project Management Institute, Inc. ITCertPath does not promise eligibility, application approval, a score or certification.
Turn the guide into a calendar today
Confirm your starting point
Check eligibility and formal training separately, read the current outline and take a mixed baseline without researching answers.
Reserve the hard-to-find time
Book weekly review blocks and the full simulations before routine commitments consume the calendar.
Study one decision at a time
Start week one, maintain the error log and judge progress through fresh explanations—not content volume.
Share your target exam date, completed training, weekly availability and current confidence. Ask an ITCertPath advisor on WhatsApp for preparation-route guidance. PMI alone controls eligibility and certification decisions.