A 10-Week PMI-ACP Study Plan Based on the 2026 ECO

Before week one: complete the eligibility learning

PMI requires 21 hours of formal agile learning before you submit the PMI-ACP application. Those hours are an eligibility condition and are separate from the independent study hours in this example. Complete the required course and keep its proof. Then use the March 2026 Examination Content Outline as the plan’s content map. Do not use an older PMI-ACP domain list.

The schedule below assumes five to seven hours of independent study each week. That is an illustration, not a PMI average or a rule. If you can study fewer hours, extend the calendar. If your baseline shows strong applied skills across all four domains, you may move through familiar weeks more quickly. Keep the practice and review steps even when you shorten the timeline.

A repeatable weekly rhythm

Divide the week into three or four sessions. One session can introduce a task or concept, a second can apply it to a case, and a third can review practice questions and update an error log. Reserve a longer block for mixed timed practice every week or two. A session should end with a decision you can explain, not just pages read.

For each missed or uncertain answer, record the domain, the fact that mattered, why the strongest option fits, and why the closest distractor fails. Review correct guesses too. Return to the same concept with a new scenario after a few days. If the answer is remembered only as a letter, the concept still needs attention.

The 10-week schedule

Week 1: baseline and blueprint map

Read the four domain descriptions and tasks in the March 2026 ECO. Take a short mixed diagnostic that samples Mindset, Leadership, Product, and Delivery. Tag each result as confident, uncertain, or incorrect. Identify the two weakest task areas and any format issue, such as interpreting an exhibit or following a multiple-response instruction. Build a one-page checklist for the rest of the plan.

Do not turn the diagnostic score into a pass prediction. PMI does not publish a fixed raw percentage cutoff. The point is to find where study can help. A candidate who misses Product questions because stakeholder requests are confused with user evidence should record that specific gap, rather than simply write ‘study Product.’

Week 2: Mindset and learning

Study experimentation, agile suitability, systems thinking, team collaboration, transparency, psychological safety, feedback loops, and change. For each idea, write a situation where it helps and one boundary or risk. Practice selecting a small experiment that tests an assumption without exposing the team or customer to unnecessary harm. Review how to tailor an approach to complexity instead of treating one process as universal.

Week 3: Leadership and team capability

Focus on trust, empowerment, coaching, mentoring, training, problem resolution, knowledge sharing, purpose, and conflict. Practice identifying the cause and level of a conflict before selecting a response. Work through cases involving a team member who needs instruction, a team that needs facilitation, or an experienced colleague asking for guidance. Note when the practitioner should support a team decision rather than make it on the team’s behalf.

Week 4: Product and value

Practice refining backlog items, clarifying customer needs, prioritizing with stakeholders, decomposing work, and sizing collaboratively. Convert vague requests into a user outcome and observable success criteria. Review how an increment can be demonstrated early and measured after release. Include security, privacy, regulatory requirements, and sustainability when the scenario calls for them; product value includes constraints that affect whether a solution can be used responsibly.

Week 5: Delivery, flow, and quality

Review early feedback, agile metrics, risk and impediment management, waste, continuous improvement, customer engagement, and flow. Practice interpreting WIP, cycle time, throughput, and cumulative flow in context. Explain what a metric shows and what it cannot prove. Use a case with blocked work to distinguish a system constraint from individual performance. Review definition of done, continuous integration, testing, and acceptance conditions.

Week 6: Tools and methods across domains

Return to the ECO’s tools and techniques and connect each one to a task. Compare when a retrospective, value stream map, risk spike, work-in-progress limit, or prioritization method can help. Avoid learning tool names without their purpose. Practice a scenario in which more than one framework could work; select the approach that matches the uncertainty, work pattern, team, and constraints described.

Week 7: Mixed scenario practice

Complete mixed sets that combine domains. After each question, state whether it asks for an immediate action, a long-term improvement, a metric, or a decision owner. Review why distractors fail. If you miss questions in familiar subject areas, inspect whether the issue is reading, authority, timing, or a local-workplace assumption rather than knowledge of the term.

Week 8: Interaction types and exhibits

Practice multiple-response, drag-and-drop-style, and exhibit questions using materials that support those interactions. For an exhibit, read its labels and units, locate the measure relevant to the prompt, and avoid drawing conclusions beyond the data. For multiple response, follow the instruction and test every option. For matching or sequencing, define the relationship before placing choices. Track errors by interaction type.

Week 9: Timed simulation and targeted repair

Take a fresh timed set and practice the 180-minute rhythm. The exam averages 90 seconds per item, but exhibits and complexity vary. Practice completing and reviewing items 1 through 60 before beginning the 10-minute break; the first section cannot be reopened once the break starts. After the set, choose two or three high-impact weaknesses for targeted review instead of rereading every note.

Week 10: Consolidate and prepare

Use short mixed practice, revisit the error log, and explain the main tasks in each domain without notes. Do not spend the final days collecting new frameworks that are outside your gaps. Confirm your appointment, identification, route or online testing requirements, and any accommodations. Preserve enough sleep and avoid a last-minute all-night study session that undermines reading accuracy.

Adjust the plan to your starting point

A product owner with strong backlog experience may spend less time on Product definitions and more on Leadership, team capability, and Delivery metrics. A Scrum master who facilitates well may need additional work on product outcomes, value measures, and customer feedback. A developer may be strong in quality practices and weak in organizational coordination or stakeholder prioritization. Keep the weekly structure, but shift time toward tasks that repeatedly cause errors.

If you only have three study hours in a week, do not try to perform every activity at half attention. Use two focused concept sessions and one short question review, then extend the schedule. If you have ten hours, add fresh practice and careful review rather than doubling passive reading. The time should serve a skill: explain, apply, analyze, or decide.

When to schedule the exam

The application gives a one-year eligibility period, with up to three attempts under PMI’s handbook. Schedule when you have enough preparation time and there is a suitable appointment within your period. Do not wait until the last month to look for a seat. Appointment changes within 30 days carry a US$70 fee plus taxes under the March 2026 handbook, and changes are unavailable within 48 hours through the normal process.

A useful readiness signal is the ability to explain answers across all domains and interaction types under time constraints. Practice percentages can guide your review but cannot establish the official result. The plan is successful when your decisions are consistent on fresh scenarios and your pacing leaves room to review, not when you have completed exactly ten calendar weeks.

Keep the plan active, not mechanical

At the end of each week, ask what became easier and what still produces uncertain answers. Update the next week accordingly. If a domain feels strong but you cannot explain a case without using memorized language, continue practicing. If your results are strong across new scenarios, move on rather than repeating a lesson to fill time. A good schedule responds to evidence and fits the candidate’s life.

If you miss a week, resume with the current priority rather than doubling every session the following week. Carry forward only the highest-value tasks, keep the practice review, and adjust the exam date if necessary. A calendar is a planning aid; it should remain realistic when work, family, or health conditions change.

Use fresh items for this final timing practice.