Predictive, Adaptive, or Hybrid? A PMP Exam Guide
- T. Laketia Jones
On the July 2026 PMP exam, about 40% of items represent predictive approaches, and the remaining 60% are divided between adaptive/agile and hybrid approaches [S1]. These approaches appear across all three exam domains rather than in a separate agile section [S1]. If you want to answer confidently, you need to know what each approach is, when it fits, and how to recognize the setting in a question.
Development Approach Versus Development Phase
PMBOK 8 draws a useful distinction. A development approach is the method used to create and evolve the product, service, or result, such as predictive, adaptive, or hybrid. A development phase is a stage in the life cycle where deliverables are built and tested [S2]. The Standard describes the approaches as a spectrum, with predictive at one end, adaptive at the other, and hybrid as a mix [S2].
The choice is usually made by the project manager with the project management team, based on requirements, scope, timeline, goals, culture, stakeholder involvement, risk, technology, and complexity [S3]. On the exam, the matching enabler is to recommend a development approach as part of planning [S4].
Predictive: Stable Scope, Plan Up Front
A predictive approach, also called waterfall, plan-driven, or traditional, may be best when scope can be stabilized early [S5]. Scope, schedule, cost, resources, quality, and risks can be well defined early and are expected to stay relatively stable, so much planning happens up front [S5]. When requirements are clear early, the scope, schedule, and cost baselines together form the integrated baseline [S3].
The Standard notes that predictive suits large projects with significant investment or regulatory oversight, and projects where iterating would cost far more than it is worth, such as the build phase of many construction projects [S5]. A predictive project can still deliver incrementally when the scope is well understood but phased delivery reduces size, complexity, or risk [S5].
Adaptive: Uncertain Requirements, Learn by Delivering
Adaptive approaches, also called change-driven or agile, fit projects whose requirements and technical solution are uncertain and likely to change [S6]. A clear vision is set at the start, and requirements are progressively elaborated based on feedback [S6]. Adaptive approaches can be iterative, refining through repeated cycles, and incremental, delivering usable pieces that build on each other [S6].
The Standard describes agile iterations of generally one to four weeks, ending with a demonstration, with the team estimating and selecting work from a prioritized backlog [S6]. Some adaptive methods use flow-based scheduling to optimize the flow of work and reduce waste [S6]. When requirements are less clear, work is reviewed in a timeboxed cadence so feedback shapes the evolving baseline [S3].
Test yourself on mixed approaches. Take a free PMP practice exam and notice how many questions are set in agile and hybrid environments.
Fixed and Flexible Constraints
Adaptive projects still have constraints. The Standard explains that projects often hold some constraints fixed and let others vary, sometimes called the inverted triangle [S3]. When scope is fixed, unexpected changes are absorbed by adjusting budget or schedule. When budget and schedule are fixed, changes are absorbed by varying scope [S3]. Many agile teams work the second way: time and cost are set by the iteration and team, and the backlog decides what gets built first.
The Standard also notes where adaptive approaches tend to fit, including new product development refined by market needs and digital or software projects with evolving scope and a need for early delivery [S7].
Hybrid: The Common Reality
A hybrid approach combines predictive and adaptive elements [S7]. The Standard's example is a custom home: iterate on the design, then build it predictively [S7]. Hybrid also fits when deliverables can be split into modules or developed by different teams [S7]. PMBOK 8 goes further and says that most projects today benefit from a hybrid approach, because relying only on one end of the spectrum does not address the complexity of modern projects [S8].
The Standard describes several forms: running adaptive and predictive work at the same time on different deliverables, adding a small adaptive element to a mostly predictive project, or adding a predictive component to a mostly adaptive one [S8]. It gives examples such as a smart building, where construction is predictive and the IT systems are adaptive, and an electronic medical records rollout, where infrastructure is predictive and the user interface is developed adaptively [S8]. It also cites PMI's Disciplined Agile tool kit, which describes three levels of hybrid based on which approach dominates [S8].
How to Read the Setting in a Question
- Words like sprint, backlog, product owner, iteration review, or velocity signal an adaptive setting. Favor answers that use the team's cadence, backlog refinement, and stakeholder feedback.
- Words like baseline, phase gate, change control board, or work breakdown structure signal predictive. Favor formal change control and the approved plan.
- A mix of both signals hybrid. The best answer often respects the governance of the predictive part while letting the adaptive part keep its cadence.
Common Traps
- Assuming agile means no planning. Adaptive projects plan continuously, just at different levels.
- Assuming predictive means no change. Predictive projects manage change through control processes.
- Forcing one approach everywhere. PMBOK 8 favors fitting the approach to the context. See Tailoring in PMBOK 8.
For more context on what the July 2026 exam expects, read our 2026 PMP exam changes overview and the AI and agile delivery article.
Frequently Asked Questions
What percentage of the PMP exam is agile or hybrid?
About 40% of items represent predictive approaches, and the remaining 60% are divided between adaptive/agile and hybrid approaches [S1].
When is a predictive approach best?
When scope can be stabilized early, and for large projects with significant investment or regulatory oversight, or where iterating would cost far more than it is worth [S5].
What is a hybrid approach in PMBOK 8?
A combination of predictive and adaptive elements. PMBOK 8 says most projects today benefit from some form of hybrid approach [S7][S8].
Your Next Step
The fastest way to get comfortable with mixed approaches is to practice them. Start with a free PMP practice exam, then build the full picture in the PMBOK 8 Exam Prep course.
Sources
- [S1] PMI, PMP Examination Content Outline (July 2026), p. 5 (approach mix across domains)
- [S2] PMI, The Standard for Project Management, in A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed. (2025), Section 4, development approaches, p. 59
- [S3] PMI, The Standard for Project Management, in A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed. (2025), Section 4, choosing an approach, p. 60
- [S4] PMI, PMP Examination Content Outline (July 2026), p. 9 (Process Task 1)
- [S5] PMI, The Standard for Project Management, in A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed. (2025), Section 4, predictive approach, p. 61
- [S6] PMI, The Standard for Project Management, in A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed. (2025), Section 4, adaptive approach, p. 63
- [S7] PMI, The Standard for Project Management, in A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed. (2025), Section 4, hybrid approach, p. 65
- [S8] PMI, The Standard for Project Management, in A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th ed. (2025), Section 4, hybrid forms and examples, pp. 65-66