Agile vs Hybrid vs Predictive Questions on the PMP Exam

A common PMP error is choosing a sound project-management action that belongs to a different delivery approach. Formal baseline control may be right in a predictive environment but unnecessarily slow for an adaptive product decision. Immediate backlog reprioritisation may suit an agile team but bypass a contractual or governance gate in a hybrid programme.

The July 2026 PMP Examination Content Outline states that approximately 40% of items represent predictive approaches, while adaptive/agile and hybrid approaches make up the remaining 60%. Exact proportions vary by examination form, and all three approaches appear across People, Process and Business Environment. The task is therefore not to memorise three separate syllabuses. It is to recognise which operating model governs the decision.

Agile, Hybrid and Predictive Compared

Dimension	Adaptive/agile	Hybrid	Predictive
Planning	Progressive and frequently revisited	Different planning cadences for different work or governance layers	More work planned against an integrated baseline
Scope and priorities	Evolve through feedback and ordered work	May evolve in one component while fixed commitments govern another	Changes evaluated against approved scope and baselines
Delivery	Frequent increments and learning cycles	Iterative delivery within broader phases, gates or release controls	Delivery organised through planned phases or work packages
Decision roles	Empowered team with product ownership and facilitation	Agile team roles coexist with programme, sponsor or governance authority	Project manager and defined control bodies coordinate planned delivery
Change mechanism	Refine and reorder work using feedback	Use the mechanism appropriate to the affected layer	Analyse impact and use formal integrated change control where required
Typical exam risk	Commanding the team or freezing learning too early	Applying one method to every layer	Bypassing baseline, contract or governance controls

How to Recognise an Adaptive or Agile Question

Look for short iterations, a product backlog, product owner, retrospectives, demonstrations, incremental delivery, team facilitation and frequent customer feedback. The team may be solving uncertainty by delivering a small amount, learning from evidence and adapting the next priority.

• Work with the product owner or equivalent value owner when ordering product work.
• Use the team’s knowledge and facilitate self-management rather than assigning every solution.
• Make impediments, risks and progress visible.
• Prefer early feedback and small value increments when the context supports them.
• Treat change as information to evaluate, not automatically as failure to follow a plan.

How to Recognise a Predictive Question

Predictive scenarios often mention approved baselines, detailed plans, formal procurement, phase sequencing, work packages, change control boards and performance measured against planned commitments. This does not mean communication or adaptation disappears. It means changes to controlled commitments follow an established evaluation and approval process.

• Assess the impact of a proposed change before implementation.
• Use the approved change-control process when baselines or controlled commitments are affected.
• Update relevant plans and communicate authorised decisions.
• Distinguish corrective action within existing authority from a baseline change requiring approval.
• Use forecasts and performance data to support decisions rather than relying on status alone.

How to Recognise a Hybrid Question

Hybrid delivery intentionally combines practices because different parts of the initiative have different uncertainty, governance or delivery needs. A software team may work in iterations while infrastructure procurement follows fixed contracts. A product may be refined through demonstrations while programme funding and regulatory releases remain controlled through gates.

When a question is hybrid, identify the layer affected by the problem. A team-level priority may be handled through backlog refinement, while a regulatory release date or approved funding boundary may require governance action. The strongest response connects the two systems instead of forcing one to replace the other.

The Same Change Request in Three Contexts

Context	Likely first reasoning step	Potential mistake
Adaptive/agile	Clarify value and acceptance needs with the product owner and team, then consider ordering it in the backlog.	Submitting every emerging product detail to a formal change board without evidence that one is required.
Hybrid	Determine whether the feature fits team-level product authority or affects a controlled scope, release, budget or compliance gate.	Assuming the agile team can alter an external commitment without coordinating governance.
Predictive	Analyse impacts on approved scope, schedule, cost, risk and quality before the authorised change decision.	Directing implementation before approval because the customer requested it.

Question Clues: Useful but Not Sufficient

Clue	Likely signal	Caution
Sprint, backlog, retrospective, product owner	Adaptive/agile	The wider programme may still use hybrid governance.
Baseline, change control board, work breakdown structure	Predictive	The team can still collaborate and adapt within approved boundaries.
Iterations plus phase gates or fixed regulatory release	Hybrid	Identify which decision belongs to which layer.
High uncertainty and frequent feedback	Adaptive tendency	Contracts, safety or compliance may constrain the available mechanism.
Stable requirements and sequential dependencies	Predictive tendency	Stability does not justify ignoring new evidence or stakeholder needs.

Three Mini Scenarios

1. A product owner learns from an iteration review that users value a different workflow. The team discusses acceptance criteria and reorders future work. This is an adaptive decision pattern.
2. A construction project identifies a scope change affecting an approved cost and schedule baseline. The project manager analyses impacts and submits the change through the authorised process. This is a predictive decision pattern.
3. An iterative software team must demonstrate compliance evidence at a programme release gate. The project manager coordinates backlog work with the governance milestone. This is a hybrid decision pattern.

Common Approach-Selection Mistakes

• Choosing every collaborative answer as agile even when the scenario is predictive; collaboration applies to all approaches.
• Treating every change as either automatically welcome or automatically controlled; first identify what commitment changes.
• Assuming hybrid means using agile vocabulary inside an otherwise predictive plan.
• Ignoring organisational governance because a delivery team is self-managing.
• Memorising artefacts without understanding the decision rights they represent.

A Better Way to Practise

Practise in contrast sets. Take one issue—stakeholder feedback, a quality defect, a regulatory change or a delivery delay—and write the response in adaptive, hybrid and predictive contexts. Name the decision owner, evidence, control mechanism and next action in each version. This teaches tailoring more effectively than memorising three lists of keywords.