PMP Exam Prep Companion: Predictive vs. Agile vs. Hybrid—Choosing Actions That Fit the Approach

Three Approaches, One Goal: Plan, Deliver, Control

On the PMP exam, “predictive,” “agile,” and “hybrid” are not labels for industries—they describe how you plan the work, how you deliver value, and how you control change. The fastest way to choose the right next action in a scenario is to identify which approach is being used and then respond in a way that fits that approach’s rules.

• Predictive: plan most work up front, deliver mostly at the end (or in big phases), control change through formal approval.
• Agile: plan in small slices, deliver frequently in increments, control change by continuously re-ordering work in a backlog.
• Hybrid: some parts are fixed and governed predictively, while other parts are flexible and delivered iteratively.

(1) Predictive: Planning First, Then Change Control

How predictive work is planned

Predictive projects aim to reduce uncertainty by defining scope and planning the path to deliver it. Planning is heavier up front because the team expects the plan to remain mostly stable.

• Plan the whole: requirements are gathered and finalized early.
• Build the roadmap: work is decomposed into tasks and sequenced.
• Set baselines: scope/schedule/cost targets become the reference for performance and change decisions.

How predictive work is delivered

Delivery often happens as a single release at the end or as major phase gates (e.g., design complete, build complete, test complete). Acceptance is usually tied to meeting documented requirements.

How predictive work is controlled (change control)

Predictive control is based on protecting the baseline. Changes are not “bad,” but they are handled deliberately so impacts are understood and approved.

Step-by-step: handling a new requirement in predictive

1. Clarify the request: what exactly is changing and why?
2. Assess impact: estimate effects on scope, schedule, cost, quality, and risks.
3. Document a change request: include rationale and impact summary.
4. Submit for approval: follow the project’s formal change control process.
5. Update plans if approved: revise baselines and communicate the decision.
6. Implement and track: execute the approved change and monitor results.

Exam clue: If the scenario mentions “baseline,” “change control board,” “formal approval,” “contract change,” or “requirements sign-off,” the expected next step is usually a formal change request and impact analysis—not quietly adding work.

Continue in our app.

• Listen to the audio with the screen off.
• Earn a certificate upon completion.
• Over 5000 courses for you to explore!

Or continue reading below...

Download the app

(2) Agile: Iterative Delivery, Backlog Refinement, Adaptive Planning

How agile work is planned (adaptive planning)

Agile planning is continuous. The team plans in detail only for the near term and keeps the rest at a higher level until it becomes “next up.”

• Vision and goals: agree on outcomes and success measures.
• Backlog-driven: work is expressed as backlog items (often user stories).
• Rolling-wave detail: near-term items are refined; later items stay coarse.

How agile work is delivered (iterative increments)

Agile delivers value in small, usable increments. Each iteration (often a sprint) aims to produce a potentially shippable increment that can be reviewed with stakeholders.

• Short cycles: timeboxed iterations create frequent feedback points.
• Increment each cycle: working product evolves step-by-step.
• Inspect and adapt: feedback changes what to do next.

Backlog refinement: what it is and why it matters

Backlog refinement is the ongoing activity of making upcoming work clear enough to build. It reduces surprises without trying to lock everything down months in advance.

• Clarify: add acceptance criteria and remove ambiguity.
• Split: break large items into smaller, testable pieces.
• Estimate: size items so the team can forecast what fits.
• Re-order: prioritize based on value, risk, and dependencies.

Adaptive planning: what changes and what stays stable

In agile, the plan changes frequently, but not everything is unstable. The team keeps stable elements like the iteration length, working agreements, and quality standards. What adapts is the content of upcoming work and the order of delivery.

Step-by-step: handling a new requirement in agile

1. Capture it as a backlog item: describe the value and user need.
2. Discuss with the product owner: confirm priority relative to other work.
3. Refine: add acceptance criteria; split if too large.
4. Re-prioritize: move it up or down based on value and urgency.
5. Plan it into an iteration: pull it into the sprint backlog when ready and prioritized.
6. Deliver and review: demonstrate the increment and gather feedback.

Exam clue: If the scenario mentions “sprint,” “backlog,” “user stories,” “product owner,” “iteration review,” or “adaptive planning,” the expected next step is usually to update/refine/re-prioritize the backlog and collaborate—rather than raising a formal change request for every new idea.

Roles and Artifacts: Plain-Language Comparison

(3) Hybrid: Boundaries—What Is Fixed vs. Flexible

Hybrid combines predictive and agile on purpose. The key is to define boundaries: which elements are governed as fixed commitments and which elements are allowed to evolve through iterative delivery.

Common “fixed” elements in hybrid (predictive-leaning)

• High-level scope boundaries: what the solution must include (and exclude).
• Major milestones: regulatory dates, market launch windows, integration events.
• Budget constraints: funding caps or fixed-price contract limits.
• Governance and approvals: stage gates, compliance sign-offs, audit needs.

Common “flexible” elements in hybrid (agile-leaning)

• Detailed requirements: refined as the team learns from demos and feedback.
• Delivery sequence: prioritized by value and risk, adjusted frequently.
• Solution design details: evolved through iteration and validation.
• Team-level planning: iteration planning, daily coordination, continuous refinement.

Step-by-step: setting hybrid boundaries so decisions are easy later

1. Identify non-negotiables: compliance, safety, contractual terms, hard deadlines.
2. Define what can vary: features, user experience details, reporting formats, etc.
3. Choose control mechanisms: formal change control for fixed items; backlog management for flexible items.
4. Map delivery cadence: iterations for build + periodic governance reviews for approvals.
5. Agree on acceptance rules: DoD for team quality + formal acceptance for gated deliverables.

Exam clue: In hybrid scenarios, the best next step often depends on whether the change touches a fixed boundary (use formal control) or a flexible area (use backlog refinement and reprioritization).

Decision Practice: “What Do You Do Next?” Scenarios

Scenario 1: Changing requirements midstream

Situation: A stakeholder asks to add a new reporting feature that was not in the original requirements. The project is halfway through execution.

• If predictive: Perform impact analysis and submit a formal change request for approval before adding work.
• If agile: Capture it as a new backlog item, refine it, and have the product owner re-prioritize it against existing items.
• If hybrid: Ask: does the feature affect a fixed milestone, budget cap, or contractual scope? If yes, use formal change control; if no, add to the backlog and prioritize for a future iteration.

Scenario 2: Stakeholder wants “just squeeze it into this sprint”

Situation: During an iteration, a senior stakeholder requests an urgent change and asks the team to add it immediately.

• If agile: Do not silently add work. Bring it to the product owner. Options: swap with equal-sized work in the sprint backlog, or place it in the product backlog for the next iteration, depending on urgency and team capacity.
• If predictive: Treat it as a change request; evaluate impact and follow approval steps.
• If hybrid: If the sprint is part of an agile delivery component, manage it through the product owner/backlog; if it impacts fixed governance commitments, escalate through formal change control.

Scenario 3: Quality disagreement—“done” vs. “done done”

Situation: The team says a feature is complete, but testing and documentation are not finished. A manager wants to demo it anyway.

• If agile: Use the Definition of Done as the rule. If it does not meet DoD, it is not “done” and should not be counted as completed work; decide whether a partial demo is acceptable without misrepresenting completion.
• If predictive: Check completion/acceptance criteria and quality procedures for the deliverable; do not claim completion until required verification steps are done.
• If hybrid: Apply DoD for iteration-level completion, and also ensure any gated deliverables meet formal acceptance requirements before sign-off.

Scenario 4: Customer feedback after a demo changes priorities

Situation: After reviewing the latest increment, the customer realizes a different feature is more valuable than what was planned next.

• If agile: Re-order the product backlog. Refine the newly important items and plan them into upcoming iterations.
• If predictive: If the new direction changes approved requirements, raise a change request and evaluate impacts before altering the plan.
• If hybrid: Reprioritize within the flexible scope, but confirm that milestone dates, compliance items, and fixed deliverables remain protected (or formally changed if needed).

Scenario 5: Contract constraints meet iterative delivery

Situation: You are building a solution iteratively, but the vendor contract is fixed-price with a tightly defined statement of work.

• Best-fit interpretation: This is typically hybrid. Use agile practices for internal delivery (iterations, backlog refinement), but manage vendor scope changes through formal contract change control. Keep a clear boundary between “re-ordering within agreed scope” and “changing contracted scope.”

Quick Recognition Checklist: Pick the Action That Matches the Approach

• Predictive next actions: impact analysis, formal change request, approval workflow, update controlled plans.
• Agile next actions: add/refine/reprioritize backlog, collaborate with product owner, plan in iterations, deliver an increment and get feedback.
• Hybrid next actions: first classify the change as touching a fixed boundary or a flexible area; then use the matching control method (formal change control vs. backlog management).