Predictive, agile and hybrid: how to think through mixed PMP questions

You can know every term in the outline and still lose marks, because the best answer in a predictive setting is often the wrong one in an agile setting.

The same problem, a different right answer

The PMP does not ask what the textbook says. It asks what a project leader should do in a situation. The same situation can have different best answers depending on how the work is organised.

If a stakeholder asks for a change in a plan-driven project, you route it through change control. If the same request appears in a team working from a backlog, the product owner can reprioritise, and the leader's job is to help the team absorb it. Both answers are correct, in their own setting.

About 40 per cent of the exam is predictive and about 60 per cent reflects agile or hybrid work. So you meet agile and hybrid situations on most questions, even where the word "agile" never appears.

Three cues that give the approach away

Predictive cues. A baseline, a work breakdown structure, a change control board, a signed scope statement, a formal sign-off, earned value, a fixed contract price with fixed scope.

Agile cues. A backlog, a product owner, sprints or iterations, retrospectives, a team that organises its own work, working software or increments reviewed with the customer, requirements that change as learning arrives.

Hybrid cues. A mix inside one project. Fixed-price procurement with iterative delivery, a regulated phase done in sequence followed by incremental releases, or a plan-driven programme with agile teams inside it.

Read the first two sentences of every scenario hunting for these cues. They tell you which rulebook applies.

A routine for mixed questions

Use four short steps.

1. Name the approach. Predictive, agile or hybrid, from the cues.
2. Name the task. Which of the 26 tasks is being tested? Conflict, scope, risk, change?
3. Ask what comes first. Most questions ask for the next step. The best next step usually gathers information or follows the agreed process before it acts.
4. Remove the two weakest answers. Then choose between the remaining two by asking which one fits the approach.

Scenario 1: a change request in two settings

Setting A. A construction project has an approved baseline. The client asks for a different lift specification. What should the project manager do first?

In a predictive setting, the answer is to assess the impact on scope, schedule, cost and risk and take the change through the change control process. Accepting it immediately skips control. Refusing it outright skips analysis.

Setting B. A product team works from a backlog and a customer asks for a new feature during a sprint review. What should the project leader do?

In an agile setting, the new item goes to the product owner, who decides its priority in the backlog against the value of other items. The leader helps the team understand the change and plan the next iteration. A formal change control board is not the first move.

The request was the same. The approach changed the answer.

Scenario 2: the team that waits to be told

A newly formed agile team keeps waiting for the project manager to assign tasks each morning. What should the project manager do?

The cue is "agile team". In that setting the leader coaches the team to select work from the backlog and agree how it will organise itself, because the team owns how it delivers. Assigning tasks each morning keeps the team dependent. Asking the product owner to assign tasks mixes up roles, because the product owner manages the backlog, not the people.

Compare that with a predictive team of unfamiliar contractors. There, clear task assignment may be exactly what a new team needs. The word that decides is not "team". It is "agile".

Scenario 3: a hybrid contract

A fixed-price supplier is contracted to deliver a system in three increments. After the first increment, the client wants to change some of the remaining requirements. What is the best response?

This is hybrid: a fixed contract with iterative delivery. The best move is usually to review the contract's change terms, evaluate the impact with both parties and agree changes through the contract's change process, while keeping the iterative review rhythm that gives the client its feedback. Ignoring the contract would create a dispute. Ignoring the iterative rhythm would defeat the reason for choosing increments.

Hybrid questions reward the answer that respects both rulebooks.

Where mixed questions trip people up

Applying one rulebook to everything. Candidates from plan-driven backgrounds treat every question as predictive. Candidates from agile backgrounds assume the team can decide everything.

Ignoring the verb "first". An answer can be sensible but come too late in the sequence.

Picking the heroic answer. The best answer is rarely "take over and fix it". It is usually "understand the situation, then work through the agreed channel".

Reading "agile" as "no process". Agile teams still have agreed ways of working. The leader's job is to serve and protect them, not to abandon structure.

Practising the skill

Take ten questions from any bank and write the approach beside each one before you look at the options. Then check whether your approach label matches the explanation. If you miss the label, you have found a reading gap rather than a knowledge gap, and reading gaps are fixed by drills, not by more textbook time.

Mark questions that mix approaches and keep a running list of the cues that fooled you. Within two weeks the list shortens quickly.