Agile vs Predictive vs Hybrid: What the 2026 PMP Exam Actually Tests

The Three Delivery Approaches

Before getting into how the exam tests this, let's make sure the definitions are clear. PMI recognizes three delivery approaches, and they show up constantly on the 2026 exam.

Predictive (Waterfall) — Plan everything upfront, execute the plan, deliver at the end. Requirements are defined early and changes go through formal change control. Think construction, regulatory compliance projects, or anything where you need to know the full scope before you start building.

Agile — Deliver in short iterations, get feedback after each one, adapt the plan as you learn. Requirements emerge over time through collaboration with the customer. Think software development, product design, or anything where the end user can't tell you exactly what they want until they see it.

Hybrid — Use predictive for parts of the project where requirements are stable and agile for parts where they're evolving. This is how most real projects actually work, and it's the approach PMI leans toward most heavily on the 2026 exam.

None of these approaches is inherently better. The exam tests whether you can match the right approach to the right situation. That's the skill PMI cares about.

How PMI Actually Tests This

Here's what catches most candidates off guard: the 2026 PMP exam rarely asks you to define agile or predictive. Instead, it gives you a project scenario and asks what you should do next. The delivery approach is embedded in the context, and your job is to recognize which approach applies and act accordingly.

There are three ways the exam tests delivery approach knowledge:

1. Choosing an approach. The scenario describes a project's characteristics — stakeholder involvement, requirement stability, risk tolerance, regulatory constraints — and asks which approach fits. These are usually straightforward if you know the decision criteria.

2. Acting within an approach. The scenario tells you the team is using Scrum (or waterfall, or a hybrid). Something goes wrong. What do you do? These test whether you understand how each approach actually works in practice, not just in theory.

3. Switching approaches. The project started predictive but conditions changed. Or the team is using agile but a regulatory requirement forces a predictive element. These hybrid scenarios are the hardest questions on the exam and the ones most candidates get wrong.

Predictive: When the Exam Expects Waterfall

About 40% of the 2026 exam still tests predictive project management. Don't let the agile hype fool you — waterfall isn't dead on this exam.

The exam expects you to choose a predictive approach when the scenario includes these signals:

• Fixed requirements — The scope is defined, documented, and unlikely to change
• Regulatory or compliance constraints — Government projects, healthcare, construction where you need documentation at every stage
• Sequential dependencies — You can't start phase B until phase A is completely done (think building a bridge)
• Contract-driven work — Fixed-price contracts where the deliverable is specified in advance
• Low stakeholder availability — The customer can't or won't provide regular feedback

When you see a predictive scenario on the exam, PMI expects you to think in terms of formal change control, baselines, earned value, and structured phase gates. If the question is about a waterfall project and one of the answer options is "add it to the backlog," that's usually wrong.

Key predictive concepts for the 2026 exam: Work Breakdown Structure (WBS), critical path method, earned value management (EVM), integrated change control, and configuration management. These aren't going away — they're just sharing the spotlight with agile.

Agile: More Than Just Scrum

Most PMP candidates study Scrum and call it a day. The 2026 exam tests a much broader understanding of agile.

Yes, you need to know Scrum: sprints, daily standups, sprint reviews, sprint retrospectives, the product owner role, the scrum master role, and the development team. That's table stakes.

But the exam also tests:

• Kanban — WIP limits, flow-based delivery, cumulative flow diagrams, pull systems. The exam loves Kanban for maintenance and operations scenarios.
• Extreme Programming (XP) — Pair programming, test-driven development, continuous integration. These show up when the scenario involves software quality practices.
• SAFe concepts — PI Planning, Agile Release Trains, program-level ceremonies. The exam tests scaled agile when the scenario involves multiple teams.
• Lean principles — Eliminate waste, optimize the whole, deliver fast. Lean thinking underlies many correct answers on the exam.

The exam expects you to choose agile when the scenario shows:

• Evolving requirements — The customer knows the general direction but not the specifics
• High stakeholder engagement — The customer is available and wants to see progress frequently
• Uncertain or complex work — The team hasn't done this before and needs to learn as they go
• Speed to market — Delivering something usable quickly is more important than delivering everything at once
• Empowered, cross-functional teams — The team has the skills and authority to make decisions

The PMI mindset on agile questions is always: collaborate, adapt, deliver value early and often, and trust the team. If an answer option involves top-down control, rigid planning, or waiting until the end to get feedback, it's probably wrong for an agile scenario.

Hybrid: Where Most Candidates Struggle

Hybrid is where the 2026 exam gets genuinely hard. This is also where most candidates lose points, because there's no clean playbook for hybrid the way there is for pure predictive or pure agile.

A hybrid approach means different parts of the project use different delivery methods. Some common patterns the exam tests:

• Predictive planning + agile execution — The project has a fixed scope and budget (predictive) but the development team delivers in sprints (agile). This is extremely common in real projects and on the exam.
• Agile core + predictive governance — The team works in iterations but must produce formal documentation for regulatory compliance at specific milestones.
• Phase-based hybrid — Requirements gathering is predictive (interviews, documentation), design and build are agile (sprints), and deployment is predictive (formal release process).
• Team-based hybrid — The software team uses Scrum, the infrastructure team uses waterfall, and they integrate at defined points.

The exam tests hybrid scenarios by putting you in situations where pure agile or pure predictive would fail. The correct answer is almost always the one that tailors the approach to the situation rather than rigidly following one methodology.

PMBOK 8th Edition's Tailoring principle is the key here. PMI wants you to think: "What does this specific project need?" not "What does Scrum say?" or "What does the PMBOK say?" The answer that adapts the methodology to fit the project is usually the right one.

The Decision Framework PMI Wants You to Use

When you see a delivery approach question on the exam, run through this mental checklist:

Factor	Predictive	Agile	Hybrid
Requirements	Fixed, documented	Evolving, emergent	Mixed — some fixed, some evolving
Customer involvement	Low (defined upfront)	High (continuous feedback)	Varies by phase
Change tolerance	Low (formal change control)	High (expected & welcomed)	Moderate (controlled flexibility)
Delivery cadence	Single delivery at end	Frequent increments	Incremental with milestones
Risk & uncertainty	Low, well-understood	High, needs exploration	Mixed across work streams
Compliance needs	Heavy documentation	Light, working product	Documentation at gates, agile between

When a scenario has signals from multiple columns, the answer is almost always hybrid. PMI's default assumption on the 2026 exam is that most projects are hybrid until proven otherwise.

5 Exam Traps and How to Avoid Them

Trap 1: Assuming every scenario is agile. The exam is 60% agile/hybrid, but that doesn't mean every correct answer is the agile one. Construction projects, compliance-heavy work, and fixed-price contracts still call for predictive approaches. Read the scenario carefully before defaulting to agile.

Trap 2: Treating hybrid as "agile with documentation." Hybrid isn't just agile plus paperwork. It's a deliberate decision about which parts of the project benefit from predictive structure and which benefit from agile flexibility. The exam tests whether you understand the reasoning, not just the label.

Trap 3: Forgetting about servant leadership in predictive scenarios. Even in waterfall projects, PMI expects servant leadership. The PM who commands and controls is wrong on the 2026 exam regardless of the delivery approach. Facilitate, remove impediments, empower the team — even in predictive.

Trap 4: Choosing "escalate to the sponsor" too quickly. In agile and hybrid scenarios, the exam wants you to try solving problems at the team level first. Escalation is for issues that genuinely exceed the team's authority, not for routine conflicts or technical disagreements.

Trap 5: Ignoring the Development Approach & Life Cycle performance domain. This is one of PMBOK 8th Edition's 8 performance domains and it's specifically about choosing and tailoring your delivery approach. Many candidates study the other 7 domains and barely touch this one. On the 2026 exam, it's central to almost every scenario-based question.

How to Practice This Skill

Knowing the theory is only half the battle. The exam tests your ability to apply it under pressure with ambiguous scenarios. Here's how to build that skill:

Practice with scenario-based questions, not definitions. If your practice tool is asking "What are the four Scrum ceremonies?" you're studying for the wrong exam. You need questions that describe a project situation and ask what the PM should do next.

After every practice question, ask yourself: "What delivery approach is this scenario using, and how did that affect the correct answer?" This builds the pattern recognition you need for exam day. After a few hundred questions, you'll start spotting the delivery approach signals instantly.

Pay extra attention to questions you get wrong. When you miss a hybrid question, don't just read the explanation — figure out which signal you missed in the scenario that should have pointed you toward hybrid. Was it the mixed requirements? The regulatory constraint on an otherwise agile team? The phased delivery with iterative development?

Study real project examples. Think about projects at your own organization. Which ones were predictive? Agile? Hybrid? Why? The exam rewards practical judgment, not textbook answers.