PMI-SP — PMI Scheduling Professional Study Plan
A practical study plan for PMI Scheduling Professional (PMI-SP) candidates, with 7-day, 14-day, 30-day, and 60/90-day schedules.
This Study Plan is for candidates preparing for the PMI Scheduling Professional (PMI-SP) exam from PMI, exam code PMI-SP. It is built for working professionals who need to convert available study time into a practical schedule, with enough structure for a one-week final review and enough depth for a full 60- or 90-day preparation path.
The PMI-SP exam rewards more than terminology recall. Your preparation should move from schedule concepts into scenario judgment: schedule strategy, development, baseline control, progress reporting, risk, change, stakeholder communication, schedule compression, rolling-wave planning, and predictive, agile, or hybrid delivery contexts.
Which plan should you use?
Start by choosing the path that matches your time remaining and your current confidence. If you have not taken any practice questions yet, take a short mixed diagnostic set before choosing.
| Time available | Best plan | Daily study target | Main goal | Use this if |
|---|---|---|---|---|
| 7 days | Final review plan | 2-4 hours | Protect points, reduce mistakes, rehearse timing | You already studied and need a structured final week |
| 14 days | Focused catch-up plan | 2-3 hours | Repair weak domains and build exam rhythm | You know scheduling basics but practice results are uneven |
| 30 days | Balanced plan | 1.5-2.5 hours | Cover, practice, review, and mock-test in cycles | You want a realistic plan without rushing every topic |
| 60 days | Full preparation path | 60-90 minutes most days, longer weekends | Build content depth and timed performance | You are starting early or returning after a break |
| 90 days | Extended full path | 45-75 minutes most days, longer weekends | Slow, durable prep with spaced review | You have limited weekday time or are new to formal scheduling methods |
Do not treat any practice percentage as an official PMI passing standard. Use practice results to find weak areas, improve timing, and confirm that you can explain why the correct answer is best.
First step: run a diagnostic before building the schedule
Before starting the plan, complete a mixed diagnostic set under light timing.
| Diagnostic action | Recommended approach |
|---|---|
| Question count | 30-60 mixed PMI-SP-style questions |
| Timing | Use a timer; do not pause to research |
| Marking | Mark every question as confident, unsure, or guessed |
| Review | Review every missed and guessed question before studying new content |
| Output | Create a ranked list of your top 5 weak areas |
Classify every miss into one of these categories:
| Miss type | What it means | Immediate fix |
|---|---|---|
| Concept gap | You did not know the scheduling principle | Read the concept, then answer 5-10 targeted questions |
| Calculation error | You knew the method but made a math or sequencing mistake | Redo the problem by hand and drill similar problems |
| Scenario judgment error | You chose a technically possible answer, not the best PMI-SP answer | Compare the role, project phase, and governance context |
| Keyword trap | You reacted to one phrase and ignored the full scenario | Re-read the question stem and identify the actual decision being asked |
| Timing pressure | You rushed or overanalyzed | Practice timed sets with strict review afterward |
| Delivery-context confusion | You missed whether the scenario was predictive, agile, or hybrid | Note the planning cadence, change approach, and reporting rhythm |
PMI-SP study map
Use this map to make sure your preparation is broad enough for the PMI Scheduling Professional (PMI-SP) exam without turning study time into random reading.
| Study area | What you need to practice | Evidence you are ready |
|---|---|---|
| Schedule strategy and governance | Schedule management plan, scheduling methodology, baseline rules, calendars, update cycles, roles and responsibilities | You can choose the appropriate scheduling action before jumping to a tool or calculation |
| Schedule planning and development | Activities, dependencies, sequencing, milestones, constraints, assumptions, leads, lags, network logic | You can build and interpret a basic schedule network from a scenario |
| Estimating and resources | Duration estimating, resource availability, productivity, calendars, assumptions, estimation confidence | You can explain how resources and calendars affect schedule feasibility |
| Critical path and float | Forward pass, backward pass, total float, free float, near-critical paths | You can calculate or interpret float without confusing it with slack in the overall project |
| Schedule risk | Uncertainty, buffers, reserves, contingency, what-if analysis, risk responses | You can distinguish schedule risk from an active schedule issue |
| Monitoring and controlling | Status collection, actuals, variance, forecasting, corrective actions, trend analysis | You can select the best next action when the schedule is slipping |
| Change control | Baseline changes, approved changes, impact analysis, stakeholder approval | You do not recommend changing the baseline casually or without governance |
| Compression and recovery | Crashing, fast tracking, re-sequencing, scope or resource tradeoffs | You can compare schedule gain, cost, risk, and quality impact |
| Reporting and stakeholders | Progress reports, dashboards, escalation, communication needs by audience | You can match the schedule message to the stakeholder decision needed |
| Closeout and lessons learned | As-built schedules, actual durations, archives, performance history | You understand why schedule data is retained after delivery |
| Agile and hybrid scheduling | Releases, iterations, rolling-wave planning, backlog-driven forecasts, dependency management | You can adapt schedule reasoning to iterative and hybrid contexts |
Daily practice rhythm
Use the same rhythm on most study days. Consistency matters more than marathon sessions.
Standard 90-minute session
| Time | Activity | What to produce |
|---|---|---|
| 10 min | Recall review | Write 3-5 rules, formulas, or decision points from memory |
| 25 min | Concept study | Review one narrow topic, not an entire domain |
| 30 min | Targeted practice | Complete 15-25 questions or 3-5 calculation/scenario drills |
| 20 min | Explanation review | Log misses, guessed questions, and traps |
| 5 min | Next-session plan | Pick tomorrow’s topic based on today’s errors |
Short 30-minute session
Use this when work or travel limits your time.
- Review 5 missed-question notes.
- Do 10 timed questions on one topic.
- Log only the errors and guesses.
- Choose one fix for the next session.
Long weekend session
| Block | Activity |
|---|---|
| 45-60 min | Timed mixed practice |
| 30-45 min | Review missed and guessed questions |
| 45-60 min | Focused content repair |
| 30 min | Calculation or network logic drill |
| 15 min | Update weak-area ranking |
Scheduling calculations and interpretation to maintain
PMI-SP preparation should include calculation fluency, but do not study calculations in isolation. Always connect the number to the schedule decision.
| Skill | Practice until you can | Common trap |
|---|---|---|
| Forward pass | Calculate early start and early finish | Forgetting the project start convention used by the question |
| Backward pass | Calculate late start and late finish | Mixing early and late dates in the same step |
| Total float | Use LS - ES or LF - EF | Assuming float belongs equally to every stakeholder |
| Free float | Identify delay allowed without delaying a successor | Confusing free float with total float |
| Critical path | Identify the longest path or controlling path | Ignoring near-critical paths or imposed constraints |
| Leads and lags | Interpret acceleration or delay between linked activities | Treating every dependency as finish-to-start |
| Schedule variance | Explain whether performance is ahead or behind plan | Reporting a number without explaining impact |
| Schedule performance index | Interpret trend and forecast implications | Treating one metric as the only basis for action |
| Crashing | Add resources where it can shorten schedule | Crashing non-critical work with no finish-date benefit |
| Fast tracking | Overlap work where risk is acceptable | Ignoring rework, quality, or dependency risk |
7-day final review plan
Use this plan if your exam is one week away. This is not a full learning plan. The goal is to stabilize performance, review explanations, and avoid last-minute overload.
| Day | Main focus | Study actions | Stop doing |
|---|---|---|---|
| 7 days out | Baseline final-week status | Take a timed mixed set; rank weak areas; review every missed and guessed question | Do not start a new textbook or course |
| 6 days out | Network logic and calculations | Drill critical path, float, leads/lags, constraints, and schedule compression | Do not memorize formulas without scenario interpretation |
| 5 days out | Monitoring, controlling, and change | Practice variance, forecasting, baseline control, corrective action, and impact analysis scenarios | Do not assume every delay requires a baseline change |
| 4 days out | Risk, stakeholders, and reporting | Practice schedule risk, escalation, communication, and stakeholder-reporting questions | Do not choose answers that skip analysis or governance |
| 3 days out | Timed mock or large mixed set | Simulate exam conditions using the current PMI-SP timing from PMI materials; mark uncertain questions | Do not pause, research, or review during the mock |
| 2 days out | Explanation review only plus light practice | Review the mock deeply; redo missed calculations; complete one short confidence set | Do not take another full mock if it will create fatigue |
| 1 day out | Light final review | Review your missed-question log, formulas, decision rules, and exam logistics | Stop adding new material |
Final 24-hour rule
The day before the exam, your best use of time is not volume. Focus on:
- Your top 20 missed-question notes.
- Critical path and float steps.
- Change control and baseline decision rules.
- Schedule compression tradeoffs.
- Stakeholder communication and escalation logic.
- Sleep, meals, identification, appointment details, and travel or check-in timing.
14-day focused plan
Use this plan if you have two weeks and need to convert partial knowledge into exam readiness.
| Day | Focus | Practice target | Review output |
|---|---|---|---|
| 1 | Diagnostic and study map | 30-60 mixed questions | Top 5 weak areas and error categories |
| 2 | Schedule strategy and governance | Schedule management plan, baselines, update cycles | One-page governance summary |
| 3 | Activity definition and sequencing | Dependencies, milestones, constraints, assumptions | Dependency and constraint notes |
| 4 | Critical path and float | Network diagrams, forward/backward pass | Redone calculation misses |
| 5 | Estimating, resources, and calendars | Duration estimating, resource constraints, calendars | Assumption and resource-impact list |
| 6 | Risk and schedule quality | Schedule risk, buffers, what-if, contingency | Risk-versus-issue comparison |
| 7 | Timed mixed set | 50-75 questions or equivalent | Missed-question log update |
| 8 | Monitoring and controlling | Actuals, variance, forecasting, corrective action | Variance decision checklist |
| 9 | Change control and recovery | Impact analysis, baseline changes, crashing, fast tracking | Compression tradeoff table |
| 10 | Reporting and stakeholders | Dashboards, escalation, communication scenarios | Audience-based reporting notes |
| 11 | Agile, hybrid, and rolling-wave planning | Iterations, releases, adaptive forecasting, dependencies | Predictive/agile/hybrid comparison |
| 12 | Timed mock or large mixed set | Simulated timing using current PMI materials | Full explanation review |
| 13 | Weak-area repair | Targeted sets in lowest-scoring areas | Final error-pattern list |
| 14 | Light final review | Short mixed set, formulas, governance rules | Exam-day checklist |
30-day balanced plan
Use this plan if you want enough time for content review, repeated practice, and mock-based correction.
Weekly structure
| Week | Goal | Main study areas | Milestone |
|---|---|---|---|
| Week 1 | Build the schedule foundation | Governance, schedule management plan, activity definition, sequencing | Diagnostic completed and study log created |
| Week 2 | Strengthen schedule development | Network logic, critical path, float, estimating, resources, calendars | Timed mid-point set completed |
| Week 3 | Build control and decision judgment | Status, variance, forecasting, risk, change, compression | First full timed mock or large simulation |
| Week 4 | Integrate and finalize | Stakeholders, reporting, agile/hybrid context, weak areas, final mock | Final review plan completed |
Day-by-day 30-day schedule
| Day | Focus | Study action |
|---|---|---|
| 1 | Diagnostic | Complete a mixed diagnostic set and classify errors |
| 2 | PMI-SP scope map | Review the current PMI-SP exam outline and map your weak areas |
| 3 | Schedule strategy | Study schedule management planning, roles, update cycles, and governance |
| 4 | Activities and milestones | Practice turning scope/work packages into schedulable activities |
| 5 | Dependencies | Drill dependency types, leads, lags, constraints, and assumptions |
| 6 | Network scenarios | Build and interpret simple schedule networks |
| 7 | Review checkpoint | Complete a timed set and update the missed-question log |
| 8 | Forward/backward pass | Practice early/late dates by hand |
| 9 | Float | Drill total float, free float, and near-critical path scenarios |
| 10 | Estimating | Review duration estimating, uncertainty, and assumptions |
| 11 | Resources and calendars | Practice resource availability and calendar-driven schedule impacts |
| 12 | Schedule quality | Review logic checks, unrealistic dates, missing dependencies, and data quality |
| 13 | Mixed development practice | Complete a timed set focused on schedule development |
| 14 | Mid-point timed set | Take a larger timed set and review all explanations |
| 15 | Status collection | Study actuals, percent complete, remaining duration, and update discipline |
| 16 | Variance and forecasting | Practice schedule variance, trends, and forecast interpretation |
| 17 | Corrective action | Choose responses to slippage, missed milestones, and recovery needs |
| 18 | Change control | Practice baseline, approved change, and impact analysis scenarios |
| 19 | Schedule risk | Review risk responses, contingency, buffers, and what-if analysis |
| 20 | Compression | Compare crashing, fast tracking, re-sequencing, and tradeoffs |
| 21 | Timed mock | Complete a full mock or the largest available timed simulation |
| 22 | Mock review | Review every miss, guess, and slow question; update weak-area ranking |
| 23 | Stakeholders | Practice reporting, escalation, and audience-specific communication |
| 24 | Agile and hybrid | Review rolling-wave planning, releases, iterations, and dependencies |
| 25 | Closeout and lessons | Study as-built schedules, actuals, archives, and historical data |
| 26 | Weak area 1 | Target your lowest-confidence area with focused practice |
| 27 | Weak area 2 | Target your second-lowest area with focused practice |
| 28 | Final mock | Complete a timed mock or large timed set |
| 29 | Explanation review | Review final mock explanations; redo calculations and scenario misses |
| 30 | Final readiness | Light review, formula check, decision rules, and exam logistics |
60/90-day full preparation path
Use this path if you are starting earlier, rebuilding from fundamentals, or balancing preparation with a demanding work schedule.
| Phase | 60-day timing | 90-day timing | Focus | Output |
|---|---|---|---|---|
| Phase 1 | Week 1 | Weeks 1-2 | Diagnostic, exam map, study system | Weak-area list and missed-question log |
| Phase 2 | Weeks 2-3 | Weeks 3-4 | Schedule strategy, governance, activities, sequencing | Schedule planning summary |
| Phase 3 | Weeks 4-5 | Weeks 5-6 | Network logic, critical path, float, estimating, resources | Calculation accuracy and interpretation |
| Phase 4 | Week 6 | Weeks 7-8 | Monitoring, controlling, forecasting, change, risk | Scenario decision checklist |
| Phase 5 | Week 7 | Weeks 9-10 | Stakeholders, reporting, recovery, compression, agile/hybrid | Integrated practice results |
| Phase 6 | Week 8 | Weeks 11-12 | Timed mocks, final explanation review, weak-area repair | Exam-readiness decision |
60-day weekly schedule
| Week | Study focus | Practice requirement |
|---|---|---|
| 1 | Diagnostic, PMI-SP content map, study log setup | 2 mixed sets, no concern about score yet |
| 2 | Schedule strategy, governance, baselines, update cycles | Targeted questions on schedule planning decisions |
| 3 | Activity definition, dependencies, constraints, leads/lags | Network-building and sequencing drills |
| 4 | Critical path, float, estimating, resources, calendars | Calculation and resource-impact practice |
| 5 | Schedule risk, quality, what-if analysis, compression | Scenario sets on risk and recovery decisions |
| 6 | Monitoring, controlling, variance, forecasting, change control | Large timed set and deep review |
| 7 | Reporting, stakeholders, agile/hybrid, closeout | Mixed scenario practice and weak-area repair |
| 8 | Timed mocks and final review | 1-2 full simulations or large timed sets with explanation review |
90-day weekly schedule
| Weeks | Study focus | Practice requirement |
|---|---|---|
| 1-2 | Diagnostic, scheduling foundations, study log | Short mixed sets and terminology cleanup |
| 3-4 | Schedule strategy, governance, baselines, activities, dependencies | Targeted scenario sets and summary notes |
| 5-6 | Network logic, critical path, float, estimating, resources | Calculation drills plus mixed interpretation questions |
| 7-8 | Status, variance, forecasting, risk, change, compression | Timed sets with detailed explanation review |
| 9-10 | Stakeholders, reporting, closeout, agile and hybrid scheduling | Integrated scenario practice |
| 11 | Full mock cycle and remediation | Timed mock, full review, targeted repair |
| 12 | Final mock and final-week rules | Light review, readiness check, no new major material |
How to review missed questions
A missed-question log is more valuable than rereading notes. Track misses in a way that changes your next study session.
| Log field | What to write |
|---|---|
| Date | When you missed it |
| Topic | Example: float, compression, baseline change, reporting |
| Question type | Calculation, concept, scenario, stakeholder, agile/hybrid |
| Your answer reason | Why your choice looked right |
| Correct answer reason | Why the better answer is stronger |
| Root cause | Gap, rush, trap, math error, governance mistake, context mistake |
| Rule to remember | One sentence you can apply next time |
| Redo date | 24 hours, 72 hours, or 7 days later |
Missed-answer decision table
| If the miss happened because… | Then do this next |
|---|---|
| You forgot a term | Make a flashcard, then answer 5 targeted questions |
| You miscalculated float | Redraw the network and redo the forward/backward pass by hand |
| You picked action before analysis | Practice scenarios where the best answer is impact assessment or stakeholder review |
| You changed the baseline too quickly | Review approved-change and baseline-control logic |
| You confused risk with issue | Write whether the event has occurred; then choose prevention or response |
| You overused crashing or fast tracking | Compare cost, risk, quality, and critical-path effect |
| You missed the stakeholder angle | Identify who needs the schedule information and what decision they must make |
| You misread agile or hybrid context | Identify cadence, planning horizon, and change mechanism before answering |
| You ran out of time | Practice shorter timed sets and cap time per question |
What to practice next
Use practice results to choose the next block. Do not simply study the topic you like most.
| Symptom in practice | Next study block |
|---|---|
| You cannot identify the controlling path | Network diagrams, dependency logic, and critical path drills |
| Float questions are inconsistent | Forward/backward pass practice plus total versus free float comparison |
| You miss baseline-change questions | Schedule governance, impact analysis, and approval workflow scenarios |
| You choose reporting answers that are too technical | Stakeholder communication and audience-based schedule reporting |
| You miss slippage scenarios | Variance, forecasting, corrective action, and escalation |
| You confuse crashing and fast tracking | Schedule compression tradeoffs and risk impact |
| You struggle with resource constraints | Resource calendars, availability, leveling concepts, and estimate assumptions |
| You miss risk questions | Schedule risk, contingency, buffers, and what-if analysis |
| You are strong in calculations but weak in scenarios | Mixed judgment sets with explanation review |
| You are slow overall | Timed 20-question sets with strict pacing and post-set review |
When to use timed mock exams
Timed mocks are most useful after you have enough foundation to learn from the explanations.
| Preparation length | Mock timing |
|---|---|
| 7 days | One mock or large timed set about 3 days before the exam, if it will not cause fatigue |
| 14 days | One larger timed set around Day 7 and one mock or large simulation around Day 12 |
| 30 days | One midpoint timed set, one mock around Day 21, and one final mock around Day 28 |
| 60 days | First large timed set around Week 6, then 1-2 final simulations in Weeks 7-8 |
| 90 days | Large timed sets in Weeks 7-10, then mock cycles in Weeks 11-12 |
Mock exam rules
- Use the current PMI-SP timing and exam-day constraints from PMI materials.
- Do not pause the timer.
- Mark uncertain questions, but keep moving.
- Review the mock within 24 hours.
- Spend serious time on explanations; a mock without review is mostly a stamina exercise.
- Track performance by topic, not just by total score.
- Do not take full mocks on consecutive days unless you are specifically training stamina and can still review properly.
When to stop adding new material
Stop adding major new material before the exam so your final days are spent stabilizing what you already know.
| Time remaining | New material rule |
|---|---|
| 7 days | Only add small fixes for high-value weak areas |
| 3 days | Stop all broad new content; review explanations and decision rules |
| 1 day | No new content; light review only |
| Exam morning | Quick confidence review only, not problem solving marathons |
Good final review items:
- Missed-question log.
- Critical path and float steps.
- Schedule baseline and change control rules.
- Risk versus issue distinctions.
- Crashing versus fast tracking.
- Stakeholder reporting and escalation.
- Predictive versus agile or hybrid scheduling cues.
Final-week readiness checks
You are closer to ready when you can do the following without heavy notes:
| Readiness check | Yes/No |
|---|---|
| I can explain how a schedule baseline is created, used, and changed | |
| I can identify dependencies, leads, lags, constraints, and assumptions in a scenario | |
| I can calculate and interpret critical path and float on a simple network | |
| I can choose a reasonable action when schedule performance is behind plan | |
| I can distinguish risk response from issue response | |
| I can compare crashing, fast tracking, and other recovery options | |
| I can tailor schedule reporting to executives, team members, customers, or governance bodies | |
| I can recognize when a scenario calls for analysis before action | |
| I can adapt schedule reasoning to predictive, agile, or hybrid delivery | |
| I can finish timed practice without rushing the final questions |
If several checks are still “No,” spend your remaining time on mixed scenario practice and explanation review rather than broad reading.
Practical next step
Choose your timeframe, take one mixed diagnostic set, and build your missed-question log before your next study block. Then follow the plan that matches your exam date and let each practice review decide what you study next.