PMP Agile vs Predictive Questions: How to Tell Which Approach a Question Tests

The PMP exam does not label questions as "agile" or "predictive." There is no tag, no header, no hint in the question number. Every one of the 180 questions presents a scenario, and you have to infer the project approach from contextual cues before you can evaluate the answer choices. Candidates who skip this step — applying waterfall thinking to an agile scenario or vice versa — account for a disproportionate share of wrong answers. This is the single most trainable skill on the exam, and PrepSolution's PMP exam prep tags every practice question by approach type so you can build this pattern recognition systematically.

With the July 2026 PMP exam update, the weighting shifted from a roughly 50/50 agile-predictive split to approximately 60% agile-hybrid and 40% predictive. That means misidentifying the approach on even a handful of questions costs more than it did a year ago. This article gives you the signal-word taxonomy, the decision framework, and the seven mistakes that trip up otherwise well-prepared candidates. For the full exam blueprint and study timeline, see our PMP exam prep guide.

Why does approach identification matter on the PMP exam?

PMI's Examination Content Outline (ECO) is framework-agnostic — it does not prescribe Scrum, PRINCE2, or any single methodology. But the correct answer to a scenario question depends entirely on the project environment described. In a predictive environment, a scope change goes through a Change Control Board (CCB) and a formal change request process. In an agile environment, the same scope change is simply reprioritized in the product backlog by the Product Owner — no change request, no CCB. Selecting "submit a change request" for an agile scenario is wrong, even though it would be textbook-correct in a predictive context. The question is testing whether you can read the environment, not whether you memorized a process.

PMI publishes no percentage of scenario-based questions, but scenario items dominate the exam — and they embed approach cues in the stem. The remaining questions test definitions, formulas, or concepts that are approach-neutral. For the scenario questions, your first task is always to classify the environment.

Signal words: predictive vs agile vs hybrid

The fastest way to identify the approach is to scan for signal words. These are terms that PMI associates with specific project environments. They appear in the question stem, the scenario description, or sometimes in the answer choices themselves.

How do predictive and agile handle changes differently?

This is the highest-yield distinction on the exam. In a predictive environment, changes follow a formal process: the project manager evaluates the impact, submits a change request, and the CCB approves or rejects it. The baseline is updated only after approval. The project manager is the central authority managing scope, schedule, and cost.

In an agile environment, there is no change request process. The Product Owner reprioritizes the backlog based on value. The team pulls work from the backlog each iteration. If a stakeholder wants something new, the Product Owner adds it to the backlog and re-ranks. The Scrum Master facilitates but does not direct. The team self-organizes to deliver the highest-priority items.

If a question describes an agile team and one answer choice mentions "submit a change request to the CCB," that answer is wrong regardless of how reasonable it sounds. Conversely, if the scenario describes a baselined project management plan and an answer says "add it to the backlog," that answer misapplies agile to a predictive context.

Which agile frameworks does PMI emphasize?

PMI is officially framework-agnostic, but the exam leans heavily on Scrum terminology and practices. Kanban appears in questions about flow-based work, WIP limits, and cumulative flow diagrams. Extreme Programming (XP) practices — pair programming, test-driven development, continuous integration — show up occasionally. SAFe and LeSS are not tested directly, though scaled agile concepts may appear in the context of large programs. PMI's Agile Practice Guide remains a primary reference for agile-specific exam content.

The PMBOK Guide Eighth Edition, released November 2025, restructured around 6 principles, 5 Focus Areas, and 7 Performance Domains. It is more approach-agnostic than ever, but the exam still draws from the Agile Practice Guide (bundled with PMBOK 7th Edition) for agile-specific questions. Candidates should be comfortable with both resources.

The 3-second approach identification framework

To identify a PMP question's approach in seconds: scan for signal words, check which roles the scenario names, and look at how changes are handled — formal change requests signal predictive, backlog reprioritization signals agile. Mixed structures are hybrid, and when a scenario stays ambiguous, default to the answer where the project manager empowers the team rather than directing it.

When you read a scenario question, run through these checks in order:

1. Scan for signal words from the table above. One or two keywords usually settle it.
2. Look at the roles mentioned. "Product Owner" and "Scrum Master" mean agile. "Project manager" alone is ambiguous — PM exists in both environments — but combined with "baseline" or "WBS," it signals predictive.
3. Check how changes are handled in the scenario. Formal change requests = predictive. Backlog reprioritization = agile.
4. If the scenario mixes both (e.g., fixed milestones with iterative sprints), treat it as hybrid and apply the principle that fits the specific situation described.
5. When in doubt, default to the approach where the project manager empowers the team rather than directing it. PMI's current exam philosophy favors servant leadership and adaptive approaches.

7 common mistakes candidates make with approach identification

The seven costliest PMP approach-identification mistakes: treating agile as no planning, applying waterfall change control to agile scenarios, directing the team instead of empowering it, allowing mid-sprint scope changes, over-applying the pure Scrum Guide, confusing the PMI ideal with real-world practice, and assuming agile is always the right approach when predictive still makes up 40% of the exam.

These errors come from analyzing PMP candidate performance data and prep community reports. Each one represents a pattern that costs multiple questions on the exam.

How did the July 2026 update change the approach split?

The July 2026 ECO update shifted the exam from a roughly 50/50 predictive-agile balance to approximately 60% agile-hybrid and 40% predictive. This does not mean predictive questions disappeared — it means agile and hybrid scenarios are now the majority. Candidates who spent most of their study time on PERT calculations, critical path method, and EVM formulas will find the exam has moved further toward leadership, stakeholder engagement, and adaptive delivery.

The practical impact: you need to be equally fluent in both approaches, but your default mental model should lean adaptive. When a question is ambiguous, the PMI-preferred answer will generally favor collaboration over control, facilitation over direction, and iterative delivery over comprehensive upfront planning.

How to practice approach identification

Reading about signal words is useful. Practicing with tagged questions is what actually builds the skill. When reviewing practice questions, do not just check whether your answer was right — check whether you correctly identified the approach first. If you got the approach wrong but the answer right, that is luck, not competence.

• Before reading the answer choices, write down whether the scenario is predictive, agile, or hybrid.
• Identify the specific signal words that led to your classification.
• Only then evaluate the answer choices within the correct framework.
• Track your approach-identification accuracy separately from your overall score.
• If your accuracy is below 90%, spend more time on signal-word drills before doing full-length mock exams.

PrepSolution's PMP question bank tags every question by approach type — predictive, agile, or hybrid — so you can filter and drill specific categories. Combined with our approach-identification tracker, you can isolate exactly where your pattern recognition breaks down. To understand how our adaptive learning engine works, see the methodology page.

The bottom line

Approach identification is not a nice-to-have — it is the prerequisite for answering the scenario-based questions that dominate the PMP exam. The exam never tells you which framework applies. You have to read the scenario, spot the signal words, classify the environment, and then apply the correct decision-making model. Candidates who train this skill systematically pass at higher rates than those who simply memorize processes from both approaches and hope the right one surfaces during the exam. See why PrepSolution tags every practice question by approach type to build this critical skill.