PMP Agile vs Predictive vs Hybrid: Reading What the Question Actually Wants

Roughly 60 percent of the PMP® exam is now agile or hybrid. Predictive is down to about 40 percent, and none of it is siloed, so a People or Business Environment question can arrive wearing an agile costume.

So half the battle is reading the scenario correctly. Get the approach wrong and you'll pick a perfectly reasonable predictive answer to an agile question, and it'll be marked wrong. Here's how to tell what's really being asked.

Read the signals first

Most scenarios tell you which world you're in if you catch the vocabulary.

A scenario is predictive when scope is fixed and known up front, there's a detailed plan and baseline, work moves through phases and gates, changes run through a change control board, and the sponsor wants a firm date and cost. Words like "the plan," "the baseline," and "the schedule" are the tell.

A scenario is agile or adaptive when you see sprints or iterations, a product owner, a backlog, daily standups, reviews, retrospectives, velocity, or "evolving requirements." The team is delivering something usable each iteration instead of one big handoff at the end.

A scenario is hybrid when both vocabularies show up together. A fixed, compliance-heavy, or contracted piece sitting next to an evolving one. Think regulated hardware being built predictively while the software layer on top is built in sprints. If you see both languages in one question, it's hybrid.

The quick rule: match the vocabulary to the approach, and when both appear at once, you're in hybrid territory.

The hybrid rule almost everyone gets wrong

Hybrid does not mean "do all the predictive planning first, then switch to agile." That's the most common misread on the exam, and it feels right to a predictive PM, which is exactly why it's dangerous.

Hybrid means running the right approach on each part of the work at the same time. The fixed, well-understood, or compliance-driven work runs predictive. The evolving, discovery-heavy work runs adaptive. In parallel, not in sequence. So when an answer offers "finish all the upfront planning, then move the team to sprints," treat it as a trap until proven otherwise. Two approaches, running side by side, each on the work it fits.

Traps that catch predictive PMs

If you've spent years running predictive projects, a few instincts will steer you into wrong answers. These are the ones I see catch people most.

Protecting the sprint. Once a sprint is underway, its scope is protected. A stakeholder, even an executive, can't drop a new must-have into a sprint that's already running. The new request goes to the product backlog, and the product owner reprioritizes it for a future sprint. Predictive instinct says "accommodate the important stakeholder." The agile answer protects the team's committed work and routes the request to the backlog.

Who owns the backlog. The product owner owns and prioritizes the backlog. Not the project manager, not the team, not the loudest voice in the room. The team decides how much it can pull into a sprint and how to build it. Priority is the product owner's call. Any answer that has the project manager setting priorities is predictive command thinking in disguise.

Definition of Done vs acceptance criteria. These get mixed up constantly. Definition of Done is team-level and applies to every backlog item: the shared bar for "actually finished," like tested, integrated, and documented. Acceptance criteria are specific to one story and come from the product owner: the conditions that particular story has to meet to be accepted. One is global and owned by the team. The other is per-story and owned by the product owner. Meeting one doesn't excuse the other.

Underneath all of these is servant leadership. In adaptive scenarios the PM coaches, facilitates, and clears blockers instead of directing. If an answer has you commanding the team, it's usually the wrong one.

Two questions that trip up predictive-minded PMs

Original and illustrative, written to show the reasoning. Not real exam questions.

1. The mid-sprint VIP request

Three days into a two-week sprint, a senior executive tells you a new feature is critical and has to go into the current sprint. What should you do?

• A. Add the feature to the current sprint. The executive is a key stakeholder.
• B. Ask the team to work overtime to fit it in.
• C. Add the request to the product backlog and have the product owner prioritize it for a future sprint.
• D. Escalate to the sponsor for a decision.

Answer: C. Sprint scope is protected once the team commits to it, and even an executive doesn't get to override a sprint in progress. The request is legitimate, so it goes to the backlog where the product owner weighs it against everything else. A and B break the team's protected work, which is the predictive "accommodate the VIP" reflex. D escalates something you can handle with the normal agile mechanism, so it isn't the best first move.

2. Done, or just accepted?

A developer says a story meets all of its acceptance criteria and asks you to mark it done. The story hasn't been integrated or regression-tested, which your team's Definition of Done requires. What's the best response?

• A. Mark it done. The acceptance criteria are met.
• B. It isn't done until it also meets the team's Definition of Done, so integration and testing still apply.
• C. Ask the product owner to waive the Definition of Done for this story.
• D. Redefine the Definition of Done so this story qualifies.

Answer: B. Acceptance criteria are per-story and come from the product owner. The Definition of Done is the team's global bar and applies to every item. Meeting one doesn't let you skip the other. A confuses the two. C and D quietly lower the quality bar for convenience, and the Definition of Done isn't something you bend story by story to close a ticket.

The quickest way to stop misreading these is volume. Free agile and hybrid practice questions with full explanations are at pmprep.app/practice, and a stretch of them will train your eye to spot the approach before you even reach the options.

PMP, CAPM, PMI-ACP, and PMI are registered marks of the Project Management Institute, Inc. pmprep.app is an independent study resource and is not affiliated with or endorsed by PMI.