Predictive, Agile, or Hybrid? How to Tell Which World a PMP Question Lives In

Here's a question that comes up in PMP study groups constantly:

"I knew the right answer. I picked it. It was wrong. The explanation said the other answer was right because the project was agile. Where did it say that?"

Usually it did say it. In one word, halfway through the second sentence.

The PMP tests predictive, agile, and hybrid project management side by side, often without telling you which one a question is about. The same situation can have a different correct answer depending on which world the question lives in. If you can't tell which world you're in, you're guessing between two defensible answers on a lot of questions.

This is one of the most learnable skills on the exam. Here's how.

Why This Matters More Than It Used To

The PMP has been mixed-approach since 2021. What's changed is how often questions blend approaches rather than labeling them. The 2026 outline weaves agile and hybrid delivery into the main Process and Business Environment content instead of treating it as a separate track. Hybrid scenarios are now everywhere.

You can't sort the exam into "the waterfall questions" and "the agile questions" anymore. You have to read each stem and work out the context yourself.

Step 1: Read the Stem for Clues

Before you look at the answer choices, find the words that tell you which approach the project uses. They're almost always there.

Agile signals:

Sprint, iteration, increment, release
Product backlog, sprint backlog, user stories, story points
Product owner, scrum master, the team, self-organizing team
Daily standup, sprint review, retrospective
Velocity, burndown, burn-up, Kanban board, WIP limits
"Customer feedback after each demo"

Predictive signals:

Baseline (scope, schedule, cost)
Work breakdown structure, WBS dictionary
Change control board, integrated change control, change request
Gantt chart, critical path, schedule variance, earned value
Phase gate, sign-off, formal acceptance
Fixed-price contract, statement of work
"The project management plan was approved"

Hybrid signals:

Both sets appear in the same stem
"The hardware is being built using a predictive approach while the software team uses sprints"
A predictive contract or governance wrapper around agile execution
"The organization is transitioning to agile"
Phase gates with iterations inside them

No signals at all: that's a clue too. See Step 4.

Step 2: Know How Each World Answers the Same Problem

This is the core of it. The same situation, five different ways:

Situation	Predictive answer	Agile answer
Stakeholder wants a new feature	Submit a change request, evaluate impact, take it through change control	Product owner adds it to the backlog and prioritizes it against existing items
Deliverable doesn't meet requirements	Compare to the scope baseline and acceptance criteria, then follow the quality process	Raise it at the sprint review, capture feedback, and adjust the backlog
Team member is underperforming	PM talks with them privately, identifies the cause, offers support or training	PM (as servant leader) talks with them and helps the team address it collaboratively. The team owns its work
Work is falling behind	Analyze schedule variance and critical path, consider crashing or fast-tracking	Look at velocity, have the product owner reprioritize so the highest-value items get done first
Who decides how to do the work	PM plans and assigns, with team input	The team decides. The PM removes obstacles

Notice the pattern:

Predictive controls change through process. The baseline is the reference point, and deviations are managed formally.
Agile absorbs change through prioritization. The backlog is the reference point, and the product owner decides what matters most.

And the role shift that catches the most people:

Predictive PM: plans, directs, controls, reports.
Agile PM (servant leader): facilitates, removes impediments, coaches, protects the team. Doesn't assign tasks.

If you see an agile stem and an answer starting with "The project manager assigns...", that answer is almost always wrong.

Step 3: Handle Hybrid by Finding Where the Problem Lives

Hybrid questions are the hardest because both kinds of answer can look right. The trick: figure out which part of the project the problem is in, and use that part's rules.

Example: a company is building a medical device. The physical hardware follows a predictive approach with regulatory phase gates. The embedded software is built in two-week sprints.

A change to the device enclosure dimensions? That's in the predictive part. It goes through change control, and probably regulatory review too.
The product owner wants to reorder software features for the next release? That's the agile part. It's a backlog decision.
A software change affects a regulatory requirement? That's where the two parts meet. It crosses the boundary, so the governance and compliance rules of the predictive wrapper apply, even though the work happens in sprints.

The general rule for hybrid: agile inside, governance outside. Day-to-day work and prioritization follow agile rules. Contracts, compliance, budget authority, and phase gates follow predictive rules.

Step 4: When There Are No Clues

Some questions really don't say. When you can't find a single signal word:

Look for the answer that's good in both worlds. Many questions are written so the right answer works under either approach. These answers tend to:

Analyze or assess before acting
Communicate directly with the people involved
Collaborate rather than dictate
Follow the agreed process, whatever it is

Eliminate the answers that only make sense in one world. "Update the WBS" or "Add it to the sprint backlog" both commit to an approach the question never stated. A neutral answer often beats either one.

Don't invent context. If the question doesn't mention sprints, don't assume the project is agile because your company is. And don't assume it's predictive because your last project was.

The Five Traps

1. The modern-sounding wrong answer. An answer that sounds collaborative and agile ("Let the self-organizing team decide") dropped into a clearly predictive stem with a fixed-price contract and an approved baseline. It sounds progressive. It ignores the context.

2. The controlling PM in an agile stem. "The PM should reassign the task," "The PM should update the schedule baseline," "The PM should approve the change." In agile, the PM isn't the approval authority for scope or the assigner of work.

3. Change control for backlog changes. In an agile context, a new requirement isn't a change request. It's a backlog item. If the stem says "product owner" and an answer says "submit to the change control board," be suspicious.

4. Skipping the product owner. In agile, decisions about what to build and in what order belong to the product owner. Answers where the PM or the team reprioritizes the backlog on their own are usually wrong.

5. Forgetting governance in hybrid. The agile execution doesn't remove the compliance, contract, or funding rules around it. If a change crosses that boundary, the formal process applies.

A Drill That Actually Builds the Skill

For your next practice set, add one step before answering:

Read the stem.
Before looking at the answers, write down P, A, H, or ? for predictive, agile, hybrid, or unclear.
Circle (or mentally note) the word that told you.
Then answer.

When you review, check two things: did you get the question right, and did you identify the world correctly? You'll probably find that a chunk of your misses came from misreading the context, not from not knowing the material. Those are the easiest points to recover.

Do this for 50–100 questions and it becomes automatic. You'll start noticing "backlog" or "baseline" the moment you read it.

The Bottom Line

The PMP isn't testing whether agile is better than predictive. It's testing whether you can tell which one a situation calls for and act accordingly. Find the signal words, know how each approach handles the same problem, use "agile inside, governance outside" for hybrid, and when there are no clues, pick the answer that works in either world.

If your practice scores are stuck and you keep losing to the "other defensible answer," this is often the reason.

Want to practice reading the context? Try free PMP questions with predictive, agile, and hybrid scenarios across the 2026 outline. No signup required.