PMI Agile Certified Practitioner Cheat Sheet

PMI-ACP Tests Agile Across Multiple Frameworks — Not Just Scrum

Scrum, Kanban, XP, Lean, and SAFe all appear. Knowing only one framework will expose you in 40% of the questions.

Among the harder certs

Avg: Approximately 62–67%

Pass: 750 / 1000

Most candidates understand PMI Agile Certified Practitioner concepts — and still fail. This exam tests how you apply knowledge under pressure.

Core Framework

PMI-ACP Framework Selection Map

PMI-ACP covers 7 domains: Agile Principles & Mindset, Value-Driven Delivery, Stakeholder Engagement, Team Performance, Adaptive Planning, Problem Detection & Resolution, and Continuous Improvement. The right framework depends on the scenario's scale and context.

01
Scrum — Iterative delivery, fixed sprints, three accountabilities
02
Kanban — Flow-based, WIP limits, continuous delivery
03
XP (Extreme Programming) — TDD, pair programming, continuous integration
04
Lean — Eliminate waste, amplify learning, deliver fast
05
SAFe — Enterprise agile scaling, PI Planning, ARTs

Scenario Traps

Wrong instinct vs correct approach

The team's velocity is declining over multiple sprints

✕ Wrong instinct

Add more people to the team to restore velocity

✓ Correct approach

Investigate root causes in retrospectives — technical debt, scope creep, or team dynamics are typical culprits; adding people often decreases velocity in the short term (Brooks' Law)

Stakeholders want detailed long-term project plans

✕ Wrong instinct

Provide a traditional project plan with fixed scope, schedule, and budget

✓ Correct approach

Provide a release roadmap with rolling-wave planning — commit to near-term iterations in detail, estimate future work as ranges, and communicate that plans will evolve based on learning

The development team wants to skip testing to meet a release date

✕ Wrong instinct

Allow it since delivering on time is the priority

✓ Correct approach

Protect the Definition of Done — shipping without testing creates technical debt; negotiate scope reduction instead of quality reduction

Quick Rules

Know these cold

▸ Know which framework applies to the scenario before selecting an answer
▸ WIP limits are a Kanban concept — don't apply sprint thinking to flow scenarios
▸ Technical debt is a business risk, not just a technical concern
▸ Brooks' Law — dding people to a late project makes it later
▸ Rolling wave planning — etail near-term, estimate long-term
▸ Definition of Done is non-negotiable — reduce scope, not quality
▸ Agile risk management — ake risks visible, small experiments reduce uncertainty

Self Check

Can you answer these without checking your notes?

In this scenario: "The team's velocity is declining over multiple sprints" — what should you do first?

Investigate root causes in retrospectives — technical debt, scope creep, or team dynamics are typical culprits; adding people often decreases velocity in the short term (Brooks' Law)

In this scenario: "Stakeholders want detailed long-term project plans" — what should you do first?

Provide a release roadmap with rolling-wave planning — commit to near-term iterations in detail, estimate future work as ranges, and communicate that plans will evolve based on learning

In this scenario: "The development team wants to skip testing to meet a release date" — what should you do first?

Protect the Definition of Done — shipping without testing creates technical debt; negotiate scope reduction instead of quality reduction

Failure Patterns

Common Exam Mistakes — What candidates get wrong

Applying Scrum answers to Kanban scenarios

Kanban has no sprints, no fixed iterations, and no roles. Questions about continuous flow, WIP limits, and cycle time are Kanban-specific. Applying sprint-based thinking to flow-based scenarios is wrong.

Treating technical debt as a developer problem only

PMI-ACP treats technical debt as a business risk that the entire team — including the Product Owner — must manage. Excluding business stakeholders from technical debt discussions misses the agile value perspective.

Confusing release planning with sprint planning

Release planning sets the roadmap across multiple sprints; sprint planning commits to the next iteration. Candidates mix these planning horizons when questions involve both short-term commitment and long-term forecasting.

Misidentifying servant-leadership as passivity

Agile leaders actively remove impediments, create psychological safety, and enable team performance. Passivity is not servant-leadership. The exam tests proactive facilitation.

Selecting XP practices for non-engineering scenarios

Test-driven development, pair programming, and refactoring are XP engineering practices. Applying them outside engineering contexts is a common error.

PMI-ACP requires multi-framework fluency. Test whether you can apply the right framework to the right scenario.

Start Diagnostic Test → View all exams