Agile project management is the part of the PMP exam that catches the most experienced candidates off guard. Senior project managers walk in confident about schedules, baselines, earned value, and risk responses, then lose half their points on questions about backlog refinement, sprint reviews, servant leadership, and what a Scrum Master would actually do when a developer pulls a senior architect aside to skip the Daily Scrum.
The reason is structural. About half of the PMP exam tests agile and hybrid delivery. PMI is no longer testing whether you can manage a predictive project. It is testing whether you can choose the right approach for a given context, lead a team without command-and-control reflexes, and recognise when a traditional response is the wrong answer. Candidates who studied from older PMBOK editions, or who learned project management entirely in a waterfall environment, often discover this on exam day rather than during preparation.
This guide is the agile reference for PMP candidates who want to close that gap properly. It covers what PMI actually tests, the three delivery approaches you need to distinguish, the agile frameworks the exam draws from (Scrum, Kanban, and a working understanding of SAFe), what hybrid delivery looks like in real organisations, the question patterns the PMP uses to test agile thinking, and the natural next credential for PMs who want to specialise.
If you are still mapping out the broader exam, our PMP exam format guide and the 2026 PMP Exam Content Outline cover the structure and domain weightings. This article goes deep on the agile half.
Table of Contents
- What PMI Actually Tests
- The Three Delivery Approaches
- Scrum
- Kanban
- SAFe Overview
- Hybrid Delivery in Practice
- How Agile Appears in PMP Exam Questions
- Beyond PMP: The PMI-ACP
- Frequently Asked Questions
- Conclusion
What PMI Actually Tests
PMI publishes the breakdown clearly in the PMP Exam Content Outline. The exam is organised into three domains: People at 42%, Process at 50%, and Business Environment at 8%. Cutting across those domains, PMI states that approximately half of the exam questions reflect predictive approaches and the other half reflect agile or hybrid approaches. Whether a question is “agile” or “predictive” is rarely the right way to think about it. The exam is testing whether you choose the appropriate response for the context the question describes.
That distinction matters. PMI is not asking you to memorise Scrum ceremonies and recite the Agile Manifesto. It is asking you to recognise, from a short scenario, whether the team is operating in a predictive context, an adaptive one, or somewhere in between, and to pick the response that fits.
The five themes that come up repeatedly are worth naming directly:
Servant leadership. PMI’s view of the project manager has shifted firmly away from command-and-control. The exam rewards answers that empower teams, remove impediments, coach, and protect focus. It punishes answers where the PM directs, assigns, or escalates without first engaging the team.
Adaptive planning. PMI expects you to know that detailed up-front plans are appropriate when uncertainty is low, and that progressive elaboration, rolling-wave planning, and iteration are appropriate when it is high.
Value delivery and prioritisation. The exam tests whether you understand that value should be delivered early and incrementally where possible, and whether you can prioritise based on business value rather than effort or sequence.
Embracing change. A common trap in PMP scenarios is the appealing but wrong answer of “follow the change control process.” Sometimes that is correct. In agile contexts, it is often wrong, and the correct answer is to absorb the change into the next iteration’s planning.
Tailoring. PMI explicitly tests whether you can adapt your approach based on project, team, and organisational context. There is no single right way.
Internalise those five themes and a large class of agile-flavoured PMP questions becomes much easier to answer correctly.
The Three Delivery Approaches
PMI groups all project work into three delivery approaches. You need to be able to recognise which one a scenario describes, and you need to know when each is appropriate. Almost every agile question on the PMP exam comes back to this distinction.
Predictive (also called plan-driven or waterfall). The full scope, schedule, and cost are defined up front. The work is delivered as a single integrated product or in large phased releases. Predictive approaches work well when requirements are stable, the technology and methods are well understood, regulatory or contractual constraints demand fixed scope, and the cost of late change is high. Construction, large infrastructure, and most regulated capital projects sit here.
Adaptive (also called agile or iterative-incremental). Scope is treated as variable. The team plans in detail only for the next short iteration, delivers working increments frequently, and uses customer feedback to refine what gets built next. Adaptive approaches work well when requirements are uncertain or evolving, the customer cannot fully describe what they want until they see it, the cost of late change is low, and time-to-market matters more than upfront precision. Most product development, software, and innovation work sits here.
Hybrid. A blend of predictive and adaptive elements within the same project. The most common pattern is a predictive overall plan with adaptive delivery inside specific phases or workstreams. A hardware-software product where the hardware is predictive and the software is agile. A regulated programme where the compliance documentation is plan-driven and the implementation runs in sprints. Hybrid is now the most common approach in large enterprises, and PMI tests it heavily.
The relevant decision factor is rarely “which approach do we prefer.” It is the combination of requirements certainty, technology familiarity, regulatory environment, customer accessibility, and team experience. PMI uses tools like the Stacey complexity matrix and agile suitability filters to frame this decision in the underlying material, even though the exam rarely names them explicitly.
A useful mental check during the exam: read the scenario, identify the level of uncertainty in requirements and approach, and then decide whether the question is testing predictive thinking, agile thinking, or the judgement to switch between them. Most candidates who fail the agile portion of the exam fail because they default to predictive answers in adaptive scenarios, or vice versa.
Scrum
Scrum is the most widely tested agile framework on the PMP exam, and it is the one most candidates already know in fragments. The fragments are not enough. The exam tests whether you understand the framework as a coherent system, not just whether you can list the ceremonies.
The roles. Scrum has three accountabilities. The Product Owner owns the what: the product vision, the backlog, the prioritisation, and the acceptance of completed work. The Scrum Master is a servant leader who owns the how-the-team-works: removing impediments, coaching, protecting the team’s focus, and enabling improvement. The Developers are the people who do the work and collectively own delivery. There is no project manager inside the Scrum framework, which is itself a frequent exam point. The PM either takes on the Scrum Master accountability, sits outside the team in a coordinating role across multiple Scrum teams, or operates at a programme level.
The events. Five events structure the work. The Sprint is the container for everything else, typically one to four weeks, ending with a potentially releasable increment. Sprint Planning sets the goal and the work for the upcoming Sprint. The Daily Scrum is a short team coordination event focused on the path to the Sprint Goal, not a status report to the Scrum Master. The Sprint Review inspects the increment with stakeholders and adapts the backlog. The Sprint Retrospective inspects how the team worked and identifies one or two specific improvements for the next Sprint.
The artefacts. Three artefacts hold the work. The Product Backlog is the ordered list of everything that might be delivered, owned by the Product Owner. The Sprint Backlog is the subset the team has committed to in the current Sprint, plus the plan for delivering it. The Increment is the sum of all completed work, meeting the Definition of Done. Each artefact has a commitment attached: the Product Goal for the Product Backlog, the Sprint Goal for the Sprint Backlog, and the Definition of Done for the Increment.
Common exam traps. PMP scenarios test the boundaries. A stakeholder asking the team to add work mid-Sprint is not handled by the Scrum Master cancelling the Sprint or escalating; the right answer is usually that the Product Owner negotiates the change for a future Sprint, or in extreme cases ends the current Sprint. A team consistently failing to meet its forecast is not solved by adding pressure; the right answer is a retrospective focused on root causes. The Daily Scrum is not a status meeting for managers; the right answer to “the manager wants daily updates” is that the manager attends the Sprint Review or works through the Product Owner.
Scrum is roughly 30% to 40% of the agile content on the PMP exam. Knowing it deeply pays back.
Kanban
Kanban is the second framework you need to know well, and it is the one most candidates underprepare for. The exam tests Kanban concepts in scenarios involving operational work, support teams, continuous delivery contexts, and any team where Sprints do not fit naturally.
The core ideas are different from Scrum, and the differences matter on exam questions.
Visualise the work. Kanban makes all work visible on a board with columns representing the workflow states. The board is not decoration; it is a management tool that surfaces bottlenecks, blocked items, and queues.
Limit Work in Progress. This is the central practice and the most exam-relevant idea. Each column has an explicit WIP limit. When a column is full, no new work can move into it until something leaves. The discipline forces the team to finish before starting and exposes systemic problems quickly.
Manage flow. Kanban optimises for the smooth, steady movement of work through the system. The relevant metrics are cycle time (how long a single item takes from start to finish), throughput (how many items the team finishes per period), and Work in Progress (the count of in-flight items). Little’s Law, which links these three, is occasionally referenced in exam questions.
Make policies explicit. Definitions of “ready” and “done” for each column are written down and visible.
Improve collaboratively, evolve experimentally. Kanban does not require a re-organisation. It is applied to the existing workflow, and improvements happen incrementally based on what the data shows.
Scrum versus Kanban on the exam. Scrum is built around timeboxes (Sprints) and team commitments. Kanban is built around continuous flow and WIP limits. The exam tests whether you can recognise which is appropriate. A team handling unpredictable inbound work (production support, infrastructure, marketing requests) is usually a Kanban scenario. A team building a defined product with batched delivery is usually a Scrum scenario. Hybrid teams using Scrumban (Scrum cadence with Kanban WIP discipline) appear in scenarios where the team is transitioning between models.
If a question describes WIP limits, cycle time, throughput, or pull-based work, the answer is almost certainly grounded in Kanban thinking even if the word is not used.
SAFe Overview
The Scaled Agile Framework (SAFe) is not a heavy area of the PMP exam, but it is the most commonly named scaling framework in real organisations, and PMI expects you to recognise the broad concepts when they appear in scenarios. You do not need to memorise SAFe in the depth required for a SAFe certification. You do need a working understanding.
SAFe coordinates multiple agile teams working on the same product or solution. The unit of organisation is the Agile Release Train (ART), which is a long-lived team-of-teams (typically 50 to 125 people) that delivers value together on a synchronised cadence.
The cadence is the Program Increment (PI), usually 8 to 12 weeks, made up of multiple iterations. Every PI begins with PI Planning, a two-day event where the entire ART aligns on objectives, dependencies, and risks for the upcoming increment. PI Planning is the SAFe ritual most likely to surface in PMP scenarios because it is the visible event that distinguishes scaled agile from team-level agile.
Above the train, SAFe defines portfolio, large solution, and essential levels, each adding governance, funding, and coordination structures. Senior PMs and programme managers usually sit at the portfolio level, where they handle epics, lean budgets, and value stream coordination.
Two competing frameworks worth recognising even in a single sentence: LeSS (Large-Scale Scrum) takes a different philosophy, scaling Scrum with minimal added structure. Disciplined Agile (DA), owned by PMI itself, treats scaling as a context-driven choice and offers a toolkit of process options rather than a single prescriptive framework. The PMP exam favours SAFe references, but PMI’s own DA is gaining ground in scenarios about choosing a way of working.
The practical exam advice is short. Recognise SAFe terminology if it appears (ART, PI, PI Planning, Release Train Engineer, Solution Train, ART Sync). Do not try to memorise the full SAFe diagram. The exam is testing whether you understand that scaling exists and what it looks like, not whether you could lead a SAFe transformation.
Hybrid Delivery in Practice
Hybrid is where most working project managers spend most of their time, and where the PMP exam now tests heavily. The challenge is that hybrid is not a single defined approach. It is a family of patterns, and the exam tests whether you can choose the right blend for the context described.
The most common hybrid patterns worth recognising:
Predictive shell, adaptive delivery. A regulated or capital-intensive programme runs on a predictive overall plan with milestones, gates, and a fixed budget. Inside specific phases (design, software development, integration), teams operate in Sprints with backlogs and retrospectives. This is the dominant pattern in financial services, healthcare, telecoms, and aerospace.
Adaptive build, predictive launch. A product is developed iteratively, but the launch itself (regulatory approval, supply chain ramp, marketing campaign, hardware shipment) is plan-driven with hard dates. Most physical and regulated product launches sit here.
Sequential predictive-then-adaptive. A programme begins with a predictive feasibility, definition, and procurement phase, then transitions to adaptive delivery once the contract is signed and the work begins.
Concurrent predictive and adaptive workstreams. A single programme has multiple workstreams running in parallel, some predictive, some adaptive. The integration layer is the project manager’s responsibility.
In each case, the project manager’s job is to make the seams work. Reporting cadences differ, governance bodies expect different artefacts, teams use different vocabularies, and stakeholders need translation. The PMP exam tests this by asking what a PM should do when, for example, a steering committee expects a Gantt chart but the delivery team works in Sprints. The right answer is almost never “force one approach onto the other.” It is to translate, to align cadences, and to give each side the artefacts they need without breaking how the work is actually done.
A practical observation worth carrying into the exam: the hybrid scenarios PMI writes are usually realistic. If a question describes a programme that sounds like the messy reality of a real organisation, treat it as a hybrid scenario, not a “pick agile or predictive” scenario. The right answer almost always involves tailoring, communicating, and respecting the constraints of both sides.
For senior PMs, the related challenge is risk management across a hybrid environment, where some risks are managed through formal registers and others through team-level threat boards. Our project risk management guide covers both layers in detail.
How Agile Appears in PMP Exam Questions
Agile content does not appear on the PMP exam as a separate section. It is interwoven across the People, Process, and Business Environment domains, and the question patterns are consistent enough to be worth studying directly.
Pattern one: the situational agile question. A short scenario describes a team working in Sprints. Something goes wrong. The question asks what the project manager (or Scrum Master) should do. The wrong answers are usually predictive responses dressed up to look reasonable: “issue a corrective action,” “update the project management plan,” “escalate to the sponsor.” The right answer is usually the agile response: facilitate a retrospective, refine the backlog with the Product Owner, remove the impediment, coach the team.
Pattern two: the trap of “which is more agile.” Two answers will both sound agile. One is genuinely agile in spirit; the other is agile in vocabulary only. For example, both options mention sprints, but one preserves the team’s autonomy and the other has the PM unilaterally re-planning the Sprint. The genuinely agile answer is the one that respects the team’s ownership.
Pattern three: the change request question. A stakeholder requests a change. In a predictive scenario, the answer often runs through the change control board. In an agile scenario, the answer is usually that the Product Owner adds it to the backlog and the team handles it in a future Sprint. The exam tests whether you read the context correctly before answering.
Pattern four: the leadership style question. A team is underperforming, dispirited, or stuck. The wrong answers involve directing, escalating, or replacing. The right answer is almost always servant leadership: coaching, removing impediments, facilitating a conversation, helping the team find its own solution. PMI tests this pattern repeatedly.
Pattern five: the hybrid context question. A scenario has elements of both predictive and adaptive delivery. The question asks how the PM should handle reporting, governance, or stakeholder expectations. The right answer almost always involves tailoring rather than enforcing a single approach.
A practical study technique: when you take practice exams, mark every question where you got an agile-flavoured answer wrong and categorise it into one of these five patterns. After 100 questions, you will see your specific weakness clearly. Most candidates over-default to predictive answers under exam pressure, and the fix is recognising the pattern, not learning more content.
The structured PMP preparation in our PMP Complete Exam Guidance package is built around these question patterns, with a heavy weighting toward the agile and hybrid scenarios that catch experienced predictive PMs out.
Beyond PMP: The PMI-ACP
If you want to go deeper into agile after passing the PMP, the natural next credential is the PMI Agile Certified Practitioner (PMI-ACP). PMI updated the credential significantly in 2026, repositioning it around enterprise agility rather than framework knowledge alone.
What the PMI-ACP covers. The 2026 PMI-ACP exam is built around four domains: Mindset (28%), Leadership (25%), Product (19%), and Delivery (28%). The exam is 120 multiple-choice questions over 180 minutes. Unlike framework-specific certifications (Certified ScrumMaster, Professional Scrum Master), the PMI-ACP is framework-agnostic and tests knowledge across Scrum, Kanban, Lean, XP, and the Disciplined Agile toolkit. PMI’s own positioning is that it validates the practitioner who can choose the right agile action for the context, not the practitioner who has memorised one playbook.
Eligibility. A secondary degree, 2,000 hours of general project experience within the last five years, 1,500 hours of agile project experience within the last three years, and 21 contact hours of formal agile training. Holding a PMP satisfies the general project experience requirement, which makes the path significantly easier for candidates who already cleared that bar. Alternative paths exist for candidates with GAC-accredited degrees or third-party agile certifications.
Why pursue it after PMP. Three reasons that hold up in practice. First, the PMP signals general project management competence; the PMI-ACP signals genuine agile fluency, which is increasingly the differentiator in technology, product, and digital transformation roles. Second, the prerequisite barrier filters out the agile certifications that are easy to acquire and therefore commodity-priced. The PMI-ACP carries weight precisely because it requires documented experience. Third, it pairs naturally with the PMP for senior PMs running hybrid portfolios and large transformations, where credibility on both predictive and adaptive sides is required.
Why some PMs choose Disciplined Agile instead. PMI also offers the Disciplined Agile family of certifications (DASM, DASSM, and the senior coach credentials). Disciplined Agile takes a toolkit approach, recognising that there is no single best way to be agile, and gives practitioners a structured way to choose. For PMs whose work involves leading transformations or coaching multiple teams in different contexts, DASSM in particular is becoming a credible alternative to the PMI-ACP.
Practical recommendation. If your day-to-day work involves leading agile teams or hybrid programmes, take the PMI-ACP. If your work involves enterprise-scale transformation, agile coaching, or process tailoring across multiple teams, look at DASSM. If you are not yet at that level of seniority and are still cementing the PMP, hold off on both until your current credential is earning its keep.
Our PMI Exam Help service covers preparation across the full PMI credential family, including the PMI-ACP, the Disciplined Agile certifications, the PMI-RMP, and the PMI-PBA, for candidates planning their post-PMP credential strategy.
Frequently Asked Questions
How much of the PMP exam is agile? PMI states that approximately half of the PMP exam reflects agile or hybrid approaches. The remaining half reflects predictive approaches. This split applies across all three domains (People, Process, Business Environment) rather than being concentrated in any single section.
Do I need to know Scrum to pass the PMP? Yes. Scrum is the most heavily referenced agile framework on the PMP exam. You should know the three accountabilities, the five events, the three artefacts, the Definition of Done, and the underlying principles well enough to apply them in scenario questions, not just recite them.
Do I need to know Kanban for the PMP exam? Yes, though less deeply than Scrum. You should know WIP limits, flow metrics (cycle time, throughput, WIP), pull-based work, and the difference between Kanban and Scrum. Kanban scenarios appear in PMP questions about operational and support teams.
Is SAFe on the PMP exam? SAFe terminology can appear in scenario questions, but the PMP does not test SAFe in any depth. You should recognise concepts like Agile Release Trains and PI Planning, but you do not need to memorise the full SAFe framework. If your work involves SAFe directly, a separate SAFe certification is more useful.
Should I take the PMP or PMI-ACP first? The PMP, in almost every case. The PMP is the foundational credential, more widely recognised, and a prerequisite-shortcut for the PMI-ACP. The PMI-ACP is most valuable as a follow-up that demonstrates agile depth on top of the PMP.
Is the PMI-ACP retired in 2026? No. The PMI-ACP remains an active PMI certification in 2026 and was updated to a new exam content outline focused on enterprise agility. The Disciplined Agile certifications (DASM, DASSM) are separate offerings, not replacements.
What is the difference between agile and hybrid on the PMP exam? Agile scenarios describe teams operating fully in adaptive cycles (Sprints, continuous flow, evolving requirements). Hybrid scenarios describe projects that combine predictive and adaptive elements, usually with predictive governance over adaptive delivery. The exam tests both, but hybrid scenarios are now the more common pattern in PMP questions.
Do I need to memorise the Agile Manifesto for the PMP? You should understand the four values and twelve principles in concept, not in exact wording. The PMP exam is unlikely to ask you to recite them verbatim. It is very likely to test scenarios where the Manifesto’s underlying values (working software over comprehensive documentation, responding to change over following a plan) drive the correct answer.
How does PMI test servant leadership on the PMP exam? Through scenario questions where the wrong answers involve directing, assigning, escalating, or controlling, and the right answer involves coaching, removing impediments, facilitating, or empowering the team. This pattern recurs across many People domain questions.
Is the PMP exam harder for predictive PMs than for agile PMs? In recent intakes, predictive PMs have reported a steeper learning curve than agile PMs, because the agile content is broader and less familiar to them. Agile PMs typically need to brush up on earned value, scheduling techniques, and procurement, but those areas are more contained.
Will the PMBOK 8 change agile coverage on the PMP exam? PMBOK 8 continues PMI’s direction toward principle-based, approach-agnostic content. The exam reflects the Exam Content Outline rather than the PMBOK directly, so the practical impact is incremental rather than dramatic. Expect more emphasis on tailoring, value, and outcomes; do not expect a wholesale rewrite of the agile testing pattern.
Conclusion
The agile half of the PMP exam is the part where preparation strategy matters most. Candidates who treat it as a vocabulary exercise (memorising ceremonies, roles, and artefacts) tend to underperform. Candidates who treat it as a judgement exercise (recognising context, choosing the right approach, applying servant leadership consistently) tend to clear it comfortably.
The framework knowledge is necessary but not sufficient. Scrum, Kanban, hybrid patterns, and a working understanding of scaling are the raw material. The exam is testing what you do with them: whether you can read a scenario, identify the delivery context, and pick the response a competent agile or hybrid project manager would actually make.
If you are preparing for the PMP and the agile content is where you feel weakest, our PMP Complete Exam Guidance package covers the agile and hybrid scenarios in depth, with structured practice on the question patterns this article describes. If you have already passed the PMP and are looking at the PMI-ACP or the Disciplined Agile path, our PMI Exam Help service supports candidates across the full PMI agile credential family.
The agile content on the PMP exam is no longer a bolt-on. It is half the test, and it is where the exam most rewards judgement over memorisation. Prepare it that way, and the rest of the exam becomes much easier.