First identify the delivery context
Look for explicit or implied signals before choosing an action. A baselined scope, formal acceptance, and contractual milestones suggest predictive governance. A prioritized backlog, short iterations, product ownership, and frequent feedback suggest adaptive delivery. Many real projects combine both.
- Predictive does not mean resistant to change.
- Agile does not mean undocumented or uncontrolled.
- Hybrid does not mean applying every process to every decision.
Scenario 1: a stakeholder requests a new feature
Predictive context: assess impact and follow the defined change-control process before altering an approved baseline. Agile context: clarify value and acceptance criteria, then let the authorized product role prioritize the item against other backlog work. Hybrid context: backlog reprioritization may still affect a governed milestone, budget, or contract and require escalation through the agreed boundary.
- Do not implement an unassessed request immediately.
- Do not reject change merely because planning already occurred.
- Respect established decision rights.
Scenario 2: the team discovers delivery risk
In any approach, make the risk visible, analyze it with the relevant people, select an owner and response, and monitor the result. Predictive work may emphasize the risk register and integrated plans; adaptive teams may address risk through backlog ordering, spikes, smaller increments, and frequent inspection.
- A risk is uncertain; an issue has occurred.
- Escalation is not automatically the first response.
- Choose a response proportionate to probability, impact, and urgency.
Scenario 3: quality problems appear repeatedly
Predictive response may include root-cause analysis, quality-control results, process improvement, and approved corrective action. Adaptive response may strengthen the definition of done, automation, pairing, refinement, or retrospective experiments. Both should address the system causing defects rather than blame an individual.
- Inspection finds defects; prevention reduces recurrence.
- Protect transparency so the team can surface problems.
- Verify that the corrective action worked.
Scenario 4: a deadline cannot move
A fixed date does not justify silently sacrificing quality. In predictive work, analyze compression options, dependencies, cost, scope, and risk through the appropriate governance. In adaptive work, protect the timebox and negotiate scope or ordering with the product authority. In hybrid work, preserve the fixed external milestone while adapting internal increments where permitted.
- Make tradeoffs explicit.
- Do not promise recovery before analysis.
- Engage the people who own priority, funding, or acceptance.
A reusable elimination sequence
Ask: What happened? Which approach and governance apply? Who owns the decision? Is this a risk, issue, change, impediment, or defect? Should the project manager assess, collaborate, act, or escalate next? Eliminate choices that skip diagnosis, bypass authority, hide information, or impose a disproportionate response.
- Prefer problem-solving over blame.
- Use the least disruptive responsible action.
- Communicate through the agreed structure.
- Reassess after the response.
Verify current exam details at the PMI PMP certification page. PrepVanta is independent and is not affiliated with or endorsed by the certification provider.