Many PMP questions have two answers that look correct. Often the difference is the environment the question is set in. The same situation can have a different best answer on a predictive project than on an agile one. Learning to spot the environment first will settle a lot of these close calls.
Step 1: Find the clues
Before you read the options, scan the stem for words that tell you the approach.
Predictive clues: baseline, WBS, change control board, Gantt chart, phase gate, statement of work, work package, project management plan.
Agile clues: sprint, iteration, backlog, product owner, scrum master, velocity, retrospective, daily standup, user story, Kanban board.
Hybrid clues: a mix of the above, or phrases like "some components are well defined while others will evolve", "regulatory requirements" alongside "user feedback", or "the organization uses phase gates but the team works in sprints".
If there are no clues at all, PMI generally expects you to answer from a general, principle-based view.
Step 2: Apply the right logic
Scope changes
- Predictive: analyze the impact, submit a change request, and let the change control board decide.
- Agile: the product owner adds the item to the backlog and prioritizes it. There is no change control board for backlog changes.
- Hybrid: it depends on which part of the project the change touches. A change to the fixed, baselined part goes through change control; a change to the adaptive part goes to the backlog.
Who decides
- Predictive: the project manager plans and coordinates, and escalates decisions above their authority.
- Agile: the team decides how to do the work, the product owner decides what to build and in which order, and the project manager or coach removes impediments.
Tracking progress
- Predictive: earned value, variance against baselines, milestone reports.
- Agile: burndown and burnup charts, velocity, working increments shown at the review.
Problems in the team
- Predictive: the project manager addresses it directly, usually privately and early.
- Agile: let the team try to solve it first; bring it up in the retrospective if it affects how the team works. Step in when the team cannot resolve it or it is outside their control.
Step 3: Watch for the tailoring question
The July 2026 exam puts more weight on choosing an approach. Signals:
- High uncertainty in requirements, frequent customer feedback, value in early delivery: lean adaptive.
- Fixed legal requirements, heavy dependencies, safety constraints, expensive late changes: lean predictive.
- Both at once: hybrid, applying each approach to the part it fits.
A common trap is the answer that forces one approach onto everything. Splitting the work into two separate projects, or putting regulatory scope into a backlog with no formal control, are both usually wrong when a hybrid structure would serve better.
A worked example
A project has a regulatory reporting module fixed by law and a customer portal whose features will evolve. The sponsor wants one integrated plan.
The best answer baselines the regulatory module under change control and manages the portal from a prioritized backlog within a fixed budget and timebox. Putting both into one WBS with rolling wave planning sounds sensible, but it still forces the portal through change control that works against expected change.
Practice
The skill is recognizing the pattern quickly. Practice questions that mix all three environments, and after each one ask yourself: which clue told me the environment, and did my answer match it? Our free 30-question quiz includes predictive, agile and hybrid scenarios at exam difficulty.