Agile PM Syllabus: Complete Foundation & Practitioner Curriculum

The Agile PM syllabus defines exactly what's testable and exactly what you'll be expected to know, at both Foundation and Practitioner levels. For candidates preparing for the exam, the syllabus is the most important document in the entire certification process. For professionals deciding whether Agile PM is the right credential to pursue, it answers the practical question of what you'll actually learn beyond a marketing description.

This guide walks through the complete Agile PM v3 syllabus as defined by APMG International and the Agile Business Consortium, the joint governing bodies for the credential. Every section reflects the current v3 curriculum, which replaced v2 in 2024 and introduces Scrum integration, multi-team guidance, and a value-delivery emphasis.

How Is the Agile PM Syllabus Structured?

As per APMG's published Learning Outcomes Assessment Model, the Agile PM syllabus is organized into syllabus areas, each with a unique 2-character identifier code. Each area contains multiple learning outcomes, and each outcome is broken down into measurable learning topics assessed in the exam.

The syllabus uses Bloom's Taxonomy of Educational Objectives to classify learning levels. Per APMG:

Foundation tests at Bloom's Level 1 (Knowledge) and Level 2 (Comprehension / Understanding)
Practitioner tests at Bloom's Level 2 (Understand), Level 3 (Apply), and Level 4 (Analyze)

This means Foundation focuses on recall and recognition, knowing what something is, when it's used, and what its purpose is. The Practitioner adds the ability to apply concepts to scenarios and analyze situations to determine appropriate Agile PM responses.

A key syllabus rule: a learning measure is only applied at one qualification level. Topics tested at Foundation are not retested at the same level for Practitioner; instead, Practitioner tests deeper applied versions of the same content.

This structure is important to understand because it shapes how you should study. Foundation preparation emphasizes definitions, terminology, and recognition. Practitioner preparation emphasizes scenario reasoning and applied judgment using the same body of knowledge.

What Topics Are Covered in the Agile PM v3 Foundation Syllabus?

The Foundation syllabus is designed to give candidates a strong working knowledge of the Agile PM framework. Per APMG's published curriculum and the Agile Business Consortium's training materials, the Foundation course covers the following core topic areas:

Background and Business Context

This opening section establishes why Agile PM exists and where it fits in modern project management. Topics include:

Business Agility, what it is and why organizations need it
VUCA (Volatility, Uncertainty, Complexity, Ambiguity) and its impact on project work
The Agile Manifesto, its four values, and twelve principles
Project management vs. product management in an Agile environment
The difference between traditional, lightweight, and Agile project approaches

Agile PM Philosophy and the Eight Principles

The Agile PM philosophy provides the underpinning rationale for all Agile PM practices. The eight DSDM-derived principles form the framework's foundation:

Focus on the business need
Deliver on time
Collaborate
Never compromise quality
Build incrementally from firm foundations
Develop iteratively
Communicate continuously and clearly
Demonstrate control

Candidates are expected to know each principle, understand its purpose, and recognize how each applies in project situations.

The Agile PM Lifecycle

Per the Agile PM v3 curriculum, the lifecycle comprises six distinct phases:

Pre-Project: establishing the project's purpose and confirming readiness to proceed.
Feasibility: assessing whether the project is technically and commercially viable.
Foundations: establishing the project's scope, approach, and team structures.
Evolutionary Development: the iterative delivery phase in which solutions are built and refined.
Deployment: releasing the solution to its intended users.
Post-Project: assessing delivered benefits and learning lessons.

Foundation candidates are expected to know each phase, its purpose, the activities performed, and the products produced.

Roles and Responsibilities

The Agile PM role structure is one of its distinguishing features. Foundation candidates learn the project-level and solution development team roles:

Project-Level Roles:

Business Sponsor, the project's senior business stakeholder
Business Visionary, owner of the high-level business vision
Technical Coordinator, owner of technical strategy and standards
Project Manager, responsible for project management aspects

Solution Development Team Roles:

Team Leader, facilitates day-to-day team activities
Business Ambassador, empowered business representative
Business Analyst supports requirements clarification
Solution Developer builds the solution
Solution Tester, independent quality validation

Supporting Roles:

Workshop Facilitator leads facilitated workshops
AgileCoach provides guidance on Agile PM practice
Business Advisor provides specialist business input

Products

Agile PM defines specific products (deliverables) that are created or evolved during a project. Foundation candidates learn the purpose of each product and when in the lifecycle it's produced.

Key Agile Techniques

The Foundation syllabus covers the techniques that distinguish Agile PM in practice:

MoSCoW Prioritization: categorizing requirements as Must have, Should have, Could have, Won't have this time.
Time-Boxing: fixing time and adjusting scope to fit.
Iterative Development: refining work through multiple cycles.
Modelling: using models to support understanding and communication.
Facilitated Workshops: structured collaborative sessions.
Daily Stand-Ups: short coordination meetings (v3 emphasizes Scrum-style implementation).

Planning, Control, and Estimation

Topics include:

Planning in Agile PM (deliverable-focused, multi-level)
Estimation approaches
Control mechanisms for Agile projects
Reporting and progress tracking

Quality, Risk, Testing, and Measurement

Topics include:

Approach to quality in Agile PM
Risk management in Agile contexts
Testing strategies through the lifecycle
Measurement and progress reporting

Requirements Management

How requirements are captured, refined, and managed iteratively through the project.

People, Teams, and Interactions

Topics include:

Building effective Agile teams
Empowerment and self-organization
Communication patterns
Stakeholder engagement

What Additional Topics Are Covered at Agile PM v3 Practitioner Level?

The Practitioner syllabus doesn't introduce entirely new topics, it tests applied judgment on the topics established at Foundation level. Per APMG's published Practitioner learning outcomes, successful Practitioner candidates should demonstrate their ability to:

Apply the Agile PM philosophy and principles in project situations
Configure Agile project lifecycles to suit different project contexts
Produce and assess Agile project products
Apply various Agile techniques appropriately
Identify appropriate techniques for specific scenarios
Understand Agile project control mechanisms
Outline testing and measurement in Agile projects
Manage requirements in an Agile context

The Practitioner exam consists of 4 scenario-based questions, each with 15 question lines worth 1 mark each, requiring candidates to analyze a project situation and select the most appropriate Agile PM responses.

In practical terms, Practitioner preparation involves taking every Foundation topic and asking "how would I apply this in a specific situation?" rather than "what is this?" The shift from knowledge to applied judgment is the entire purpose of the second-level qualification.

What Are the 8 Principles That Form the Agile PM Foundation?

The eight Agile PM principles are the most testable single set of concepts in the entire syllabus. Foundation candidates should know each principle deeply enough to recognize it in different phrasings and apply it to scenarios.

Principle 1: Focus on the business need. Every decision an Agile PM team makes should support delivery of business value. Activities that don't directly contribute are candidates for removal.

Principle 2: Deliver on time. Time-boxing is the practical implementation of this principle. Date commitments are protected by adjusting scope (via MoSCoW prioritization) rather than extending time.

Principle 3: Collaborate. Agile PM teams operate through active, continuous collaboration across business and technical roles, with stakeholder participation built into the framework.

Principle 4: Never compromise quality. Quality criteria are agreed early, monitored throughout, and never sacrificed to meet date or scope commitments. The Minimum Usable Subset must still be fit for purpose.

Principle 5: Build incrementally from firm foundations. Agile PM emphasizes establishing firm Foundations (lifecycle phase) before evolutionary development begins, sufficient understanding to proceed, but not so much that it constrains adaptation.

Principle 6: Develop iteratively. Solutions are refined through repeated cycles of analysis, design, build, and test, with continuous feedback shaping each iteration.

Principle 7: Communicate continuously and clearly. Multiple communication channels (workshops, stand-ups, modeling, prototypes, demonstrations) supplement formal documentation. Frequent, multi-modal communication reduces misunderstanding.

Principle 8: Demonstrate control. Agile PM projects must remain visibly under control through appropriate planning, monitoring, and reporting, proving to stakeholders that the project is progressing as expected.

Practitioner-level candidates are expected to apply these principles to scenarios, for example, recognizing when a project decision violates a principle or selecting the principle that best applies to a given situation.

What Does the Agile PM Lifecycle Cover?

The Agile PM lifecycle is one of the most distinctive elements of the syllabus and a major reason Agile PM differs from Scrum-only frameworks.

Pre-Project Phase: The starting point. Project ideas are formally documented, business sponsors are identified, and a decision is made to proceed to feasibility or terminate the idea.
Feasibility Phase: Sufficient investigation to determine whether the project is technically and economically viable. The output is a feasibility assessment, including high-level business case and approach.
Foundations Phase: Establishes the project's scope, technical approach, team structure, and prioritization at a level of detail sufficient to begin evolutionary development. This phase is critical because it establishes the firm foundations Principle 5 calls for.
Evolutionary Development Phase: The iterative delivery phase. Solutions are built through multiple time-boxed cycles, each producing usable increments. This is where most of the project's work happens and where the Solution Development Team operates.
Deployment Phase: Releasing the solution to its intended users. May happen multiple times across an Agile PM project for incremental deployments.
Post-Project Phase: Assessing whether expected benefits have been delivered and capturing lessons for future projects.

Foundation candidates learn the purpose of each phase, the activities performed in each phase, and the products produced. Practitioner candidates apply this understanding to scenarios where they must configure or adjust the lifecycle for specific project contexts.

Which Agile PM Roles and Responsibilities Are Tested?

The Agile PM role structure is more granular than Scrum's three roles and reflects the framework's project-management orientation. Per APMG's role definitions:

Role Category	Role	Primary Responsibility
Project-Level	Business Sponsor	Senior business stakeholder; champion of the project
Project-Level	Business Visionary	Owner of the high-level business vision
Project-Level	Technical Coordinator	Owner of technical strategy and standards
Project-Level	Project Manager	Day-to-day project management
Solution Development Team	Team Leader	Day-to-day team facilitation
Solution Development Team	Business Ambassador	Empowered business representative within the team
Solution Development Team	Business Analyst	Requirements clarification and analysis
Solution Development Team	Solution Developer	Building the solution
Solution Development Team	Solution Tester	Quality validation
Supporting	Workshop Facilitator	Facilitates structured workshops
Supporting	AgileCoach	Guidance on Agile PM practice
Supporting	Business Advisor	Specialist business input

Foundation candidates are expected to know what each role does and how the roles interact. Practitioner candidates are tested on applying role responsibilities to scenarios, identifying who should make a particular decision, attend a particular meeting, or produce a particular product.

This role structure makes Agile PM particularly applicable to traditional project management environments because it maps cleanly to roles that those environments already recognize (sponsor, project manager, business analyst, etc.) while introducing Agile-specific responsibilities.

What Are the Key Techniques Covered in the Agile PM Syllabus?

Agile PM emphasizes a set of practical techniques candidates must understand at the Foundation and apply at the Practitioner level.

MoSCoW Prioritization: Categorizing requirements into four levels, Must have, Should have, Could have, Won't have this time. This is one of the most useful and most tested techniques in the syllabus. Practitioner candidates should be able to apply MoSCoW to scenario-based situations and explain why specific categorizations are appropriate.
Time-Boxing: Fixing the time allocated to work and adjusting the scope to fit. Time-boxing is the practical mechanism by which Agile PM delivers Principle 2 (Deliver on time). Candidates learn how time-boxes are structured, how they're managed, and how scope flexes within them.
Iterative Development: Refining solutions through repeated cycles. Agile PM iterations typically run within larger time-boxes, with each iteration producing usable increments.
Modelling: Using models, diagrams, prototypes, mock-ups, and conceptual representations to support understanding and communication. Models are practical tools for stakeholder engagement.
Facilitated Workshops: Structured collaborative sessions with defined roles (workshop facilitator, participants), purposes, and outputs. Facilitated workshops are central to how Agile PM teams make decisions and develop shared understanding.
Minimum Usable Subset (MUS): Identifying the smallest deliverable that provides real business value. Closely related to MVP (Minimum Viable Product) thinking, but more formally embedded in Agile PM planning.
Daily Stand-Ups: Short daily coordination meetings. Agile PM v3 explicitly aligns these with Scrum's Daily Scrum practice as part of its Scrum integration.

Practitioner candidates apply these techniques to scenarios, selecting the one that best addresses a particular project situation, or critiquing how a technique has been applied in a given case.

What's New in the Agile PM v3 Syllabus Compared to v2?

Several substantive changes distinguish v3 from earlier versions of the Agile PM curriculum.

Scrum integration: V3 incorporates Scrum as the core delivery engine for Agile PM projects. Foundation and Practitioner candidates are expected to understand Scrum events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), artifacts (Product Backlog, Sprint Backlog, Increment), and how Scrum operates within the Agile PM lifecycle. This is the most significant change in content.
Shift from product delivery to value delivery: V3 emphasizes creating tangible business value at every stage of the project rather than focusing primarily on product delivery. Exam content reflects this orientation through more scenario questions involving benefits realization, outcome measurement, and value tracking.
Multi-team guidance: V3 includes enhanced guidance on coordinating multiple teams on larger projects. This addresses a gap in earlier versions and reflects the reality of how Agile PM is used in enterprise environments.
Project simulations: Training delivery for v3 includes simulations and storytelling exercises that reinforce Agile-thinking. While the exam itself remains scenario-based rather than simulation-based, course delivery has been redesigned.
Updated Reference Book: The Agile PM v3 Reference Book (now in Edition 2) replaces the Agile PM v2 Handbook as the official syllabus reference. Both Foundation and Practitioner candidates study from this updated text.
v2 retirement: Per APMG, the v2 exam is being phased out and is currently only available in Dutch and French until 30 June 2026. After that, v3 is the only globally available option. Candidates beginning preparation in 2026 should plan for v3.

Per the Agile Business Consortium, Agile PM v3 has had over 230,000 exams taken since the framework's 2010 launch (across all versions). The v3 refresh keeps this widely-adopted framework current with how Agile project management is actually practiced in 2026.

How Are Syllabus Topics Assessed in the Exams?

The APMG assessment model maps each syllabus topic to specific learning and qualification levels.

Foundation exam mapping:

50 multiple-choice questions covering Foundation-level learning outcomes
40 minutes total
Tests Bloom's Level 1 (Knowledge) and Level 2 (Comprehension)
Closed-book; no reference materials permitted during the exam
Passing score: 30 out of 50 (60%)

Practitioner exam mapping:

4 scenario-based questions, each with 15 sub-questions worth 1 mark each
2 hours total
Tests Bloom's Level 2 (Understand), Level 3 (Apply), and Level 4 (Analyze)
Open-book; only the official Agile PM Handbook with handwritten notes or tabs permitted
Passing score: 30 out of 60 (50%)

A practical implication: the Foundation exam rewards quick recall of definitions and concepts, while the Practitioner exam rewards careful scenario reading and structured application of principles to specific situations. The preparation strategies for each are different, even though they cover the same underlying body of knowledge.

Per APMG, official results, including a PDF breakdown of marks by syllabus area, are available in the APMG Candidate Portal after the exam is processed. This breakdown is particularly useful for retakers because it identifies which syllabus areas were weakest, allowing targeted re-study.

Conclusion

The Agile PM syllabus is a clearly structured curriculum covering the philosophy, principles, lifecycle, roles, products, and techniques that distinguish Agile PM from other Agile credentials. Foundation candidates focus on knowing and understanding the content; Practitioner candidates focus on applying and analyzing the same content in real project scenarios.

The 2024 v3 update added Scrum integration, multi-team guidance, and a value-delivery emphasis without changing the syllabus's underlying structure. For candidates preparing in 2026, v3 is effectively the only practical option globally, and the integrated coverage of Scrum within a structured project management framework makes the syllabus more applicable to modern hybrid environments than any earlier version.

Use the syllabus as the anchor for your preparation. Read it before you start. Reference it as you study. Use it to track which areas you've covered and which still need work. Combined with the Agile PM v3 Reference Book, official sample papers from APMG, and accredited training (or disciplined self-study), the syllabus gives you everything you need to walk into the exam with realistic expectations and the right preparation behind you.

To build a structured understanding of the Agile PM syllabus and prepare confidently for both Foundation and Practitioner exams, explore Invensis Learning's Agile PM Certification Training. Learn through expert-led sessions, exam-focused guidance, real-world Agile project scenarios, and practical preparation strategies aligned with the latest Agile PM v3 curriculum.

Frequently Asked Questions

1. What is the Agile PM syllabus, and who publishes it?

The Agile PM syllabus is the official document defining what's testable in the Foundation and Practitioner exams. It's published by APMG International on behalf of the Agile Business Consortium, the joint governing bodies for Agile PM.

2. What's the difference between the Foundation syllabus and the Practitioner syllabus?

The two syllabi cover the same body of knowledge but at different learning levels. Foundation tests recall and comprehension (Bloom's Levels 1–2). Practitioner tests applied judgment and analysis (Bloom's Levels 2–4) using the same content.

3. How many syllabus areas does Agile PM cover?

The syllabus is organized into multiple areas covering background, philosophy and principles, lifecycle, roles, products, techniques, planning and control, quality and risk, requirements, and people and teams. Each area has a unique two-character identifier code in APMG's official documentation.

4. What are the 8 Agile PM principles?

The eight Agile PM principles are: Focus on the business need; Deliver on time; Collaborate; Never compromise quality; Build incrementally from firm foundations; Develop iteratively; Communicate continuously and clearly; Demonstrate control.

5. How many lifecycle phases does Agile PM cover?

Six: Pre-Project, Feasibility, Foundations, Evolutionary Development, Deployment, and Post-Project.

6. How many roles does Agile PM define?

Agile PM defines roles across three categories: project-level (Business Sponsor, Business Visionary, Technical Coordinator, Project Manager), Solution Development Team (Team Leader, Business Ambassador, Business Analyst, Solution Developer, Solution Tester), and supporting (Workshop Facilitator, AgileCoach, Business Advisor).

7. What is MoSCoW prioritization?

A technique for categorizing requirements as Must have, Should have, Could have, or Won't have this time. MoSCoW is one of the most heavily tested techniques in the Agile PM syllabus.

8. Does the Agile PM v3 syllabus include Scrum?

Yes. Agile PM v3 integrates Scrum as the core delivery engine, including Scrum events, artifacts, and roles, where they support Agile PM project delivery. This is one of the most significant content changes from v2.

9. Is the Agile PM Reference Book required for both exams?

Yes. The Agile PM v3 Reference Book (Edition 2) is the official reference for both Foundation and Practitioner. For the Foundation, you study from it but cannot use it during the closed-book exam. For the Practitioner, the Handbook is permitted during the open-book exam.

10. How does Bloom's Taxonomy apply to the Agile PM syllabus?

APMG uses Bloom's Taxonomy to define learning levels. Foundation tests Level 1 (Knowledge) and Level 2 (Comprehension). Practitioner tests Levels 2 (Understand), 3 (Apply), and 4 (Analyze). Each measurable topic is assigned to a specific learning level and qualification.

11. Where can I download the official Agile PM v3 syllabus?

APMG-accredited training organizations publish the syllabus alongside their course materials, and the official syllabus is referenced in the Agile PM v3 Reference Book. Accredited Training Organizations (ATOs) listed on APMG's website also distribute the syllabus to enrolled students.

12. How much of the exam content is on the Agile PM principles vs. lifecycle vs. techniques?

APMG does not publish a fixed weighting, but in practice, the principles, lifecycle, and roles together account for the majority of Foundation questions. Techniques (MoSCoW, time-boxing, iterative development) and products are also heavily tested. Practitioner scenarios typically blend principles, lifecycle understanding, and application of techniques within each question.

13. Will the syllabus change again before 2027?

APMG periodically updates Agile PM curricula. V3 was introduced in 2024 and reflects substantial updates from v2. Per APMG's communication, no further major updates are signaled in the near term, but practitioners should monitor the APMG and Agile Business Consortium websites for announcements.