Who this study plan is for
This independent Study Plan is for candidates preparing for PMI’s PMI Agile Certified Practitioner (PMI-ACP), exam code PMI-ACP. It is designed for working professionals who need to turn limited study time into a realistic schedule.
The PMI-ACP exam rewards more than agile vocabulary. Your plan should move you from concept recognition into scenario judgment: what an agile practitioner should do next when working with teams, stakeholders, product priorities, change, risk, governance, delivery constraints, and hybrid environments.
Use PMI’s current exam content outline and candidate resources as your source of truth for official exam details. Use this page to organize your preparation time, practice rhythm, mock exam timing, and review process.
Which plan should you use?
| Time until exam | Use this path if… | Typical study time | Main goal | Main risk to avoid |
|---|
| 7 days | You have already studied and need final review | 12-20 hours | Consolidate, time practice, review mistakes | Trying to learn too many new topics |
| 14 days | You know agile basics but need focused exam preparation | 25-40 hours | Patch gaps and build scenario judgment | Taking questions without reviewing explanations |
| 30 days | You want a balanced plan while working full time | 45-75 hours | Cover domains, practice steadily, take mocks | Staying in passive reading too long |
| 60 days | You are starting early and can study most days | 70-110 hours | Build concepts, then transition to mixed practice | Delaying timed practice |
| 90 days | You are newer to agile or have an uneven background | 90-140 hours | Learn, apply, review, and stabilize | Forgetting early topics before final review |
Quick decision guide
| If this describes you | Start here | Adjustment |
|---|
| Strong agile work experience, weak test practice | 14-day or 30-day plan | Spend more time on scenario questions and explanation review |
| Scrum experience only, limited Kanban/Lean/XP exposure | 30-day or 60-day plan | Add framework comparison drills |
| Predictive project management background, newer to agile | 60/90-day plan | Focus on mindset shift, servant leadership, value delivery, and adaptive change |
| Exam in one week and scores are inconsistent | 7-day plan | Stop broad reading and triage weaknesses |
| You have failed or postponed before | 30-day or 60-day plan | Build an error log and retake only after explanation mastery improves |
Core study areas to rotate through
Use the current PMI-ACP exam outline to confirm official domain language. In practical study terms, your weekly rotation should include:
| Study area | What to know | What to practice |
|---|
| Agile mindset and principles | Adaptive planning, empirical process control, value delivery, collaboration, continuous improvement | Choosing responses that support transparency, inspection, adaptation, and customer value |
| Scrum and team-based delivery | Roles, events, artifacts, backlog refinement, sprint planning, review, retrospective | Handling team impediments, product owner interaction, sprint changes, and stakeholder feedback |
| Kanban and flow | Work in progress, flow, queues, bottlenecks, cycle time, cumulative flow concepts | Interpreting flow problems and improving delivery without over-controlling the team |
| Lean and value | Waste reduction, value stream thinking, small batches, continuous improvement | Prioritizing valuable work and removing low-value activity |
| XP and quality practices | Pairing, test-first thinking, refactoring, continuous integration concepts | Choosing quality built-in responses over late defect discovery |
| Product and value delivery | Backlog prioritization, release planning, MVP thinking, feedback loops | Deciding what to build next and how to incorporate stakeholder feedback |
| Stakeholder engagement | Communication, collaboration, expectation management, transparency | Managing conflict, disagreement, and changing priorities |
| Team performance | Servant leadership, facilitation, coaching, empowerment, self-organization | Selecting actions that enable the team rather than command the team |
| Risk, issues, and change | Risk-based adaptation, impediment removal, iterative learning, agile change handling | Responding to blockers, uncertainty, late discoveries, and shifting business needs |
| Hybrid and organizational context | Agile inside governance, contracts, compliance, predictive interfaces | Tailoring without abandoning agile values |
Daily practice rhythm
A good PMI-ACP study day has both learning and judgment practice. Do not spend the entire plan reading.
Standard 90-minute weekday block
| Time | Activity | Output |
|---|
| 10 minutes | Review yesterday’s missed-question log | Know what you are trying to fix today |
| 25 minutes | Focused concept review | One topic clarified |
| 35 minutes | Scenario practice questions | New decisions under exam-like wording |
| 15 minutes | Explanation review | Why correct is correct; why distractors are wrong |
| 5 minutes | Update error log | One or two rules to revisit |
Short 45-minute block
| Time | Activity |
|---|
| 5 minutes | Review error log |
| 25 minutes | Answer a small timed set |
| 15 minutes | Review explanations and tag misses |
Longer weekend block
| Time | Activity |
|---|
| 30 minutes | Review weak topic |
| 60-90 minutes | Timed mixed practice |
| 60 minutes | Deep explanation review |
| 20 minutes | Flash review of agile terms, roles, metrics, and decision rules |
Shift your study mix over time
| Phase | Concept review | Practice questions | Explanation review |
|---|
| Early | 50% | 30% | 20% |
| Middle | 30% | 45% | 25% |
| Final week | 15% | 45% | 40% |
In the final phase, explanation review is as important as answering more questions. PMI-ACP preparation improves when you understand the decision pattern behind the answer.
Start with a diagnostic
Before choosing detailed topics, take a diagnostic set.
| Diagnostic action | Recommended approach |
|---|
| Use a mixed question set | Include agile mindset, team, product, stakeholder, risk, change, metrics, and delivery approach questions |
| Time the set | Do not pause to research answers |
| Review every explanation | Include correct answers you guessed |
| Tag each miss | Topic gap, wording trap, mindset error, framework confusion, or time pressure |
| Build your first priority list | Pick the top 3 weak areas for the next 3 study days |
Do not overreact to one diagnostic score. Use it to decide what to study next.
7-day final review plan
Use this if your exam is in one week and you have already completed most content review. This is not a full learning plan.
| Day | Main focus | Practice work | Review output |
|---|
| 1 | Baseline and triage | Timed mixed set or mock section | List top 5 weak areas |
| 2 | Agile mindset and servant leadership | Scenario questions on team decisions | Decision rules for coaching, facilitation, and empowerment |
| 3 | Product, value, and backlog | Questions on prioritization, release planning, feedback, MVP, and value | Backlog and stakeholder review notes |
| 4 | Frameworks and delivery practices | Scrum, Kanban, Lean, XP, metrics, quality practices | Comparison chart of roles, flow, quality, and ceremonies |
| 5 | Stakeholders, risk, change, and impediments | Mixed scenario set | Missed-question log cleaned and grouped |
| 6 | Timed mock or exam-length simulation | Use current exam timing from PMI or your provider | Full explanation review; no broad new topics |
| 7 | Light final review | Small confidence set only if needed | Final notes, logistics, rest |
7-day rules
- Stop adding new major resources by Day 5.
- Use Day 6 for timing and explanation review, not for memorizing everything.
- If a question explanation changes how you think, add it to a one-page final review sheet.
- If you are missing questions because you rush, practice slowing down on the first read.
- If you are missing questions because you debate two good answers, focus on agile values and the role expected in the scenario.
14-day focused plan
Use this if you know agile basics but need structured exam preparation.
Week 1: repair knowledge gaps
| Day | Study focus | Practice focus |
|---|
| 1 | Diagnostic and exam-outline mapping | Mixed timed diagnostic |
| 2 | Agile principles, mindset, servant leadership | “What should the agile practitioner do next?” questions |
| 3 | Scrum roles, events, artifacts, backlog refinement | Sprint planning, review, retrospective, product owner scenarios |
| 4 | Kanban, Lean, flow, WIP, bottlenecks | Flow metrics and process improvement scenarios |
| 5 | XP and quality practices | Built-in quality, defects, technical debt, continuous improvement |
| 6 | Product value, prioritization, release planning | Stakeholder feedback and backlog ordering |
| 7 | Weekly timed mixed set | Full review of all missed and guessed questions |
Week 2: build exam judgment
| Day | Study focus | Practice focus |
|---|
| 8 | Stakeholders, facilitation, communication | Conflict, expectations, collaboration, transparency |
| 9 | Risk, issues, impediments, change | Adaptive responses to uncertainty and blockers |
| 10 | Hybrid and predictive interfaces | Tailoring, governance, contracts, compliance, and agile values |
| 11 | Timed mock or large timed set | Stamina, pacing, answer discipline |
| 12 | Deep review of mock misses | Rework weak topics and redo similar questions |
| 13 | Final explanation review | Missed-question log, agile decision rules, framework comparisons |
| 14 | Light review and readiness check | Small set only; no heavy new material |
14-day emphasis
| If your Day 7 review shows… | Spend Days 8-13 on… |
|---|
| Weak agile mindset | Servant leadership, collaboration, transparency, adaptation |
| Weak framework recognition | Scrum/Kanban/Lean/XP comparison drills |
| Weak product decisions | Prioritization, value, feedback, backlog refinement |
| Weak stakeholder judgment | Communication, facilitation, conflict, expectation management |
| Weak timing | Timed sets with strict review after each set |
30-day balanced plan
Use this if you want a complete but efficient schedule.
30-day overview
| Week | Goal | Main study actions | Practice target |
|---|
| 1 | Build foundation and diagnose | Agile mindset, principles, PMI-ACP outline review, baseline diagnostic | Short mixed sets after each topic |
| 2 | Learn frameworks and delivery practices | Scrum, Kanban, Lean, XP, quality, flow, metrics | Topic-based scenario sets |
| 3 | Practice complex scenarios | Product value, stakeholders, risk, change, team performance, hybrid context | Mixed timed sets |
| 4 | Simulate and review | Timed mocks, explanation review, weak-area repair, final sheet | Mock plus targeted drills |
30-day weekly schedule
| Day range | Focus | What to produce |
|---|
| Days 1-3 | Diagnostic, agile mindset, principles | Error log and first weak-area list |
| Days 4-7 | Scrum and core team delivery | Role/event/artifact review sheet |
| Days 8-11 | Kanban, Lean, flow, WIP, continuous improvement | Metrics and flow interpretation notes |
| Days 12-14 | XP, quality, technical debt, built-in quality | Quality decision rules |
| Days 15-18 | Product value, backlog, release planning, prioritization | Product/value scenario notes |
| Days 19-21 | Stakeholders, facilitation, communication | Stakeholder response playbook |
| Days 22-24 | Risk, change, impediments, uncertainty | Risk/change decision table |
| Days 25-26 | Hybrid and organizational context | Tailoring and governance notes |
| Day 27 | Timed mock or large simulation | Timing data and error log |
| Day 28 | Mock review and weak-area repair | Redo similar questions |
| Day 29 | Final mixed practice and explanation review | Final review sheet |
| Day 30 | Light review and exam readiness check | Rested, organized, no new resources |
30-day weekly routine
| Day type | Recommended work |
|---|
| 4 weekdays | 60-90 minutes each |
| 1 weekday | Light review or catch-up |
| Weekend day 1 | 2-3 hour deep study and practice block |
| Weekend day 2 | 60-120 minute review block |
60/90-day full preparation path
Use this if you are starting early, are newer to agile, or need to balance preparation with a demanding work schedule.
Full path by phase
| Phase | 60-day schedule | 90-day schedule | Goal |
|---|
| Setup and diagnostic | Days 1-4 | Days 1-7 | Understand exam scope and baseline weaknesses |
| Agile foundations | Days 5-12 | Days 8-18 | Build mindset, principles, servant leadership |
| Frameworks and practices | Days 13-25 | Days 19-38 | Learn Scrum, Kanban, Lean, XP, quality, metrics |
| Product and value delivery | Days 26-34 | Days 39-52 | Practice prioritization, backlog, release, stakeholder feedback |
| People, risk, and change | Days 35-43 | Days 53-66 | Handle stakeholders, conflict, impediments, uncertainty |
| Hybrid and integration | Days 44-48 | Days 67-72 | Apply agile judgment in organizational constraints |
| Timed practice phase | Days 49-55 | Days 73-82 | Take mocks or large timed sets and review deeply |
| Final repair and review | Days 56-60 | Days 83-90 | Stop new content, review explanations, stabilize |
60/90-day weekly targets
| Week | 60-day plan | 90-day plan |
|---|
| 1 | Diagnostic, study setup, agile mindset | Diagnostic, study setup, agile mindset |
| 2 | Agile principles and servant leadership | Agile principles and servant leadership |
| 3 | Scrum and team delivery | Scrum roles, events, artifacts, backlog |
| 4 | Kanban, Lean, XP, quality | Kanban, Lean, flow, WIP |
| 5 | Product value and prioritization | XP, quality, technical debt |
| 6 | Stakeholders, risk, change | Product value and prioritization |
| 7 | Hybrid context and mixed practice | Stakeholders and communication |
| 8 | Timed mocks and final review | Risk, change, impediments |
| 9 | Final week, if using full 60 days | Hybrid context and tailoring |
| 10 | — | Mixed scenario practice |
| 11 | — | Timed mock and review |
| 12 | — | Weak-area repair |
| 13 | — | Final review and exam readiness |
How to avoid forgetting early material
| Every week, include… | Why |
|---|
| One mixed question set | Keeps older topics active |
| One error-log review session | Prevents repeated mistakes |
| One framework comparison drill | Reduces confusion between Scrum, Kanban, Lean, and XP |
| One stakeholder or risk scenario set | Builds judgment beyond terminology |
| One timed block after the midpoint | Builds pacing before the final week |
Missed-question review method
Your missed-question review is where most score improvement happens. Do not simply mark an answer wrong and move on.
| Column | What to record |
|---|
| Date | When you missed it |
| Topic | Agile mindset, Scrum, Kanban, product, stakeholder, risk, change, hybrid, etc. |
| Scenario clue | The phrase that should have guided your answer |
| Your answer pattern | What you were thinking |
| Correct reasoning | Why the credited answer is better |
| Distractor lesson | Why the tempting wrong answer is wrong |
| Fix action | Read, drill, compare, or retest |
| Review date | Same day, 48 hours later, and final week |
Classify every miss
| Miss type | What it means | Fix |
|---|
| Concept gap | You did not know the term or practice | Review the topic, then answer 5-10 similar questions |
| Mindset error | You chose a command-and-control or overly predictive response | Review agile values, servant leadership, team empowerment |
| Role confusion | You mixed up product owner, team, sponsor, stakeholder, or agile practitioner responsibilities | Create a role-action chart |
| Framework confusion | You applied Scrum thinking to a Kanban situation or vice versa | Build a comparison table |
| Over-escalation | You escalated before facilitating, collaborating, or removing impediments | Practice “what should you do first?” questions |
| Ignored value | You focused on activity rather than business outcome | Review prioritization and feedback loops |
| Timing error | You understood it but rushed | Use shorter timed drills with deliberate reading |
| Wording trap | You missed “first,” “best,” “next,” or scenario context | Underline the decision word before answering |
Review cadence
| When | What to do |
|---|
| Same day | Read explanation and write the rule in your own words |
| 48 hours later | Redo a similar question without looking at notes |
| End of week | Review all red/yellow topics |
| Final week | Review only recurring errors and high-value notes |
Agile, predictive, and hybrid scenario judgment
PMI-ACP questions often test whether you can choose an agile-appropriate response in a real organizational context.
| Scenario clue | Stronger study response |
|---|
| Team is blocked | Identify impediment, facilitate removal, improve transparency |
| Stakeholder wants a change | Use backlog/prioritization and value discussion rather than uncontrolled scope acceptance |
| Product owner is unavailable | Improve collaboration and clarify decision flow; do not have the team guess priorities |
| Team is missing sprint commitments | Inspect causes, coach, adjust planning, and improve estimation/flow |
| Defects appear late | Strengthen built-in quality, feedback, testing, and definition of done concepts |
| Work piles up in progress | Review WIP, flow, bottlenecks, and Kanban improvement options |
| Sponsor wants predictability | Communicate transparently using empirical data and realistic forecasting |
| Governance requires documentation | Tailor documentation to need while preserving agile feedback and collaboration |
| A predictive organization is adopting agile | Coach incrementally, address culture, and tailor practices responsibly |
| Team conflict appears | Facilitate collaboration and shared understanding before escalation |
What to practice next
Use this table after every study session.
| Your current weakness | Next practice block |
|---|
| You know terms but miss scenarios | Mixed “best next action” questions |
| You miss stakeholder questions | Facilitation, communication, expectations, transparency |
| You miss product questions | Backlog ordering, value, feedback, MVP, release planning |
| You miss team questions | Servant leadership, coaching, impediments, self-organization |
| You miss metrics questions | Flow, WIP, cycle time concepts, burn charts, cumulative flow interpretation |
| You miss framework questions | Scrum/Kanban/Lean/XP comparison review |
| You miss change questions | Agile change handling, backlog refinement, adaptive planning |
| You run out of time | Timed sets of moderate length, then explanation review |
| Your mock results vary widely | Slow down, classify mistakes, and reduce weak-area clusters |
| You get down to two answers | Compare which answer better supports agile values and scenario timing |
When to use timed mock exams
Do not wait until the final day to test stamina. Also, do not take repeated mocks without reviewing them.
| Preparation stage | Timed mock use |
|---|
| Start of plan | Use a smaller diagnostic set, not necessarily a full mock |
| After core content coverage | Take one large timed mixed set or full mock |
| Final 2 weeks | Take 1-2 timed mocks or exam-length simulations if available |
| Final 3 days | Avoid heavy new mock exams unless timing is your main issue |
Use PMI’s current candidate materials or your practice provider’s settings to match the current exam timing and format.
Mock review checklist
After every mock or large timed set:
- Review all missed questions.
- Review all guessed questions, even if correct.
- Identify the top 3 repeated miss types.
- Re-study only the topics connected to repeated errors.
- Redo a small set of similar questions within 48 hours.
- Update your final review sheet.
- Decide whether your next block should be content repair, timed practice, or explanation review.
Final-week rules
| Rule | Why it matters |
|---|
| Stop adding major new resources 3-4 days before the exam | New material can create confusion and reduce confidence |
| Prioritize explanation review over volume | Understanding patterns improves decision-making |
| Keep practice mixed | The real exam will not announce the topic before each question |
| Review agile values and principles daily | They guide ambiguous scenario choices |
| Review framework differences briefly | Prevents role, metric, and practice confusion |
| Do not ignore sleep and logistics | Fatigue causes avoidable reading and judgment errors |
| Keep the final day light | You want recall and calm judgment, not overload |
Exam-readiness checks
You are in a stronger position when you can do the following consistently:
| Readiness check | Yes/No |
|---|
| I can explain why the correct answer is better than the most tempting distractor | |
| I can identify whether a scenario is testing mindset, role, framework, value, stakeholder, risk, change, or hybrid judgment | |
| I can choose collaborative and adaptive responses without defaulting to command-and-control actions | |
| I can distinguish Scrum, Kanban, Lean, and XP practices at a practical level | |
| I can handle backlog, prioritization, release, and stakeholder feedback scenarios | |
| I can interpret basic agile flow and progress information without overcomplicating it | |
| I can complete timed question sets without rushing the final portion | |
| My missed-question log shows fewer repeated errors | |
| I know what I will review the day before the exam | |
| I have checked exam logistics using PMI’s current instructions | |
If you are not ready yet
| Problem | Best adjustment |
|---|
| Repeated mindset misses | Pause broad practice and review agile principles, servant leadership, and empowerment |
| Repeated framework misses | Build a one-page Scrum/Kanban/Lean/XP comparison chart |
| Repeated product/value misses | Drill prioritization, backlog refinement, MVP, feedback, and release scenarios |
| Repeated stakeholder misses | Practice communication, conflict, expectations, facilitation, and transparency scenarios |
| Repeated risk/change misses | Review adaptive planning, impediment removal, and backlog-based change handling |
| Timing problems | Use timed sets and review pacing, not just more reading |
| Low confidence after mocks | Review explanations deeply before taking another mock |
| Too many resources | Pick one primary content source, one practice source, and one error log |
Practical next step
Choose the plan that matches your exam date. Then take a timed diagnostic set, build your missed-question log, and schedule your next three study blocks. For PMI Agile Certified Practitioner (PMI-ACP), improvement comes from repeated scenario practice plus careful explanation review, not from passive reading alone.