Development Approaches & Tailoring: Choose the Right Approach for Your Project

The question every project opens with is not "what is the plan?" but "what kind of planning suits this work?" The common error is answering it out of habit or fashion: one organization plans everything up front because it always has, another declares itself agile because that is newer. The Eighth Edition treats the matter differently — as a decision resting on specific variables in the deliverables, the project, and the organization, not on preference. It goes further, noting that the diversity of these factors often implies several development approaches may be used within the same project for different deliverables.

Definition and Foundation

There are three approaches in the Eighth Edition, each with conditions that make it optimal:

• Predictive — may be optimal when project scope can be stabilized early. Also referred to as waterfall, plan-driven, or traditional. It suits large projects involving significant investment or regulatory oversight, where robust change control mechanisms and planned reevaluation between successive phases are required. Scope, schedule, cost, resource needs, quality requirements, and risks are well defined in the early phases and expected to remain relatively stable.
• Adaptive — also referred to as change-driven or agile. Useful when a project's requirements and technical solution are subject to a high level of uncertainty and volatility and are likely to change significantly. A clear vision is established at the start, and the initial known requirements are progressively elaborated, changed, or replaced in accordance with stakeholder feedback, the environment, or unexpected events.
• Hybrid — a combination incorporating some elements from a predictive approach and some from an adaptive one. It may be appropriate when there is uncertainty or risk around the requirements, such as the design of a custom home: once the design is complete, it makes sense to iterate no more than once for the build. It is also useful when deliverables can be modularized, or when different project teams develop different deliverables.

The Eighth Edition takes an explicit position: most projects can strongly benefit from a hybrid approach combining both, because focusing exclusively on either does not fully address the varied challenges and complexities modern projects present. A hybrid approach provides flexibility to adapt to changing conditions while retaining control over predictable aspects.

It is worth separating adaptive from incremental. In certain predictive approaches it may be optimal to deliver the product partially and incrementally rather than as a single, final release. An incremental approach is used when the overall scope is well understood and planned up front, but phased delivery offers advantages due to size, complexity, or specific risk factors. There, the overall scope and timeline remain largely fixed — which is the essential difference from an adaptive approach.

How It Works in Practice

Deliverable variables

Nine stated variables influence the choice. Degree of innovation — new or complex technological or business model innovation favors adaptive. Requirements certainty — well-known, straightforward requirements favor predictive. Degree of scope stability — the less stable the scope, the more optimal adaptive becomes. Ease of change — if the deliverable makes change difficult or costly to incorporate, predictive may be optimal. Delivery options. Risk — adaptive approaches may help manage risk and uncertainty. Safety requirements — products with rigorous safety requirements often use predictive because significant up-front planning is needed for compliance. Feedback — where frequent end-user feedback carries significant value, adaptive may be optimal. Regulations — environments with significant regulatory oversight may use predictive due to required processes, documentation, and demonstration needs.

Project and organization variables

At project level: size and complexity, since more flexible approaches suit larger, complex projects with evolving requirements; team experience and skills, since adaptively managed projects benefit from teams strong in communication, collaboration, and problem-solving; and interdependencies on other projects or departments.

At organizational level: structure — organizations with a fixed functional structure and traditional hierarchies are more inclined to predictive due to preferred lines of authority, while network-oriented structures embrace adaptive or hybrid more naturally. Culture — predictive fits an organization that manages and directs, where work is planned and progress measured against baselines; adaptive fits a culture that embraces uncertainty while emphasizing self-managed teams, flexible thinking, and innovation. Organizational capability. Team size and location — adaptive often works better with smaller teams, some frameworks recommending between three and nine members, and some adaptive methods call for colocation.

The four hybrid patterns

The Eighth Edition presents four common patterns: early processes using an adaptive life cycle followed by a predictive rollout; a combination of both throughout the life cycle; a small adaptive element within a primarily predictive project; and a largely adaptive approach with a predictive component. Its examples include a construction project (predictive) building a smart building whose complex IT systems need flexibility during development (adaptive), and an electronic medical records implementation where infrastructure setup is predictive while the user interface benefits from adaptive work.

Delivery cadence

Based on the selected approach, projects can have a single delivery producing all outcomes at the end, multiple deliveries of different components at different times, periodic deliveries, or continuous delivery. This dimension is separate from the approach even where it is influenced by it, so predictive should not be assumed to mean a single delivery.

On the Exam

The 2026 ECO makes approach selection an enabler in its own words: Domain II, Process, Task 1 — develop an integrated project management plan and plan delivery — carries "recommend a project management development approach (i.e., predictive, adaptive/agile, or hybrid management)," alongside "assess project needs, complexity, and magnitude" and "recommend a project execution strategy." Task 8 connects through its enabler "prepare a schedule based on the selected development approach."

The dominant pattern is a scenario describing a project's characteristics and asking which approach fits. Four keys settle most of it:

• Strict regulation or safety requirements → predictive, however technical the project looks.
• Cost of iterating far exceeding its value → predictive, as in the build phase of construction.
• Two deliverables of different natures inside one project → hybrid, not one approach for both.
• A question about the "best" approach with no characteristics given → no approach is best in the abstract; the answer rests on the variables.

What deceives is options presenting adaptive as newer and more efficient, or predictive as more disciplined. Both are value judgments the guide does not support. So does conflating incremental with adaptive: incremental delivery happens within a predictive approach, with the overall scope and timeline remaining largely fixed.

Detailed Mistakes

Treating the approaches as three separate options

The Eighth Edition presents hybrid not as a third option but as a spectrum, naming three levels: one where predictive is the dominant contributor while adaptive elements reduce specific pain points; one where both contribute significantly; and one where adaptive becomes the major contributor with predictive elements satisfying business constraints. The practical question is therefore not "which of the three?" but "where are we on the spectrum?"

Choosing the approach once for the whole project

The diversity of factors often implies several development approaches may be used within the same project for different deliverables. The guide adds that the various phases can be approached differently, and that a project may be carried out primarily through one approach while subsidiary streams use a different way of working. The approach decision belongs to each deliverable and phase, not to one announcement at the start.

Confusing a method with a tool kit

The Eighth Edition distinguishes a method — a systematic way of doing something, typically involving a series of steps or procedures designed to achieve a specific outcome — from a tool kit — a collection of tools, techniques, and resources supporting various methods, providing flexibility and a range of options to choose from based on context and specific needs. Applying a tool kit as if it were a binding method destroys the flexibility that is its whole reason for existing.

Where It Does Not Apply

Talk of choosing an approach presumes freedom to choose, which is not always available. Organizational capability is a stated constraint: policies, ways of working, reporting structures, and attitudes should all be aligned to employ delivery methods successfully, and the extent to which project management processes are established influences the reliability and predictability of the chosen delivery approach. A fixed functional structure with a directing culture will not be changed by an announcement of agility. A second constraint follows: some adaptive methods call for colocation, and some frameworks recommend between three and nine members — so a project with a large distributed team faces a structural limit that enthusiasm does not resolve. The choice is bounded by what the organization can carry, not by what the manager prefers.