How to Recognise Predictive, Agile and Hybrid PMP Scenarios

A PMP scenario question almost never tells you which development approach is in play. It gives you a situation: a stakeholder asking for a change, a team debating priorities, a sponsor querying a forecast, and expects you to work out what kind of project you are looking at before you can work out what a competent project manager would do next. Candidates who know the theory of predictive, adaptive and hybrid delivery still lose marks here, because the exam is testing recognition, not recall.

The same difficulty shows up on real projects, usually in the first few weeks of a new assignment or when picking up work from someone else. Nobody hands you a document that says "this is a hybrid project, treat it accordingly." You infer it from how the work is actually being planned, sequenced and controlled, and you get it wrong at your peril, because responding to a stable, well-understood scope as though it were still evolving creates unnecessary churn, and responding to a genuinely uncertain solution as though it can be fully planned up front creates false confidence in a schedule that will not survive contact with reality.

What the cues actually look like

The starting point is to stop looking for the word "Agile" or "Waterfall" and start looking for what the situation tells you about certainty and control.

A predictive signal usually involves language about baselines, phases, formal change requests, fixed scope agreed with a client, or a sequence of deliverables that depend on earlier ones being complete. If a scenario describes a project manager comparing actual progress against an approved schedule, or escalating a variance through a change control process, that is predictive behaviour, and it belongs to a context where the solution was well enough understood at the outset to plan it in detail.

An adaptive signal looks different. It involves backlogs, iterations, retrospectives, reprioritisation in response to feedback, or a team adjusting what they build next because they learned something from what they just delivered. If the scenario shows a team accepting that requirements will keep evolving and building short feedback loops to manage that, you are looking at adaptive delivery, not disorganisation.

Hybrid scenarios are the ones candidates find hardest, because the scenario contains both sets of cues at once and expects you to notice that this is deliberate rather than confused. A construction project with a fixed completion date and regulatory milestones might still run its interior design and technology fit-out iteratively. A public-sector programme might hold firm, predictive governance and funding gates around software that is being built adaptively underneath. Section 4.2 of The Standard for Project Management frames these as legitimate combinations chosen because different parts of the work carry different degrees of certainty, not as a compromise between two purer methods.

The judgement question behind the recognition question

Once you can identify the approach, the harder skill is asking what that approach implies for the action the situation is asking about. This is where PMP preparation sometimes narrows into pattern matching: candidates learn to associate certain words with certain "correct" answers, without developing the underlying judgement.

A more durable habit is to ask three questions of any scenario, PMP or otherwise. What has already been fixed and agreed, and what is genuinely still being discovered? Who has the authority to absorb this change without escalation, and who does not? And does the proposed response match the level of certainty actually present in the situation, or does it borrow confidence from a different kind of project?

Consider a project manager running a mid-sized systems integration for a regional bank. The overall programme has a fixed regulatory go-live date and a formally baselined budget, agreed with the sponsor eighteen months earlier. Underneath that, the development team is building the customer-facing interface in two-week iterations, adjusting screens and workflows based on user testing feedback as they go. A stakeholder asks the project manager to add a new reporting feature midway through delivery.

The predictive layer of this project says the request needs to go through change control, because it affects a baselined budget and a regulatory deadline that cannot simply absorb scope creep. The adaptive layer says the development team can genuinely reprioritise the backlog to accommodate the feature once it is approved, without needing to replan the whole schedule. A project manager who treats the whole project as purely predictive will insist on a full change request before the team can even discuss feasibility, slowing down a conversation that the team is well placed to have quickly. One who treats it as purely adaptive risks quietly absorbing a change that has real budget and regulatory consequences. The competent response uses both layers correctly: a fast, informed conversation with the delivery team about feasibility, alongside a properly governed change decision at programme level before anything is committed.

Why this distinction matters beyond the exam

For a PMP candidate, the useful exam-preparation habit is to read every scenario for what has been fixed and what is still fluid, rather than searching for a keyword that signals the "right" methodology. Recognising the pattern is worth more than memorising a rule, and it is a skill that transfers directly once you are managing delivery rather than answering questions about it. If you want a structured way to practise exactly this kind of scenario reading, the PMP® Exam Preparation course builds the habit deliberately across the full syllabus rather than leaving it to chance on exam day.

An experienced project manager who has no intention of sitting the exam faces the same recognition problem constantly, usually when inheriting a project, joining a new organisation, or supporting a team whose delivery rhythm does not match the governance structure around it. The projects that go wrong are rarely the ones that are purely predictive or purely adaptive. They are the ones where someone applied the wrong logic to the wrong layer of the work, either governing an evolving solution as though it were fixed, or leaving a genuinely fixed commitment to drift as though it could still change freely.

Andre Malowney

Interested in going further?

If scenario questions are where your preparation feels least solid, that usually means the underlying recognition skill needs more deliberate practice than the theory does. Working through varied, realistic scenarios in a structured setting closes that gap faster than reading definitions again.

For a fuller treatment of how development approaches are defined and selected, the PMBOK® Guide Eighth Edition sets out the underlying framework in more depth than any single article can.

Ad · Amazon affiliate link.

References

A056: Predictive vs Agile vs Hybrid Project Management: How to Choose
A059: Hybrid Project Management Explained for Traditional Project Managers
A060: Why Hybrid Projects Use Agile and Traditional Artefacts Together
A062: Predictive Project Management Still Has a Place

PMP and PMBOK are registered marks of the Project Management Institute, Inc.