How much of the PMP® exam is agile?

On the current exam (through July 8, 2026), approximately 50% of questions involve agile or hybrid approaches. On the new 2026 exam (starting July 9, 2026), the agile and hybrid share rises to roughly 60%. Pure predictive (waterfall) questions now make up less than half the exam in either version.

Do I need to know both agile and predictive to pass the PMP® exam?

Yes. You cannot pass by ignoring either methodology. Candidates who come from a waterfall background frequently fail because they underinvest in agile. Candidates from agile backgrounds fail because they skip predictive concepts like earned value management, critical path, and formal change control.

How do I tell if an exam question is about agile, predictive, or hybrid?

Look for signal words. Agile scenarios mention sprints, iterations, product backlogs, Scrum events, user stories, or self-organizing teams. Predictive scenarios mention baselines, work breakdown structures, earned value, critical path, or formal change control boards. Hybrid scenarios explicitly combine both, like a Scrum team operating within a fixed-budget, fixed-deadline program.

Why is the agile mindset shift harder than learning the agile content?

Most exam failures on agile questions are not knowledge failures. They are mindset failures. Predictive-trained PMs instinctively reach for controls, baselines, and escalation paths. Agile questions reward servant leadership, removing blockers, empowering the team, and protecting iteration goals. The correct answer often feels 'too hands-off' to a traditional PM.

Can I skip the PMBOK® if I'm already experienced with agile?

No. The PMP® exam tests PMI®'s specific interpretation of agile, which draws from Scrum, XP, Lean, and Kanban but frames them through a PMI® lens. Experienced Scrum Masters who skip PMI®-aligned study often fail agile questions because their real-world team's practices diverge from what PMI® considers the 'textbook' approach.

What are the most common agile frameworks tested on the PMP® exam?

Scrum is the most tested by a wide margin: roles (Product Owner, Scrum Master, Developers), events (Sprint Planning, Daily Scrum, Review, Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment). Kanban, XP (Extreme Programming), and Lean concepts also appear. You should recognize SAFe at a high level, but deep SAFe knowledge is not required.

Agile vs Predictive vs Hybrid on the PMP® Exam

TL;DR: The PMP® exam is roughly 50% agile/hybrid and 50% predictive on the current exam, shifting to about 60/40 agile-hybrid on the July 2026 exam. You cannot ignore either approach. Predictive-trained PMs lose points on agile scenarios by reaching for controls and escalations when the right answer is to empower the team. Agile-trained PMs lose points on predictive scenarios by skipping formal processes they consider overhead. Passing requires genuinely understanding both mindsets, not just memorizing terminology.

Most first-time PMP® candidates underestimate how dramatically the exam has shifted away from pure predictive project management. If you came up through waterfall or PRINCE2, roughly half the exam will feel unfamiliar. If you came up through Scrum, roughly half will feel like overhead theater. Here is what the split actually means and how to prepare for both.

What Is the Actual Split Between Agile and Predictive on the PMP® Exam?

PMI® has never published exact question-by-question percentages, but based on the Examination Content Outline (ECO), PMI® candidate reports, and analysis of released sample questions, the approximate methodology distribution is:

Exam Version	Predictive	Agile / Hybrid
Current exam (through July 8, 2026)	~50%	~50%
New exam (starting July 9, 2026)	~40%	~60%

This is a massive shift from the pre-2021 exam, which was 85%+ predictive. Candidates who studied from older materials or who rely on decades-old real-world predictive experience frequently get blindsided by how heavily agile is now weighted. For the full list of what changes on the July 9, 2026 exam, see the PMP® exam changes for 2026 guide.

The change is not random. PMI® restructured the exam to reflect how real-world projects actually run. Most modern organizations do not run pure waterfall or pure Scrum. They run hybrid. A Scrum team inside a regulated pharmaceutical rollout. A predictive infrastructure program with agile software work streams. A stage-gate product development with sprint-based engineering. The exam reflects that reality.

For a deeper look at the full structure, read our PMP® exam content outline guide.

Why Is the Agile Mindset Shift the Hardest Part?

Most candidates who fail agile questions are not failing on content. They know what a Sprint Retrospective is. They can define a Product Backlog. They have memorized Scrum roles. They still lose points because their instincts are wrong.

Here is a common example:

A self-organizing Scrum team is behind on sprint commitments. The Product Owner is pushing for additional scope. Two developers are visibly frustrated. What should the project manager do first?

A predictive-trained PM reads this and wants to:

Review the baseline and assess variance
Escalate to the sponsor
Issue a corrective action plan
Renegotiate scope with the Product Owner

None of those are the PMI® best answer. The PMI® best answer is to facilitate a conversation between the Product Owner and the team to surface the impediments, protect the sprint goal, and empower the team to propose solutions.

The predictive instinct is to control. The agile instinct is to enable. If your instincts are wired for control, you will systematically pick the wrong answer on agile scenarios even when you "know the material."

This is why rote memorization fails on the PMP®. You need to internalize the mindset, not just the vocabulary. For tactical guidance on navigating situational questions, see our guide on how to answer PMP® scenario questions.

What Is a Predictive (Waterfall) Project?

A predictive project has:

Clear, stable requirements defined upfront
A fixed scope documented in a project scope statement and WBS
A sequential flow through initiation, planning, execution, monitoring and controlling, and closing
Formal change control through a Change Control Board (CCB)
Detailed baselines for scope, schedule, and cost
Variance analysis to track against baselines (earned value management)

Predictive works well when:

Requirements are well understood (construction, regulated manufacturing, infrastructure)
Changes are expensive (physical products, regulatory submissions)
Stakeholders need predictability for budget and timeline

On the exam, a predictive scenario often mentions: baselines, WBS, critical path, earned value, CCB, formal change requests, variance analysis, CPI/SPI, gate reviews, stage gates.

What Is an Agile Project?

An agile project has:

Evolving requirements refined throughout the project
A prioritized backlog rather than fixed scope
Iterative delivery through sprints, iterations, or continuous flow
Self-organizing teams that decide how to do the work
Servant leadership - the PM or Scrum Master removes impediments, not directs the work
Frequent stakeholder feedback through reviews and demos

Agile works well when:

Requirements will change as the team learns (software, product development, research)
Rapid delivery of value matters more than long-term predictability
Stakeholders can commit to regular feedback loops

On the exam, an agile scenario often mentions: sprints, iterations, product backlog, user stories, Product Owner, Scrum Master, Daily Scrum, Sprint Review, Sprint Retrospective, burn-down charts, velocity, Definition of Done.

Agile Roles You Must Know

Role	Responsibility
Product Owner	Owns the backlog. Prioritizes work. Accepts or rejects completed increments. Represents the customer.
Scrum Master	Servant leader. Removes impediments. Facilitates events. Coaches the team on agile practices. Does NOT assign work.
Developers / Team	Self-organizing. Decide how to do the work. Commit to sprint goals. Deliver the increment.

A critical exam trap: the Scrum Master does not manage the team the way a predictive PM manages a team. The Scrum Master facilitates and removes blockers. Answers that have the Scrum Master assigning tasks, setting priorities, or making scope decisions are almost always wrong.

What Is a Hybrid Project?

Hybrid projects blend predictive and agile elements. The most common patterns:

Predictive shell, agile core: Overall program is gated and budgeted predictively, but individual work streams (especially software) run agile
Agile development, predictive deployment: Sprints deliver increments, but rollout follows a predictive release schedule
Incremental predictive: Large program broken into sequential predictive phases, each with fixed scope

Hybrid scenarios are the hardest on the exam because the "right answer" depends on which layer of the project the question is asking about. A question about a hybrid program's budget review is likely predictive. A question about the software team's daily practices is likely agile.

On the exam, hybrid scenarios often mention: a program or portfolio context, multiple vendors or teams using different approaches, regulatory constraints plus iterative work, or a sponsor expecting waterfall reporting from an agile team.

How Do You Identify the Methodology in an Exam Question?

The exam rarely tells you explicitly "this is an agile question" or "this is a predictive question." You have to infer it from signal words and context.

Predictive Signals

Scope baseline, schedule baseline, cost baseline
Work breakdown structure (WBS)
Critical path, critical chain, PERT, CPM
Earned value, CPI, SPI, EAC, ETC
Change control board, formal change request
Gantt chart, network diagram
"The project charter specifies..."
"The approved baseline requires..."

Agile Signals

Sprint, iteration, release
Product backlog, sprint backlog, user stories
Product Owner, Scrum Master, self-organizing team
Daily Scrum, Sprint Planning, Review, Retrospective
Burn-down, burn-up, velocity, story points
Definition of Done, Definition of Ready
Kanban, WIP limits, pull-based flow

Hybrid Signals

Program with multiple teams on different methodologies
Regulated environment with iterative delivery
Fixed-budget sprint-based work
"The sprint team operates within a stage-gate program..."

The first sentence of a scenario usually contains the methodology signal. Train yourself to identify it before reading the rest of the question. Once you know the methodology, you know which mindset to apply.

What Agile Concepts Does the PMP® Exam Actually Test?

PMI® aligns with the Agile Practice Guide. The most tested agile concepts:

Scrum fundamentals (most heavily tested):

Three roles (Product Owner, Scrum Master, Developers)
Five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective)
Three artifacts (Product Backlog, Sprint Backlog, Increment)
Timeboxes for each event

Servant leadership:

Remove impediments
Protect the team from outside interruption
Coach, don't command
Facilitate, don't decide

Backlog management:

Product Owner prioritizes
Refinement is ongoing
Items get estimated by the team, not by the PM
Done means meeting the Definition of Done

Metrics and tracking:

Velocity (not productivity)
Burn-down and burn-up charts
Cumulative flow diagrams (Kanban)
Lead time and cycle time (Kanban)

Team dynamics:

Self-organizing teams
Cross-functional teams
Psychological safety
Retrospective-driven improvement

Lean / XP / Kanban:

WIP limits
Pair programming, TDD (at a conceptual level)
Eliminating waste
Continuous improvement (kaizen)

What Predictive Concepts Does the PMP® Exam Actually Test?

Predictive concepts that remain heavily tested:

Integration management:

Project charter
Change control process
Lessons learned register
Integrated change control

Scope management:

Scope baseline (scope statement + WBS + WBS dictionary)
Requirements traceability matrix
Scope creep vs. gold plating
Validated scope

Schedule management:

Critical path method (CPM)
Forward and backward pass
Float / slack calculation
Schedule compression (crashing, fast-tracking)
Network diagrams

Cost management:

Cost baseline (S-curve)
Earned value management (EV, PV, AC, CPI, SPI, EAC, ETC, VAC)
Reserve analysis (contingency vs. management reserves)

Risk management:

Risk register
Qualitative vs. quantitative analysis
Risk response strategies (avoid, transfer, mitigate, accept; escalate, enhance, exploit, share, accept for opportunities)
Risk owner assignment

Quality management:

Cost of quality (prevention, appraisal, internal failure, external failure)
Control charts, Pareto, fishbone
Continuous improvement (PDCA, Six Sigma at a high level)

Stakeholder and communication:

Stakeholder register and engagement matrix
Communication channels formula: n(n-1)/2
RACI chart

If any of those concepts feel unfamiliar, that is a specific gap to target. For a deeper breakdown of the domain balance, see PMP® domain weights for 2026.

How Should You Study Each Approach?

If You Come From a Predictive Background

Invest 60% of your study time on agile and hybrid. Your instinct will be to spend more time on what is comfortable (predictive). Resist it. You already understand baselines, WBS, and earned value from your job. Your exam risk is on agile scenarios where you will default to control-oriented answers.

Specific focus areas:

Scrum events and roles (memorize cold)
What a Scrum Master does NOT do (does not assign work, does not manage the team, does not set priorities)
How to respond to team-level problems in agile (facilitate, don't direct)
Servant leadership scenarios
Retrospective-driven improvement

If You Come From an Agile Background

Invest 60% of your study time on predictive and hybrid. Your instinct will be to dismiss predictive questions as "not how real projects work." The exam does not care. PMI® tests the predictive framework in detail, and agile-only PMs frequently fail by underinvesting in it.

Specific focus areas:

Earned value formulas and interpretation
Critical path calculation
Formal change control process
Stakeholder engagement matrices
Risk management processes and response strategies
Procurement and contracting basics

If You Come From a Hybrid Background (or No PM Background)

You are actually in the best position for this exam. You do not have strong instincts pulling you toward one methodology or the other. Study both approaches with equal weight and focus heavily on identifying which methodology applies in a given scenario. For a full study workflow, see how to study for the PMP® exam.

What Are the Most Common Mistakes Candidates Make with the Agile/Predictive Split?

1. Skipping the Agile Practice Guide

Many candidates study only the PMBOK® Guide and skip the Agile Practice Guide. The exam tests content from both. The Agile Practice Guide is where PMI® defines servant leadership, team empowerment, and the adaptive mindset that drives agile exam answers.

2. Assuming Real-World Scrum Experience Is Enough

PMI®'s interpretation of agile is "textbook Scrum," not whatever flavor your team actually practices. If your real team has the Scrum Master assigning tasks or skipping retrospectives, your instincts are misaligned with the exam.

3. Memorizing Agile Vocabulary Without the Mindset

You can memorize that the Scrum Master is a servant leader and still pick the wrong answer because you do not internalize what servant leadership actually looks like in practice. The agile mindset is about empowerment and facilitation, not command and control.

4. Treating Hybrid as a Separate Third Category

Hybrid is not a distinct methodology with its own rules. It is predictive and agile layered together. On hybrid questions, identify which layer the question is asking about, then apply that layer's mindset.

5. Ignoring the Agile / Predictive Signal in the First Sentence

Candidates often read the entire scenario, form an instinct based on general PM knowledge, and then miss the signal that would have pointed them to the correct mindset. Train yourself to identify the methodology before evaluating answer choices.

How Do You Know When You Are Ready on Both Approaches?

You are ready when:

You can identify the methodology within the first two sentences of a scenario
You can correctly answer Scrum event/role questions without hesitation
You can calculate earned value formulas without a cheat sheet
You do not feel a "wrong" pull toward control-oriented answers on agile questions
You do not dismiss predictive scenarios as "unrealistic"
Your practice scores on agile and predictive questions are within 10 points of each other (if one is much stronger than the other, study the weaker one)

Mixed-methodology fluency is what separates Target-level performers from Above-Target performers on the real exam.

Start Preparing with PrepPilot™

PrepPilot™ is built to train both mindsets. The adaptive quiz engine tracks your accuracy on predictive versus agile versus hybrid questions separately, so you can see exactly where the gap is. If you are scoring 78% on predictive but 54% on agile, PrepPilot™ shifts your next study session toward agile scenarios without you having to guess what to focus on.

Every practice question is tagged by methodology. When you get one wrong, the AI instructor explains not just the correct answer but the mindset behind it, why a Scrum Master would facilitate rather than direct, why a predictive PM would baseline before executing, or why a hybrid scenario requires identifying the layer first.

Check your readiness score to see where you stand across predictive and agile scenarios. Methodology fluency is the highest-leverage area to study, and PrepPilot™ backs your prep with a pass guarantee so you can drill both mindsets without worrying about the cost of a retake. Start studying free at PrepPilot™.