PMI-ACP Master Guide

What the PMI-ACP credential measures

PMI-ACP is a professional certification for people who use agile practices in project, product, and team environments. PMI describes its intended audience broadly: product owners, Scrum masters, agile project managers, developers, coaches, and other practitioners. The assessment is framework-agnostic. It expects a candidate to reason about outcomes and team conditions rather than recite one framework’s ceremonies as universal rules.

The March 2026 Examination Content Outline (ECO) reframes the exam around four domains: Mindset, Leadership, Product, and Delivery. The domains connect team-level work to organizational priorities, stakeholder feedback, flow across teams, and useful outcomes. The outline is the right basis for current preparation. Older PMI-ACP materials describe a different set of domains and should not be used as a substitute for the March 2026 blueprint.

A practical way to read a scenario is to ask: What outcome is the team trying to improve? What evidence is available? Who needs to collaborate? Which smallest safe action will create learning or reduce a delivery problem? Agile judgment often favors making the work visible, involving the people closest to it, testing a reversible assumption, and learning from the result. That does not mean ignoring safety, compliance, architecture, or commitments. Those constraints shape the experiment and the path to value.

Exam format and timing

The exam contains 120 items in 180 minutes. One hundred items are scored and 20 are unscored pretest items mixed into the exam. You are not told which items are pretests, so answer every item as if it counts. The ECO lists multiple-choice, multiple-response, drag-and-drop-style items, and exhibits. A study resource that only provides ordinary single-answer questions will not prepare you for every interaction described in the outline.

The exam includes a 10-minute break after you finish reviewing items 1 through 60. Once you start that break, you cannot return to the first section. Use the review screen deliberately: answer remaining questions, check marked items, and decide whether you are ready to submit that section before beginning the break. The break is part of the exam experience, but the allotted 180 minutes is the exam time. The optional tutorial and survey sit outside that timed period.

Three hours for 120 items averages 90 seconds per item. That average is a planning guide, not a command to spend equal time on every question. Some exhibit questions need more reading; a clear definition question may take much less. If a question is consuming time, identify the decision it tests, remove options that violate the scenario, select the strongest remaining response, and mark it for review if the interface permits. Do not let one difficult item take time from several answerable items.

The four domains

The percentages describe the share of exam items assigned to each domain. They are not a promise that a specific test form contains exactly 28 or 25 items in each area, because the exam has scored and unscored items and the blueprint is a proportion. Use the weights to allocate study effort, then check whether your own practice shows a weakness that deserves extra time.

Mindset and Delivery each receive 28%, together more than half of the blueprint. Mindset asks whether you can help a team learn and adapt while keeping the system in view. Delivery asks whether work moves through a reliable process with quality and risk considered. Leadership is not simply being a supportive manager; it involves building team capability and facilitating decisions. Product centers on value and learning from users. These topics overlap in real work, but the exam groups them to make the expected responsibilities clear.

Eligibility: education, learning, and experience

The March 2026 ECO lists a secondary diploma, such as a high school diploma, GED, or global equivalent, and 21 hours of formal training in agile practices, frameworks, and methodologies. It also lists alternative professional experience routes: two years of agile experience in the past five years; one year of agile experience plus a degree from a Global Accreditation Center (GAC) program; one year of agile experience plus an active third-party agile certification that has been held for more than a year; or an active PMP certification. Treat the active PMP route as a way to satisfy the experience criterion, not as a reason to skip the education and learning requirements shown in the table.

Training must be completed before you submit the application. The ECO says to record formal training contact hours in the application and keep proof of completion. Coursework should relate to agile approaches, tools, and techniques in the outline. It can cover agile mindset, collaboration, change, knowledge sharing, team-centric leadership, value delivery, and metrics. A completion certificate and course record make it easier to document what you studied and when.

The experience route concerns agile work, not simply a job title. A person who served as a developer on a team that used iterative planning, a visible backlog, frequent feedback, and incremental delivery may have relevant experience even if the employer did not call the role ‘Agile Practitioner.’ Conversely, a title containing ‘Scrum Master’ does not by itself establish the length or nature of the work. Keep a record of the project, dates, responsibilities, and agile approach so the application can describe the work accurately.

Examples of how the routes apply

A candidate with a secondary diploma, 21 training hours, and two years of agile experience during the past five years meets the listed education, learning, and standard experience conditions. A candidate with one year of agile experience and a GAC-accredited degree can use the GAC route, provided the other listed conditions are met. A candidate with a current Scrum certification earned more than one year ago and one year of agile experience may qualify through the third-party credential route if that credential demonstrates agile knowledge and remains active.

An active PMP holder can use the listed PMP route for the experience requirement. The ECO still lists secondary education and 21 formal learning hours as separate requirements. A candidate whose agile certification expired before applying should not assume it qualifies as active. A candidate with one year of agile experience and a newly earned third-party certificate also should not assume the one-year holding condition is met. The time condition modifies the credential route; it does not turn every short course into a qualifying certification.

The experience window matters. If a candidate has several years in agile work but much of it falls outside the five-year period, the older portion does not satisfy the stated recent-experience period. For a GAC or third-party certification route, one year of recent agile experience remains necessary. When planning an application, map dates carefully instead of adding overlapping project months twice. The application asks for truthful evidence of eligibility, not an inflated total.

Applying and scheduling

A typical path is to create or sign in to a PMI account, complete the online PMI-ACP application, enter education and training, and document the applicable agile experience route. PMI may select an application for audit. Keep education records, training proof, and experience details available so you can support the entries if requested. After approval, pay the exam fee and schedule through Pearson VUE, choosing an available test-center or online-proctored appointment.

Approval and a scheduled appointment are different milestones. Plan around the eligibility period described in PMI’s certification materials, and choose a date that leaves enough preparation time while preserving room for a retake if needed. Online testing requires a compatible room and equipment and a check-in process. A test center removes the home-room requirements but still requires timely arrival and compliant identification. The delivery option is a practical choice about the environment in which you can focus.

How to prepare from the 2026 outline

Start with a blueprint map. Read each domain and task, then write one sentence describing what the practitioner needs to do. Mark your experience level for each task: can explain, can apply, or needs work. This reveals whether a familiar framework name is masking a gap in decision-making. For instance, knowing that a team uses a Kanban board does not prove you can respond to excessive work in progress, blocked work, poor flow, or conflicting stakeholder requests.

Next, build practice around decisions. When a team is missing a forecast, inspect flow and the work system before demanding individual speed. When a customer changes a priority, clarify the expected outcome and trade-offs, then update the ordered work with the appropriate people. When a retrospective reveals a recurring defect, help the team identify a testable process improvement and check its effect. When stakeholders disagree, make the underlying interests and evidence visible and facilitate a choice. Each exercise should state the context, the best next action, and why a tempting alternative is weaker.

Use mixed question sets after you have studied each domain. Review missed items by the reason for the error: misunderstood agile principle, confused role authority, overlooked a constraint, failed to read an exhibit, or rushed through an option that described a later step. Keep a short error log and revisit the relevant task rather than simply rereading all notes. When repeating a question, explain the logic aloud before looking at the rationale. A remembered letter is not evidence of understanding.

Prepare for multiple response and drag-and-drop by reading the full instruction. In a multiple-response item, the task may require more than one selection; selecting a true but incomplete option can still be wrong. For a sequencing or matching task, identify the relationship the prompt asks for before moving items. With an exhibit, locate the specific data that bears on the decision, note its units and timing, and avoid importing assumptions that the display does not support. A useful practice tool should teach those interaction types rather than claim that ordinary multiple-choice drills are equivalent.

A worked agile decision

A product team has delivered two increments, but customer support reports that users still abandon a new onboarding flow. The sponsor asks the team to accelerate the next release by adding three requested features. The strongest first move is to bring the abandonment evidence and the feature requests into a conversation with the product decision-maker and team, clarify the user outcome, and decide whether a small change or experiment can test the cause. The team should preserve quality and make the next work visible. Immediately accepting every feature treats requests as value evidence; immediately refusing them treats the existing plan as fixed. Neither response tests what users need.

This scenario combines Product, Mindset, Leadership, and Delivery. Product is about value and feedback. Mindset includes learning and adaptation. Leadership can mean facilitating the conversation rather than dictating the answer. Delivery requires a small, testable increment with quality considered. On an exam item, the best option usually responds to the stated evidence and role authority without jumping to a broad reorganization or a large solution before the uncertainty is understood.

Scoring, results, and maintenance

The March 2026 ECO identifies 100 scored items and 20 unscored pretest items, but it does not state a public raw-percentage pass cutoff. Do not convert a practice-test percentage into a guaranteed pass threshold. Use practice performance to locate knowledge gaps, improve pacing, and check whether your decisions are consistent across domains. The certification result, rather than a guessed raw score, determines whether you passed.

Passing the exam earns the certification after PMI completes the certification process. Maintaining PMI-ACP requires 30 professional development units every three years. Plan continuing professional development as part of holding the credential, and record learning as it occurs instead of reconstructing the whole cycle at the end.

A sensible final review

In the final week, stop expanding your notes and concentrate on the tasks that still produce errors. Review how to use feedback, facilitate team decisions, manage flow, preserve quality, and choose an experiment under uncertainty. Take a timed mixed set, analyze it, and leave time to sleep and prepare the testing environment. On exam day, read for the actual problem in the scenario: a method label does not decide the answer. The evidence, goal, roles, constraints, and next useful action do.

Choose an approach that fits the uncertainty

The PMI-ACP outline is framework-agnostic, so preparation should distinguish principles from framework mechanics. Scrum provides defined accountabilities, events, and artifacts for managing iterative work. Kanban emphasizes visualizing workflow, limiting work in progress, and improving flow. Lean focuses on value, learning, and reducing waste. These approaches can be combined when the work and organization call for it, but a candidate should understand what each practice is intended to accomplish before blending them.

A team building a novel service may face uncertainty about both the user problem and the technical solution. Short experiments and frequent user feedback can reduce that uncertainty. A maintenance team receiving a steady stream of requests may benefit from explicit intake policies and work-in-progress limits. A regulated program may need iteration at the team level while preserving evidence, approval points, and traceability required by its environment. The appropriate agile model depends on the risks, constraints, dependencies, and learning needs in the scenario.

Tailoring is not a license to remove useful controls. If a team changes its cadence, it should still make work visible, inspect outcomes, and adapt. If compliance requires documented approval, the team can integrate that approval into its flow instead of treating it as invisible work at the end. The exam can present different methods as plausible. The better answer is the one that responds to the specific context and preserves feedback, quality, and accountable decisions.

Read scenario questions for role and timing

Many wrong answers are attractive because they describe a sound practice applied at the wrong moment or by the wrong person. Before selecting an option, identify who owns the decision. A product owner or product decision-maker typically prioritizes product work; the delivery team contributes estimates and technical information. A facilitator can help the group resolve a conflict without taking the decision away from those accountable for it. A sponsor may set organizational constraints but cannot supply user evidence the team has not gathered.

Then identify whether the prompt asks for the first action, the best long-term response, or a measure of progress. If the team has not understood a defect pattern, a root-cause discussion comes before a broad process change. If the team has already agreed on an improvement and the question asks how to evaluate it, inspect the resulting evidence. If the question says a release must meet a security condition, an answer that postpones the condition for speed is not agile judgment; it ignores a stated constraint.

Watch for absolute language in the options. Always adding a ceremony, never changing a plan, immediately escalating every disagreement, or removing all documentation rarely fits a nuanced scenario. Agile principles encourage adaptation and collaboration, but they do not erase professional responsibility. Prefer a response that is proportionate, transparent, and tied to the facts.

Build readiness from evidence

A study plan should start with a baseline rather than an assumed number of hours. Take a short set of mixed questions aligned to the March 2026 ECO, then sort mistakes by domain and cause. One candidate may miss Product items because backlog language is unfamiliar; another may understand value but rush through exhibits. These call for different practice. Repeat targeted work, then use a fresh mixed set to check whether the reasoning transfers.

Keep a decision log with three fields: what fact mattered, what principle guided the answer, and what made the closest distractor weaker. For a question about a blocked dependency, the relevant fact might be that work cannot progress until another team responds. The principle could be making the dependency visible and coordinating with the other team. A weak distractor might be asking the team to increase its velocity, because effort does not remove the external constraint. This log builds a reusable method instead of a list of memorized answers.

A readiness check should include mixed content, realistic timing, and the interactions represented by the outline. The candidate should be able to explain decisions, manage uncertainty, and finish without relying on repeated guesses. Do not use a single practice score as a pass prediction. PMI does not publish a fixed public raw score cutoff in the March 2026 outline, and practice products differ in difficulty and scoring.

What the credential does and does not establish

PMI-ACP is evidence that the holder met PMI’s certification requirements and passed its assessment. It does not guarantee a particular job, salary, or promotion, and it does not make one framework the right answer for every organization. Employers still evaluate experience, communication, technical knowledge, and the ability to work within their environment. Candidates should describe their actual agile experience accurately and treat the credential as one part of professional development.

The credential also has a maintenance obligation: holders need 30 professional development units in each three-year cycle. That requirement is separate from the 21 hours of formal agile learning needed before applying. One is a pre-exam eligibility condition; the other applies after certification. Keeping those numbers and purposes separate prevents a common planning mistake.