September 6, 2026 · 9 min read
TL;DR: The exam almost never asks you to define predictive, iterative, incremental, agile or hybrid. It gives you a scenario and asks which one it is describing, or what to do given the one you are in. Across the 155 delivery-planning questions in this bank, naming a method is usually the wrong answer: predictive wording is offered 28 times and keyed 10 times, agile wording is offered 26 times and keyed 14. The discriminator that actually earns marks is iterative versus incremental.
Every candidate learns the five approaches from the same diagram, the one with a horizontal bar for predictive and a row of little boxes for agile. Then a question describes a team repeatedly reworking one feature while a sponsor waits for something usable each month, and the diagram is no help, because the scenario contains both patterns at once. That is the question, not an accident of the wording.
Five terms, and they are not five points on one line. Two of them describe how work is done and two describe what reaches the customer.
| Approach | What defines it | The scenario cue |
|---|---|---|
| Predictive | Scope, schedule and cost fixed up front, then delivered against | Stable requirements, a committed date, a defined deliverable |
| Iterative | The same piece of the product is reworked, pass after pass, until it is right | "Refining it each cycle", prototypes, a design nobody has settled |
| Incremental | A usable slice is delivered, then another, on a cadence | "Working functionality every month", partial release, early use |
| Agile | Iterative and incremental together, with feedback steering what comes next | Short cycles, a backlog reprioritised on what was learned |
| Hybrid | A deliberate blend, tailored to the project | Some requirements settled, others still open |
Iterative and incremental are the pair that decides questions. Iterative is about repetition over one thing. Incremental is about handing something usable over. They travel together in agile, which is why candidates fuse them, and then a question separates them and the fused version has no answer.
Common trap: a scenario says the team keeps analysing, designing, building and testing the same reporting feature, refining it each pass, while the sponsor expects a working, usable piece delivered every month. Candidates read "repeatedly ... refining each pass" and answer iterative. Wrong. The team's working style is iterative, but the question asks which life cycle matches what the sponsor needs, and a usable delivery on a monthly cadence is the definition of incremental. This bank keys that question on incremental and offers iterative as the distractor immediately above it, worded to sound like the safer reading.
A hybrid life cycle combines predictive, iterative, incremental and agile elements, tailored to the deliverable, the team and the environment. That definition matters less than the trigger.
Hybrid is keyed when the scope splits. A project manager joins an organisation that delivers almost everything predictively and finds that a number of requirements on the new project are still unclear. Not all of them, a number of them. The keyed answer decomposes those unclear requirements and prioritises them into iterative work packages, so the well-understood work proceeds normally while the ambiguity resolves one increment at a time.
Watch what the distractors offer instead: wait until the unclear requirements firm up, set them aside and plan around what is known, or escalate them to management and wait for authorisation. All three treat uncertainty as something to be removed before planning can start. Hybrid exists because it usually cannot be.
The other hybrid cue is organisational rather than technical, and it is a trap in the opposite direction. When a scenario mentions that executives are uncomfortable with agile, the discomfort is context, not the reason. Hybrid is chosen because the work is mixed, not because it splits the difference politically.
Because most of these questions are situational. The stem describes a team already working in some approach and asks what to do next, and the options that name a method are offering you a migration you were never asked to perform.
The numbers in this bank are blunt about it. In the 130 multiple-choice questions in the delivery-planning slice, predictive or waterfall wording appears in the options of 28 questions and is the keyed answer in 10. Agile or adaptive wording appears in 26 and is keyed in 14. So more often than not, a word naming a method belongs to a wrong answer rather than the right one.
Three specific shapes recur:
Tailoring is the concept underneath all of this, and PMBOK 8 gives it real weight: the delivery approach is selected to fit the deliverable, the team and the environment, rather than inherited from whatever the last project did. A question that describes an approach being applied because it is what the organisation always does is describing the problem.
What is the difference between iterative and incremental? Iterative describes how the work is done: the team repeats analyse, design, build and test over the same piece of the product, refining it each pass until it is right. Incremental describes what gets delivered: a usable slice handed over on a cadence, then another. A team can iterate for months and deliver nothing, and a team can deliver increments without iterating on any of them. When a question describes both, the delivery cadence names the life cycle.
When is a hybrid approach the right answer? When part of the scope is well understood and part is not. Hybrid plans the known work in the usual way and breaks the uncertain work down to be delivered iteratively, so each increment clarifies the next. Every requirement unclear points at an adaptive approach; all of them settled points at predictive.
How do I know if a scenario wants predictive? Stable requirements, a fixed and known scope, a regulatory or contractual commitment to a defined deliverable, or a sponsor who needs a date and a total before work starts. Predictive is not the wrong answer by default; it is keyed in 10 of the 28 questions here that offer it.
Is agile always the safer guess on the PMP exam? No. Agile or adaptive wording is offered in 26 questions in this slice and keyed in 14. Naming a method is wrong more often than right, because the question is usually asking what the situation needs, not which camp you belong to.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 ECO, and every wrong answer carries the reason it is wrong, explained rather than just marked. The delivery-planning questions are the largest slice in the Process domain, which is where that matters most. Start the free 20-question sample with no card and no signup.
Related: The project management plan and what a baseline actually is · Scope, requirements and the baseline · Process domain study guide
Sources: PMI, PMBOK Guide and standards · PMI, PMP Exam Content Outline
What is the difference between iterative and incremental?
Iterative describes how the work is done: the team repeats analyse, design, build and test over the same piece of the product, refining it each pass until it is right. Incremental describes what gets delivered: a usable slice of the product handed over on a cadence, then another, then another. A team can iterate for months and deliver nothing, and a team can deliver increments without iterating on any of them. When a question describes both, the delivery cadence is what names the life cycle.
When is a hybrid approach the right answer?
When part of the scope is well understood and part is not. Hybrid is not a compromise between two camps or a way to keep nervous executives comfortable. It plans the known work in the usual way and breaks the uncertain work down to be delivered iteratively so each increment clarifies the next. A scenario where every requirement is unclear points at an adaptive approach, and one where all of them are settled points at predictive.
How do I know if a scenario wants predictive?
Look for stable requirements, a fixed and known scope, a regulatory or contractual commitment to a defined deliverable, or a sponsor who needs a date and a total before work starts. Predictive is not the wrong answer by default. Across this bank it is keyed in 10 of the 28 questions where it is offered, so more than a third of the time the plan-it-first answer is the correct one.
Is agile always the safer guess on the PMP exam?
No, and the bank's own numbers say so. Agile or adaptive wording appears in the options of 26 questions in the delivery-planning slice and is keyed in 14 of them. Naming a method, agile or predictive, is the wrong answer more often than it is the right one, because most of these questions are asking what the situation needs rather than which camp you belong to.