The scenario sets the approach and the vocabulary gives it away: backlog, sprint, product owner and velocity mean agile; baseline, work breakdown structure, change control board and earned value mean predictive; both together mean hybrid. Read for those words before reading the options, and never answer from the approach you prefer.
Candidates lose marks here in a very particular way. They read a scenario, recognise a problem they have solved before, and answer from the approach they use at work — which the scenario never mentioned and may have quietly excluded three lines earlier.
The exam covers predictive, agile and hybrid approaches together, and it does not ask which you would choose. It plants the approach in the scenario and expects you to notice. Miss the plant and you will pick an answer that is competent, sensible, and wrong.
This guide covers the vocabulary that gives the approach away, the traps in hybrid scenarios, and the useful fact that a surprising share of correct answers are the same whichever approach you are in.
The tell is almost always a noun, and it is usually in the first two sentences.
Backlog, sprint, iteration, product owner, velocity, increment, retrospective, story points, definition of done — you are in an agile scenario, and answers that reach for a change control board or a baseline variance are wrong regardless of how sensible they sound.
Work breakdown structure, baseline, change control board, earned value, critical path, statement of work, phase gate — you are in a predictive scenario, and answers about re-prioritising the backlog do not apply.
Both sets in the same paragraph — a baselined schedule with a team working in iterations, a governance board reviewing increments — and you are in a hybrid scenario, which is where the exam does most of its interesting work.
Make this mechanical. Underline the approach words first, decide which world you are in, and only then look at the options. Reading the options first is what lets your own habits answer the question.
Underneath the vocabulary sits one difference that generates most of the questions: what each approach believes change is.
In a predictive approach, change is a deviation from an agreed plan. It is not forbidden, but it is controlled — raised, assessed, approved or rejected, and the baseline updated if approved. A scenario where a stakeholder asks for something new mid-phase is asking you about change control.
In an agile approach, change is expected and is absorbed through prioritisation rather than through control. The same stakeholder request becomes a backlog item, ordered by the product owner against everything else. Nobody raises a change request to add a story.
In a hybrid, both are true at once and the exam's question is usually which mechanism applies to this particular change. The rule of thumb that survives most scenarios: if the change affects the agreed envelope — total budget, contractual scope, the delivery date committed to the customer — it goes through governance. If it affects what the team builds next inside that envelope, it goes to the backlog.
Get that one distinction right and hybrid scenarios stop being intimidating.
Scan the scenario for these before doing anything else.
| If you see | You are in | Answers that are wrong here |
|---|---|---|
| Backlog, sprint, iteration, velocity, story points | Agile | Change control board, baseline variance, WBS decomposition |
| Product owner, retrospective, definition of done, increment | Agile | Phase gate approval, formal change request for a feature |
| WBS, baseline, critical path, earned value, CPI/SPI | Predictive | Re-prioritise the backlog, let the team self-select |
| Change control board, statement of work, phase gate | Predictive | Absorb it into the next iteration |
| A baseline and iterations together | Hybrid | Applying one mechanism to everything |
| Governance board reviewing increments | Hybrid | Assuming the sponsor owns the backlog |
| No approach words at all | Approach-agnostic | Assuming your own working style |
This happens more often than candidates expect, and it is not an oversight. A large share of PMP questions are approach-agnostic, because the behaviour being tested is the same in all three.
Talk to the person before deciding about them. Understand the cause before applying a remedy. Do not commit on someone else's behalf. Do not conceal a problem from the people who need to know. Address a conflict directly and early rather than escalating it first. Protect the team's ability to do the work. None of that changes with approach.
So when you cannot find a tell, stop looking for one. The question is testing judgment, and the correct answer will be the one that engages, understands or protects — not the one that deploys a technique.
The failure mode here is a candidate who has drilled agile hard and starts importing ceremonies into questions that never mentioned them. A retrospective is not the answer to a scenario with no iterations in it.
The role trap. In hybrid delivery the sponsor and the product owner both exist, and they are not interchangeable. Whether the project continues is the sponsor's question. What the team builds next is the product owner's. Candidates who have only studied one approach routinely hand one's decision to the other.
The mechanism trap. Applying one change mechanism to everything. A hybrid scenario usually contains both a governed envelope and an unordered backlog inside it, and the question is which one this change touches.
The reporting trap. Hybrid projects frequently report progress in predictive terms to governance while working in iterations underneath — a burndown for the team and an earned value figure for the steering group. A question about what to tell the sponsor is not answered with the team's velocity.
One habit defuses all three: before answering a hybrid question, say to yourself which layer you are being asked about — the governed envelope, or the delivery inside it. Almost every hybrid question sits clearly in one of the two, and almost every wrong answer belongs to the other.
Change what you record when you get a practice question wrong. Note the approach you assumed and the approach the scenario actually specified. Most candidates discover a systematic bias — usually toward whatever they do at work — and a bias you can name is a bias you can correct in a fortnight.
Then practise the first ten seconds deliberately: read, underline the approach words, state the approach out loud, and only then look at the options. It feels slow for a week and then it is free.
And use the visual approach for this specifically, because the tells are a pattern rather than a list. Our visual study guide draws them as decision maps across People, Process and Business Environment, with agile and hybrid decisions set side by side rather than in separate chapters — which is the layout that makes the difference visible instead of remembered.
Finally, remember what the exam is testing. Not which approach is better. Whether you can work correctly inside the one you have been given.
Neither. It covers predictive, agile and hybrid approaches together and expects you to work correctly inside whichever one the scenario describes. Answering from your own preferred approach is one of the most common ways to lose marks.
Read the nouns. Backlog, sprint, product owner and velocity mean agile. Baseline, WBS, change control board and earned value mean predictive. Both together mean hybrid. Underline them before you read the options.
Then the question is approach-agnostic and is testing judgment. The right answer will engage the person, understand the cause, or protect the team — not deploy a technique from an approach the scenario never mentioned.
The product owner, working the backlog. The sponsor decides whether the project continues and owns the business case. Conflating the two is the most common hybrid mistake.
Both mechanisms coexist. If the change affects the agreed envelope — total budget, contractual scope, the committed date — it goes through governance. If it affects what the team builds next inside that envelope, it goes to the backlog.
Rules change. Where a figure or a procedure can move, the issuing agency’s current published instructions win over anything here.
