Predictive, adaptive and hybrid delivery

Construction people hear “agile” and think of software teams with sticky notes. The PMBOK® Guide – Eighth Edition from PMI® takes a calmer view. It treats predictive, adaptive and hybrid as three ways to develop a project's outputs, and expects you to choose among them on purpose. This lesson explains each approach, the factors that drive the choice and the idea of delivery cadence. Then it shows why Northgate Distribution Centre, our fictional warehouse in Vaughan, is a hybrid project even though it runs on a stipulated price contract.

Learning outcomes

• Explain the difference between a project life cycle, a development approach and a construction delivery method.
• Describe predictive, adaptive and hybrid approaches, and say what kind of work each one suits.
• Use three questions about scope clarity, cost of change and need for feedback to choose an approach for a work package.
• Recognize the four delivery cadences and spot which ones a construction project actually uses.

The lesson

Three terms people mix up

Before comparing approaches, separate three ideas that often get blended in OAC meetings.

• Project life cycle. The series of phases a project passes through from start to close. On a building that might be business case, design, tender, construction, commissioning and closeout. PMBOK 8 treats the life cycle as the frame that holds everything else.
• Development approach. How the team produces and refines the deliverables within that life cycle: plan it all first (predictive), learn and adjust in short cycles (adaptive), or a mix (hybrid). This is the subject of this lesson.
• Construction delivery method. How the owner contracts for design and construction: design-bid-build, construction management, design-build and so on. The Contracts track, lesson 3, covers these. A delivery method is a contracting decision. It does not settle the development approach by itself.

The distinction matters. Northgate is design-bid-build under CCDC 2-2020. That is a fixed contracting decision. Inside it, the owner still decides how each piece of work is planned and controlled.

Predictive: plan it, then build it

A predictive approach fixes scope, schedule and cost early and then manages against that baseline. Change is possible but goes through formal change control. It works when requirements are well understood, when the cost of changing your mind late is high and when outside parties such as lenders, regulators and contractors need firm commitments.

Most of a tilt-up warehouse fits that description. You cannot iterate a slab-on-grade. Once the panels are cast and lifted, a layout change costs real money and time. The building permit, the stipulated price and the contractor's baseline schedule all assume the design is settled. Predictive is not old-fashioned here. It is the right tool.

Adaptive: learn in short cycles

An adaptive approach accepts that the requirements are not fully known at the start. The team works in short cycles, shows the result, gets feedback and adjusts. Scope is held in a prioritized list (a backlog) that changes as people learn. Agile frameworks such as Scrum and Kanban are the best-known examples. Adaptive approaches come in two flavours that are often combined: iterative (refine the same thing through repeated versions) and incremental (add usable pieces one at a time).

Adaptive work suits problems where feedback is cheap and changes are inexpensive: software, a new service, a layout still being worked out with the people who will use it.

Hybrid: fix what you know, iterate the rest

A hybrid approach mixes the two within one project. The mix can be by phase, for example adaptive concept design followed by predictive construction. It can be by work package, with a predictive building and an adaptive owner fit-out. Or it can be by layer: a predictive master schedule with adaptive short-interval planning underneath. PMBOK 8 treats hybrid as a normal, deliberate choice, not a compromise.

Construction has been hybrid for a long time without calling it that. A contractor's baseline is predictive. The weekly work plan and the three-week lookahead are adaptive. Lean construction's Last Planner® System makes this explicit. It links milestone and pull planning to the master schedule, then has the crews make weekly commitments and learn from the reasons work slipped.

Choosing an approach

PMBOK 8 groups the selection factors under three headings: the deliverables, the project and the organization. On a construction job, BRC boils them down to three questions you can ask of each work package.

1. How clear is the scope? If you can draw it and price it today, lean predictive.
2. What does a late change cost? If changing it after the fact means demolition, re-permitting or a claim, lean predictive.
3. How much do you need feedback from users? If the right answer only appears when operators, tenants or commissioning agents react to something real, lean adaptive.

Organizational factors then move the answer. A public owner with strict approval gates, a lender's draw schedule or a board that meets quarterly will pull more of the project toward predictive control. A team with easy access to decision makers can run more of the work adaptively.

Delivery cadence

Cadence is how often the project hands over something usable. The PMBOK 8 literature names four patterns: single, multiple, periodic and continuous.

Cadence and approach are related but not the same. A predictive project can deliver in several pieces, as a phased hospital or a multi-building campus does. An adaptive team can still be bound to a single final handover. Construction contracts usually set a single or multiple delivery for the main work. The periodic rhythm lives in the owner's and contractor's internal work.

Northgate worked example

Northgate Distribution Centre (fictional) is a 12,000 m² tilt-up warehouse with a 900 m² office mezzanine, delivered design-bid-build under a CCDC 2-2020 stipulated price contract with Halvorsen Builders Ltd. (fictional) for $34,950,000. The issued-for-construction set went out on January 29, 2027. Halvorsen's baseline schedule is due February 10, 2027 and it mobilizes on March 1. Ready-for-Takeover is targeted for January 14, 2028. Northgate's own racking contractor starts on January 17, 2028.

The Owner's PM applies the three questions to five work packages. The ratings are BRC's judgement for teaching, not a PMI scoring method.

The shell, slab, structure and MEP systems are fixed by the IFC drawings and priced in the Contract Price. They are predictive, controlled through the baseline and the change order process. Three pockets need learning:

• Weekly site sequencing. Halvorsen plans the next three weeks with its trades and commits to a weekly plan. The owner doesn't run this, but should ask to see it, because it is the earliest warning of slippage.
• Owner racking layout. Northgate's operations team is still working out aisle widths, pick zones and the dock-door assignment with its racking supplier. That work runs in two-week review cycles. It can't run open-ended. The layout has to be frozen by July 30, 2027 so it can be checked against the ESFR sprinkler design, the slab anchoring and the dock equipment before those are built.
• Commissioning issue closeout. From commissioning start on November 1, 2027, open issues are worked in weekly cycles: test, log, fix, retest. The list is reprioritized each week by what blocks Ready-for-Takeover.

The point of Figure 4 is the relationship between the two colours. Every orange pocket sits inside blue dates it cannot move. The racking freeze is set by the sprinkler and slab work. Commissioning cycles have to close enough issues to reach Ready-for-Takeover on January 14, 2028. Adaptive doesn't mean undated.

Owner's move

• Name the approach for each major work package in the owner's project management plan. One line each: predictive, adaptive or hybrid, and why.
• Set a freeze date for every adaptive pocket that feeds the contractor's work, and put it in the owner's master schedule as a milestone. Unfrozen owner decisions are a common source of delay claims.
• Ask for the contractor's lookahead as well as the monthly update. The baseline tells you where you should be. The weekly plan tells you whether the next month is ready to happen.
• Keep the contract predictive. Don't try to make a stipulated price contract “agile” by leaving scope open. If the scope is still moving, finish learning first or choose a different contract model.
• Report the two layers differently. Report the spine as variance against the baseline. Report the pockets by decisions closed against the freeze date.

Common mistakes

1. Confusing delivery method with development approach. “We're design-build, so we're agile” mixes a contracting choice with a planning choice.
2. Thinking hybrid means half-and-half. Most building projects are mostly predictive with a few adaptive pockets. The mix should follow the work, not a target ratio.
3. Running adaptive pockets with no end date. Owner iteration that drifts past the date the contractor needs the answer becomes a change, and often a claim.
4. Calling the lookahead “the schedule”. Short-interval plans have to roll up to the baseline logic. If they don't, you have two schedules and no control.
5. Assuming PMBOK 8 prefers adaptive. It doesn't. It expects a reasoned choice, and on most of a warehouse the reasoned choice is predictive.

Quick quiz

1. Northgate uses design-bid-build under CCDC 2-2020. What does that tell you about its development approach?

   1. It must be fully predictive.
   2. It must be adaptive, because the design is done.
   3. Nothing on its own; delivery method is a contracting decision and the approach is chosen separately.
   4. It must be hybrid.

2. Which work package is the best candidate for an adaptive approach?

   1. Tilt-up wall panels
   2. Slab-on-grade
   3. An owner layout that depends on operators reacting to options
   4. The ESFR sprinkler main

3. Halvorsen hands over the building once, at Ready-for-Takeover. Which delivery cadence is that?

   1. Single
   2. Multiple
   3. Periodic
   4. Continuous

4. What is the main control an owner should put on an adaptive pocket that feeds the contractor's work?

   1. A daily stand-up
   2. A freeze date tied to the contractor's schedule
   3. A separate stipulated price
   4. Removing it from the master schedule

5. Under which three headings does PMBOK 8 group the considerations for choosing a development approach?

   1. Cost, time and quality
   2. Deliverables, project and organization
   3. Initiating, Planning and Executing
   4. Scope, Schedule and Risk

Key terms

Project life cycle

The series of phases a project passes through from start to close.

Development approach

The way deliverables are produced and refined within the life cycle: predictive, adaptive or hybrid.

Predictive approach

Scope, schedule and cost are fixed early and managed against a baseline, with formal change control.

Adaptive approach

Work proceeds in short cycles with frequent feedback. Scope is held in a backlog that is reprioritized as the team learns.

Hybrid approach

A deliberate mix of predictive and adaptive elements, by phase, by work package or by planning layer.

Delivery cadence

How often usable outputs are handed over: single, multiple, periodic or continuous.

Freeze date

The date by which an adaptive decision must be fixed so that dependent predictive work can proceed. This is BRC's working term, not a PMBOK term.

Construction delivery method

The way an owner contracts for design and construction, such as design-bid-build or design-build. It is separate from the development approach.

References

1. Project Management Institute. PMBOK® Guide – Eighth Edition and The Standard for Project Management (November 2025, 408 pages; tailoring practices to context).
2. PMI, via O'Reilly Learning. Project life cycle section, table of contents and overview (phases; predictive, adaptive and hybrid approaches; selection considerations for deliverables, project and organization; delivery cadence).
3. PMExams. PMBOK 8 Delivery Cadence Options (single, multiple, periodic and continuous delivery). Independent study guide, not PMI.
4. ITU Online. Understanding Agile and Hybrid Approaches in PMBOK 8 (hybrid combinations and selection factors).
5. Ricardo Vargas. Mastering Delivery Cadence: Choosing the Right Rhythm for Your Project (multiple delivery common in construction and capital projects).
6. Lean Construction Institute. The Last Planner System: From Pull Planning to Weekly Work Planning (milestone and pull planning, make-ready, weekly commitments, learning from variance).

Verified on November 4, 2026.