How Hard Is the PMI-ACP Exam?

The Project Management Institute (PMI) does not make the numbers easy to reason about, either: there is no published pass rate and no published passing score for the PMI Agile Certified Practitioner (PMI-ACP) exam. Results come back as proficiency levels per domain — Above Target down to Needs Improvement — so anyone quoting "you need 70%" or "the pass rate is X%" is guessing. Difficulty here has to be judged on the exam's design, and that is what this article does.

What you are actually up against

The current exam is 120 questions in 180 minutes — a workable 90 seconds per question, but only if you do not stall on long scenarios. Question formats go beyond single-answer multiple choice: expect multiple-response items, drag-and-drop, and exhibit-based questions that make you read a chart or board before answering. Since the content refresh, everything maps to four domains: Mindset (28%), Leadership (25%), Product (19%) and Delivery (28%).

None of that structure is what makes the exam hard. What makes it hard is the style of the questions.

Why PMI-ACP questions feel tricky

Almost every question is a judgement call

Typical PMI-ACP items describe a live situation — a stakeholder demanding a fixed scope, a team member dominating retrospectives, velocity swinging wildly — and ask what you should do next or first. Two or three options will be things a competent professional might genuinely do. The credited answer is the one that best expresses agile values: collaborate before escalating, inspect and adapt before re-planning, deliver value before perfecting process. If you have only learned definitions, every option reads as defensible, and that is precisely the trap.

"Correct at work" is not always correct on the exam

Experienced practitioners carry their organisation's habits into the exam room. Perhaps your company's version of agile involves a project manager assigning sprint tasks, or status reports substituting for reviews. The exam grades against PMI's framework-agnostic ideal, not your team's reality — so the more your workplace bends agile, the more you must consciously answer as the textbook practitioner rather than as yourself.

The exam is deliberately broader than Scrum

PMI-ACP draws on Scrum, Kanban, Extreme Programming, Lean and general agile leadership. Candidates whose entire agile education is a Scrum course meet unfamiliar vocabulary and, worse, keep choosing Scrum-mechanical answers in scenarios that call for a principle-level response. Breadth, not depth, is the differentiator.

Distractors are engineered to flatter old instincts

Wrong options tend to fall into recognisable families: too directive (decide for the team), too predictive (lock the plan down), too slow (defer value for documentation), or too passive (do nothing and hope). They feel safe because they mirror traditional project management instincts. Learning to name these patterns is the single biggest difficulty-reducer available to you — our PMI-ACP preparation guide builds a full study plan around exactly that skill.

Who finds the PMI-ACP hard — and who does not

Finds it fair: a delivery lead who has worked across Scrum and Kanban teams, coached rather than commanded, and can explain why agile practices exist. For this profile the exam mostly confirms judgement they already exercise; their risk is unfamiliar exam formats and PMI-specific phrasing rather than content.

Finds it harder than expected: a certified scrum master from a single-framework background. The Scrum questions feel easy; the Lean, XP and leadership scenarios do not, and the framework-agnostic scoring punishes reflexive Scrum answers.

Finds it genuinely difficult: a traditional project manager moving into agile with limited hands-on team experience. Every situational question requires mentally overriding predictive instincts, and the required 28 hours of agile training alone rarely rewires that. This candidate needs the longest runway — and honest self-assessment before booking.