Key Agile Methodologies Assessed in the PMI-ACP Exam

The PMI Agile Certified Practitioner (PMI-ACP)® certification is unique among agile credentials because it doesn’t focus on a single methodology. Instead, the exam covers a wide range of agile frameworks and practices, reflecting the diverse, real-world application of agile in modern project environments.

This article explores the key agile methodologies assessed in the PMI-ACP exam, providing an overview of each approach and its relevance to the exam content.

The PMI-ACP exam covers multiple Agile methodologies and frameworks commonly used in modern organizations. A comprehensive PMI-ACP Training Course can help you understand the similarities, differences, and practical applications of these approaches.

---

Why Multiple Methodologies Matter

The PMI-ACP is framework-neutral. It recognizes that agile is not one-size-fits-all and that organizations often blend methods to meet their needs. As a result, candidates are expected to understand the principles and practices of several agile methodologies, not just memorize one system.

Understanding multiple methodologies also prepares you to:

• Adapt agile practices in hybrid environments
• Evaluate and combine techniques based on team and project context
• Apply agile principles beyond any one framework

---

1. Scrum

Overview:
Scrum is one of the most widely adopted agile frameworks, focused on delivering value through iterative, time-boxed development cycles called sprints.

Key Concepts for the Exam:

• Roles: Product Owner, Scrum Master, Development Team
• Artifacts: Product Backlog, Sprint Backlog, Increment
• Events: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective
• Empirical process control and servant leadership

Scrum provides the foundational language and structure for many exam questions.

---

2. Kanban

Overview:
Kanban is a visual workflow management method that emphasizes continuous delivery, work-in-progress (WIP) limits, and flow efficiency.

Key Concepts for the Exam:

• Visual boards and work item tracking
• WIP limits to prevent bottlenecks
• Lead time, cycle time, throughput
• Pull-based systems and flow metrics
• Continuous improvement and feedback loops

Kanban is often compared to Scrum on the exam to test your ability to distinguish between frameworks.

---

3. Lean

Overview:
Lean focuses on maximizing customer value while minimizing waste, originally derived from manufacturing but now widely applied in software and knowledge work.

Key Concepts for the Exam:

• The 7 types of waste (e.g., waiting, overproduction)
• Just-in-time delivery
• Continuous improvement (Kaizen)
• Value stream mapping
• Respect for people and systems thinking

Lean principles influence how agile teams prioritize and streamline delivery.

---

4. Extreme Programming (XP)

Overview:
XP is a technical agile framework focused on engineering practices that improve code quality and responsiveness to change.

Key Concepts for the Exam:

• Pair programming
• Test-driven development (TDD)
• Continuous integration
• Refactoring
• Collective code ownership
• Simple design and frequent releases

XP practices may appear in scenario-based questions related to team collaboration and product quality.

---

5. Crystal

Overview:
Crystal is a family of lightweight, people-centric agile methodologies tailored to project size and criticality.

Key Concepts for the Exam:

• Emphasis on team communication and flexibility
• Methodology selection based on team size and project complexity (e.g., Crystal Clear, Crystal Orange)
• Minimalism in tools and documentation

Crystal promotes the idea that no single process fits all projects, reinforcing the importance of context.

---

6. Dynamic Systems Development Method (DSDM)

Overview:
DSDM is a robust, business-focused agile framework emphasizing structured governance, frequent delivery, and active user involvement.

Key Concepts for the Exam:

• Principles such as fitness for business purpose, iterative development, and collaboration
• MoSCoW prioritization (Must Have, Should Have, Could Have, Won’t Have)
• Fixed time and cost with flexible scope
• Business sponsor and facilitator roles

DSDM may show up in exam questions about project constraints and prioritization techniques.

---

7. Feature-Driven Development (FDD)

Overview:
FDD is a model-driven, incremental approach to software development based on designing and building features.

Key Concepts for the Exam:

• Domain modeling
• Feature lists and feature teams
• Five-step process (developing overall model to building by feature)
• Short, iterative cycles
• Emphasis on documentation and design

While less commonly used today, FDD is still included in the PMI-ACP syllabus to ensure broad framework awareness.

---

How These Methodologies Are Tested

The PMI-ACP exam uses scenario-based questions to assess your understanding of:

• When to use one methodology over another
• How to blend practices to meet team or business needs
• Differences in roles, planning techniques, and delivery models
• Underlying principles shared across methodologies

Many questions challenge you to apply agile principles in context, rather than simply recall framework definitions.

---

Conclusion

The PMI-ACP exam evaluates your knowledge of several key agile methodologies, each offering unique strengths and perspectives on delivering value in dynamic environments. To prepare effectively, go beyond surface-level definitions—focus on the practical application, comparative understanding, and principles that guide agile teams across frameworks.

Mastering this breadth of agile knowledge will not only help you pass the exam but also make you a more adaptable and effective agile practitioner.