Who should get the PMI-ACP certification?
The PMI-ACP is designed for project professionals who work on agile teams or lead agile projects. It requires 2,000 hours of general project experience and 1,500 hours of agile project experience within the past 3 years, plus 21 contact hours of agile training. It is best suited for Scrum Masters, agile project managers, product owners, and technical leads who want a vendor-neutral agile credential recognized across industries.
The PMI Agile Certified Practitioner (PMI-ACP) is the Project Management Institute's practitioner-level agile credential. Unlike Scrum-specific certifications such as the CSM (Certified ScrumMaster) or CSPO (Certified Scrum Product Owner), the PMI-ACP is explicitly framework-agnostic. It tests competency across Scrum, Kanban, Lean, Extreme Programming (XP), and SAFe, making it a strong credential for professionals working in organizations that use multiple agile frameworks or are transitioning between them.
As of 2024, PMI reports over 38,000 active PMI-ACP holders globally. The credential has grown significantly since its launch in 2011, driven by the widespread adoption of agile practices outside the software development context where agile originated. Healthcare, financial services, construction, and government organizations are increasingly using agile or hybrid approaches, expanding the relevant audience for the PMI-ACP.
PMI-ACP Eligibility Requirements
The PMI-ACP has a more nuanced eligibility structure than either the CAPM or PMP because it requires both general project experience and specific agile project experience.
| Requirement | Details |
|---|---|
| General project experience | 2,000 hours within the past 5 years |
| Agile project experience | 1,500 hours within the past 3 years |
| Agile training | 21 contact hours of agile-focused education |
| Education | No degree requirement |
General project experience covers the same types of work that qualify for the PMP -- leading or contributing to project teams. Unlike the PMP, the PMI-ACP does not require that you led projects; team member experience counts.
Agile project experience must be specifically on projects that used agile or iterative approaches. This includes Scrum sprints, Kanban flow management, XP iterations, SAFe PI planning, or any formalized iterative delivery methodology. Ad-hoc "kind of agile" work where your team did standups without a formal framework is a gray area -- document it in terms of specific agile practices used.
21 contact hours of agile training must come from structured educational sources. Most Scrum certifications (CSM, CSPO, etc.) and PMI-authorized agile courses satisfy this requirement. If you hold a CSM, those 16 training hours count toward the 21 hours, and you just need an additional 5 hours from another agile course.
Can PMP Experience Count Toward PMI-ACP?
Yes. If you have already earned your PMP, your documented project management experience can satisfy the 2,000-hour general project experience requirement. The 1,500 hours of agile-specific experience must be separately documented.
PMI-ACP Exam Structure
The PMI-ACP exam was updated in 2023 to align with the current state of agile practice, with increased coverage of scaling frameworks and agile leadership.
| Exam Characteristic | Details |
|---|---|
| Number of questions | 120 |
| Exam duration | 3 hours (180 minutes) |
| Question types | Multiple choice, multiple response, matching |
| Passing score | Approximately 65% (not officially published) |
| Exam delivery | Pearson VUE testing center or online proctored |
| Exam fee (PMI member) | $435 |
| Exam fee (non-member) | $495 |
| Renewal cycle | 30 PDUs every 3 years |
The PMI-ACP exam is shorter than the PMP (120 vs. 180 questions) but tests deeper agile fluency within a narrower subject domain.
PMI-ACP Exam Content Domains
The 2023 PMI-ACP exam is organized around seven domains that reflect the full breadth of agile practice.
Domain 1: Agile Principles and Mindset (16%)
This domain tests your understanding of the philosophical foundation of agile practice. Questions address the Agile Manifesto values and 12 principles, the servant leader mindset, agile team dynamics, and the conditions that make agile appropriate for a project context.
Key concepts:
- The four Agile Manifesto values and their practical implications
- The 12 principles behind the Agile Manifesto
- How to create an agile-friendly organizational environment
- The distinction between following agile practices and having an agile mindset
- When agile is more appropriate than predictive approaches (high uncertainty, evolving requirements, customer collaboration availability)
"Adopting agile practices without developing an agile mindset produces fragile, ceremony-heavy teams that frustrate everyone. The PMI-ACP tests whether candidates understand agile thinking, not just agile ceremonies." -- Jim Highsmith, co-author of the Agile Manifesto
Domain 2: Value-Driven Delivery (20%)
This domain addresses how agile teams prioritize and deliver work to maximize business value. It is the most heavily weighted domain and appears throughout exam scenarios.
Key concepts:
- Minimum Viable Product (MVP): The smallest version of a product that delivers learning about customer needs
- Prioritization techniques: MoSCoW (Must Have, Should Have, Could Have, Won't Have), Kano model, weighted shortest job first, value-based prioritization
- Product backlog management: Refinement, story splitting, acceptance criteria, definition of ready
- Release planning: Determining what will be delivered in each release based on velocity and priorities
- Incremental delivery: Delivering value in small, frequent increments rather than a single large release
Domain 3: Stakeholder Engagement (17%)
Effective stakeholder engagement is critical in agile environments because customers and users are actively involved in the development process rather than receiving a specification and waiting for delivery.
Key concepts:
- Customer collaboration: Techniques for involving customers in backlog grooming, sprint reviews, and acceptance validation
- Active listening: Facilitation skills for eliciting requirements and feedback
- Managing stakeholder expectations: Communicating velocity, capacity, and sprint outcomes honestly
- Negotiation: Scope negotiation with stakeholders within sprint and release constraints
- Wireframes and prototyping: Using visual tools to validate requirements before development
Domain 4: Team Performance (16%)
This domain reflects the agile principle that self-organizing, cross-functional teams outperform traditionally managed teams. Questions test how to build, enable, and improve high-performing agile teams.
Key concepts:
- Team formation stages: Tuckman's model (Forming, Storming, Norming, Performing, Adjourning) applied to agile teams
- Self-organization: Enabling teams to make their own decisions about how to do the work
- Cross-functional teams: Teams with all skills needed to deliver without external dependencies
- Retrospective facilitation: Techniques for effective Sprint Retrospectives (Start/Stop/Continue, 5 Whys, Sailboat)
- Coaching and mentoring: Developing agile capability within the team
- Team velocity: Using velocity trends to forecast capacity and identify performance issues
Domain 5: Adaptive Planning (12%)
Agile planning is fundamentally different from predictive planning. Rather than building a detailed plan at the start, agile teams plan at multiple levels and update plans based on empirical data.
Key concepts:
- Levels of planning: Portfolio, roadmap, release, sprint, and daily planning
- Rolling wave planning: Detailed planning for near-term work, high-level planning for future work
- Story estimation: Story points, planning poker, affinity estimation
- Velocity-based forecasting: Using historical velocity to predict release dates and feature delivery
- Iteration planning: Sprint planning meetings, sprint goals, sprint commitments
"In agile, the plan is not the goal. The goal is the working product. Planning is a continuous learning exercise that improves forecast accuracy over time." -- Mary and Tom Poppendieck, authors of Lean Software Development
Domain 6: Problem Detection and Resolution (10%)
Agile teams emphasize early problem detection through frequent feedback loops and transparency. This domain tests skills in identifying, analyzing, and removing impediments.
Key concepts:
- Impediment removal: The Scrum Master's primary responsibility; identifying and removing obstacles to team progress
- Daily standup structure: What blocked, what was done, what is next; surfacing impediments daily
- Risk management in agile: Risk-adjusted backlog, risk spikes, risk burndown chart
- Technical debt management: Identifying, documenting, and planning to address technical debt
- Escaped defects: Tracking defects found after release as a quality metric
- Information radiators: Making project status visible through burndown charts, task boards, and cumulative flow diagrams
Domain 7: Continuous Improvement (9%)
Continuous improvement is built into agile through retrospectives, kaizen events, and organizational learning practices.
Key concepts:
- Retrospective outcomes: Action items that change team practices, process improvements implemented in next sprint
- Process tailoring: Adapting the agile framework to fit the team and project context
- Communities of practice: Cross-team knowledge sharing in scaled agile environments
- Inspect and adapt: The Scrum and SAFe principle of regularly reviewing outcomes and adjusting approach
- Kaizen: Lean concept of continuous incremental improvement
Agile Frameworks Covered on the PMI-ACP
The PMI-ACP tests knowledge of multiple agile frameworks. Understanding the distinctions between them is essential for answering framework-specific questions correctly.
Scrum
The dominant agile framework, covered most deeply on the exam. All Scrum roles (Product Owner, Scrum Master, Development Team), events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment) are examinable in detail.
Kanban
Flow-based framework emphasizing visual management, WIP limits, and cycle time optimization. Key exam concepts: WIP limits, cumulative flow diagrams, lead time vs. cycle time, pull systems.
Lean
The foundational philosophy for many agile frameworks. Key lean concepts: eliminate waste, amplify learning, decide as late as possible, deliver as fast as possible, empower the team, build integrity in, see the whole.
The seven wastes of lean software development (from Mary Poppendieck): partially done work, extra features, relearning, handoffs, task switching, delays, defects.
Extreme Programming (XP)
A technically-focused agile method with practices including test-driven development (TDD), pair programming, continuous integration, refactoring, and simple design. The PMI-ACP tests XP concepts at a conceptual level rather than coding-practice depth.
SAFe (Scaled Agile Framework)
SAFe is covered at a conceptual level for teams working at enterprise scale. Key concepts: Agile Release Train (ART), Program Increment (PI), PI Planning, Portfolio Kanban.
PMI-ACP vs. Other Agile Certifications
Candidates choosing between PMI-ACP and framework-specific certifications should understand where each credential positions them.
| Certification | Provider | Scope | Renewal |
|---|---|---|---|
| PMI-ACP | PMI | Vendor-neutral, multi-framework | 30 PDUs / 3 years |
| CSM | Scrum Alliance | Scrum only | 20 SEUs / 2 years |
| PSM I | Scrum.org | Scrum only | No renewal required |
| SAFe Agilist | Scaled Agile | SAFe framework | Annual renewal |
| ICAgile ICP | ICAgile | Foundational agile | No renewal |
The PMI-ACP's primary advantage over Scrum-specific certifications is breadth: it demonstrates competency across the agile landscape rather than expertise in one framework. This breadth is valuable in organizations using multiple frameworks or in consulting roles where advisors must work with diverse client environments.
The Scrum-specific certifications (CSM, PSM) are better choices for candidates whose roles are exclusively Scrum-based or for those who want to deepen Scrum expertise rather than broaden across frameworks.
Study Strategy for the PMI-ACP
The PMI-ACP exam rewards practical agile experience and conceptual understanding over memorization. Study strategies should reflect this.
Recommended Study Timeline
- 4-6 weeks for candidates with 2+ years of active agile experience
- 8-10 weeks for candidates with limited agile experience who are studying agile frameworks for the first time
Primary Study Resources
- PMI-ACP Examination Content Outline (free at pmi.org): The official exam blueprint
- Agile Practice Guide (free to PMI members): The primary agile reference for the exam
- Agile Estimating and Planning by Mike Cohn: Excellent for Domain 5 (Adaptive Planning)
- The Art of Agile Development by James Shore: Practical agile development reference
- Mike Griffiths PMI-ACP Exam Prep: The leading dedicated PMI-ACP study guide
- PMI-ACP practice exam simulator: PrepCast or similar with 600+ aligned questions
Frequently Asked Questions
Is the PMI-ACP harder than the PMP exam? The PMI-ACP and PMP are different in scope, not necessarily in difficulty. The PMI-ACP tests deeper agile fluency across multiple frameworks but is shorter (120 questions vs. 180) and does not include EVM calculations or the breadth of predictive project management content. Candidates with genuine agile project experience typically find the PMI-ACP more straightforward than the PMP.
Does having a CSM or CSPO help prepare for the PMI-ACP? Yes significantly. Scrum certification training provides foundational agile knowledge and typically satisfies part or all of the 21 contact hours requirement. However, CSM and CSPO training covers only Scrum, while the PMI-ACP tests Kanban, Lean, XP, and SAFe as well. Additional study of non-Scrum frameworks is required regardless of Scrum certification status.
Can I earn both the PMP and PMI-ACP? Yes, and many professionals hold both credentials. The PMP and PMI-ACP complement each other well: the PMP demonstrates competency across all delivery approaches while the PMI-ACP signals specialized agile depth. Employers in technology, consulting, and financial services frequently list both credentials as preferred for senior project management roles.
References
- Project Management Institute. "PMI-ACP Examination Content Outline." PMI.org, 2023.
- Project Management Institute. Agile Practice Guide. PMI and Agile Alliance, 2017.
- Beck, Kent et al. "Manifesto for Agile Software Development." agilemanifesto.org, 2001.
- Griffiths, Mike. PMI-ACP Exam Prep: A Course in a Book for Passing the PMI Agile Certified Practitioner Exam. RMC Learning Solutions, 2022.
- Cohn, Mike. Agile Estimating and Planning. Prentice Hall, 2005.
- Poppendieck, Mary and Tom. Lean Software Development: An Agile Toolkit. Addison-Wesley, 2003.
- Highsmith, Jim. Agile Project Management: Creating Innovative Products, Second Edition. Addison-Wesley, 2009.