Concept · under Integrated planning, delivery approach and scope
Predictive, agile and hybrid approaches for the PMP® exam
Choosing between predictive, agile and hybrid delivery comes down to the facts of the project: how stable the requirements are, how much uncertainty there is, what regulation demands, and how often the customer can use a delivery. PMI®'s 2026 content outline sets roughly 40% of items in predictive projects and 60% in agile or hybrid ones (as of October 2026), so the choice sits underneath every domain. Choosing the approach is part of integrated planning, delivery approach and scope.
- Exam
- PMP
- Domain
- Process
- Domain weight
- 41%
- Packages
- 8
- Updated
- Oct 13, 2026
02Signals in a scenario
| Fact in the stem | Leans predictive | Leans adaptive |
|---|---|---|
| Requirements | Known and stable | Unclear or expected to move |
| Delivery | One usable result at the end | Usable pieces early and often |
| Compliance | Documented approvals required before work proceeds | Requirements that can be met inside each increment |
| Customer involvement | Reviews at milestones | Regular feedback from users or a product owner |
| Technology | Proven, done many times | New to the team or the market |
Scenarios rarely line up on one side. When the facts point both ways, a hybrid tends to fit: predictive where the work is fixed, adaptive where it is not.
03Life cycles that get mixed up
- Predictive
- Scope, schedule and cost are planned up front and change is managed against baselines. Delivery usually comes at the end.
- Agile (adaptive)
- Iterative and incremental at once: short cycles that each produce a usable increment, with the plan revised from what was learned.
- Hybrid
- A deliberate mix, for example a predictive construction schedule for a clinic alongside agile development of its patient app.
04What a sensible hybrid looks like
Does a company-wide standard settle the question? It narrows the options, but the approach still has to fit each project, so one phase-gate template applied to both a marketing website and a data-center build is a warning sign.
A hybrid earns its overhead when ownership of the seams is planned: who keeps the release plan, how backlog progress shows up in the schedule and the budget, and which decisions still need a formal gate. Predictive paperwork piled on top of sprints, with nobody owning the join, tends to get the costs of both and the benefits of neither.
Related pages
The agile estimating artifacts are on story points, velocity and burn charts, and delivering in usable increments for value is on value-based and incremental delivery. How the approach mix entered the 2026 outline, next to the outline it replaced, is on PMP exam changes in 2026.
05Match the life cycle to the facts
Each scenario describes a project; naming the life cycle that fits it is your part.
Work packages 8
WP 01A global project involves executives demanding strict formal phase-gate approvals and distributed end-users requiring frequent iterative feedback loops. How should the project manager tailor the delivery methodology to satisfy these conflicting stakeholder cadence needs?
Debrief answer to open the notes
- ACorrect: A hybrid approach lets executives keep phase-gate governance while users get the frequent feedback of adaptive iterations.
- BA fully agile framework serves users but ignores the executives' legitimate need for formal approvals.
- CA strictly predictive approach satisfies executives but denies users the frequent feedback they need.
- DSplitting stakeholders into separate teams fragments the project rather than tailoring a single approach.
WP 02A project team initially selected a highly adaptive approach to navigate high uncertainty during early discovery. As the project enters a stable nationwide rollout phase, performance metrics begin declining. What is the most appropriate action for the project manager?
Debrief answer to open the notes
- AKeeping an approach for consistency ignores that the project's conditions have changed; tailoring should follow the context.
- BReplacing the team is drastic and unnecessary; the approach, not the people, needs to change.
- CCorrect: Tailoring is revisited as conditions change; a stable rollout suits more predictive controls than early, uncertain discovery did.
- DTermination is unwarranted when the issue is a mismatch between approach and phase, which can be corrected.
WP 03A project to develop a mobile application is facing frequent scope changes due to evolving market conditions. The project manager wants to implement a more flexible approach to handle these changes. Which of the following would be most appropriate?
Debrief answer to open the notes
- AHolding back all feedback until the end is the opposite of what volatile scope needs.
- BCorrect: Incremental delivery with feedback after each release lets the team absorb changing market needs in small, low-cost steps.
- CStretching the timeline for every possible change is impossible to plan and leaves the approach unchanged.
- DFreezing scope ignores real market changes and risks delivering a product nobody wants.
WP 04A water utility must replace a pipeline crossing under a river. The route and pipe specification are fixed by an environmental permit, and any revision needs a new permit. Once the pipe is pulled under the riverbed it cannot be reworked, and no water can flow until the whole crossing passes a pressure test. Which life cycle should the project manager recommend?
Debrief answer to open the notes
- ACorrect: requirements fixed by permit, rework that is impossible once the pipe is in, and one usable result at the end all point to planning up front.
- BSprints pay off when requirements can move and each increment is usable; here the route is fixed by the permit and a partial crossing delivers nothing.
- CA hybrid fits when the facts split between stable and uncertain work; nothing in this crossing is uncertain enough to iterate on.
- DNo water flows until the whole crossing passes its test, so there are no usable sections to hand over early.
WP 05A city transit agency wants its new trip-planning app to deliver usable functionality early: first a timetable lookup, then route planning a few months later, then fare payment. Each feature is well understood, and each release must be complete and usable on its own. Which life cycle best fits this need?
Debrief answer to open the notes
- AA single release at the end gives the agency nothing usable early, which is the main thing it asked for.
- BIterative cycles refine a product through feedback on unfinished work; that suits unclear requirements, not early usable releases.
- CCorrect: An incremental life cycle delivers finished, usable pieces in successive releases, matching the agency's need.
- DPhase gates control progress between phases but still delay the usable product until the end.
WP 06A project manager is implementing a hybrid approach for a product development project. The team is using iterative development for software components while following a sequential approach for hardware development. What is the MOST important consideration when integrating these two methodologies?
Debrief answer to open the notes
- ACorrect: when software iterates and hardware runs sequentially, planned integration points keep both streams aligned while each uses the approach that fits its work.
- BDaily status meetings add overhead but do not define when the two streams must come together.
- CCross-training everyone in both methods is costly and does not solve the timing problem between the streams.
- DForcing hardware into iterations ignores why it was planned sequentially; a hybrid approach keeps each part where it fits.
WP 07A project team is using a predictive approach for a construction project but experiencing challenges with requirements changes. Which hybrid element could they introduce to better handle changing requirements while maintaining overall project structure?
Debrief answer to open the notes
- AFreezing requirements is the opposite of handling change; it pushes the problem into late rework.
- BRemoving change control would let changes in without any impact analysis or approval.
- CSwitching fully to agile discards the structure a construction project still needs for permits and sequencing.
- DCorrect: planned adaptation points at phase boundaries let the team revisit requirements on a schedule while the predictive structure stays in place.
WP 08You are managing a construction project that consists of multiple stages. Recently, your sponsor informed you of new regulatory requirements that mandate a specific project execution methodology. Your current project management plan outlines an iterative approach. What element of your project management plan needs to be revised?
Debrief answer to open the notes
- AThe quality management plan covers standards and quality activities, not the overall delivery method.
- BThe communication management plan covers who gets what information; it does not set the methodology.
- CCorrect: the development approach records how the work will be delivered, such as predictive, iterative or hybrid, so a mandated method changes it.
- DThe risk management strategy covers how risk is handled; the execution method itself is defined elsewhere.
Open a row to answer. Keys: 1–4 or A–D answer, N opens the next row.
06Choosing an approach: common questions
Is agile the better answer by default?
Fit matters more than the label. Agile and hybrid settings are the majority of items, as the chart above shows, but predictive planning is still the right call when a project's facts point that way.
Is hybrid the safe default?
A hybrid has real costs: two sets of artifacts and seams that need an owner. Choose it when the facts genuinely split; size or complexity alone is not a reason for it.
Is Scrum the same thing as agile?
Scrum is one agile framework; kanban and Extreme Programming are others. Scrum terms such as sprint and product owner are everywhere in agile writing, but agile principles do not depend on Scrum events.