Hybrid Project Management in a Programme: Fix the Controls First
Hybrid project management mixes practices from more than one approach inside one project.
By Sanjeev Kumar, Founder · Updated 18 Nov 2026

Key takeaways
- Hybrid project management mixes practices from more than one approach inside one project. At programme level, hold benefit dates, gates, funding and the RAID log (risks, assumptions, issues, dependencies) fixed and let each component choose its own approach.
- PMI's Pulse of the Profession 2024 reports the share of respondents using hybrid approaches always or often rising from 20% in 2020 to 31.5% in 2023, with project performance only marginally different across predictive, hybrid and agile approaches.
- In a 477-project study, budget, schedule and scope results were similar across approaches. Agile and hybrid projects scored higher than traditional ones on stakeholder success.
- Answer six yes/no questions for each component; five count towards the reading and the sixth sets the handover rule. Then record the approach in the programme management plan.
In this article
- 1What is hybrid project management, and what does it mean in a programme?
- 2Which hybrid patterns do programmes use?
- 3Does the approach you choose change project results?
- 4Which programme controls stay fixed whatever approach a component uses?
- 5What goes wrong when components run different approaches?
- 6How do you choose an approach for each component?
- 7Six questions to ask for each component
- 8Worked example: three components
- 9Which Augment Consultancy course gives a foundation for programme controls?
- 10Where should you start in your programme?
- 11Frequently asked questions
The harder half sits above the teams: the dates, gates and funding that must mean the same thing to every component, whatever method it runs.
This page is for programme, portfolio and PMO (project management office) leads who already know agile and predictive (plan-first) delivery and now have both inside one programme. It sets out what the evidence says about whether the choice of approach matters, which controls to hold fixed whatever approach each component uses, and a six-question sheet for choosing an approach component by component.
The evidence we cite measures projects, not programmes, so we mark where it stops and where our own recommendation begins.
Definition
What is hybrid project management, and what does it mean in a programme?
Hybrid project management combines practices from more than one delivery approach in a single project. In the PMJ Practitioner Insights summary of the study by Gemino, Horner Reich and Serrador (Project Management Journal, 2021), the example is a work breakdown structure (WBS, the deliverables broken into work packages) and a risk register used alongside stand-ups and sprints. The definition does not mention the order of phases. (PMI Practitioner Insights, 2022)
In a programme, “hybrid” usually means something wider: components (projects or teams) run on different approaches under one set of controls. As our guide to programme management methodologies sets out, a delivery approach is how a component is built, not how the programme is governed. “Hybrid” can also mean office and remote working, which this post does not cover.
Which hybrid patterns do programmes use?
These descriptions are our shorthand for the common patterns. Water-Scrum-Fall plans and approves the work in a waterfall style, builds in Scrum sprints, then releases through a waterfall-style deployment. Agile-Stage-Gate keeps stage gates for approval and funding decisions and runs sprints inside each stage. Both are ways of arranging the same practices. Neither is required for a programme to count as hybrid.
Does the approach you choose change project results?
Not on budget, schedule or scope. Stakeholder satisfaction is where the approaches differ, and the evidence behind both points comes from projects, not programmes.
Two PMI sources bear on this:
- PMI's Pulse of the Profession 2024 reports that hybrid use rose from 20% of respondents in 2020 to 31.5% in 2023, counting those using it always or often. The same report finds that project teams using predictive, hybrid and agile approaches show comparable performance. (PMI, Pulse of the Profession 2024)
- A cross-industry study of 477 projects, reported by experienced project managers, found that 52% used hybrid approaches, 33% traditional and 15% agile. All three delivered similar budget, schedule and scope/quality results. (PMI Practitioner Insights, 2022; the 52% figure is also reported in PMI, Pulse of the Profession 2024, p. 12)
On stakeholder success, which the 477-project study measured as the average of sponsor, client and team satisfaction, agile and hybrid projects scored significantly higher than traditional ones. That is satisfaction, not benefits realised, so it is a signal and not proof of benefit delivery.
Both sources measure projects. Neither reports programme-level results. Our recommendation follows from that: if the method does not decide the triple-constraint outcome (budget, schedule, scope), a programme gains more from fixing the controls that sit above the methods than from standardising the methods.
According to PMI’s Pulse of the Profession 2024, the average project success rate across all respondents was 73.8%, a measure based on respondents’ self-reported achievement of business goals for a project. The same report finds the rate varies only marginally across predictive, agile and hybrid approaches.

Which programme controls stay fixed whatever approach a component uses?
Five controls stay fixed: benefit dates, gate decisions, funding release, one RAID log and a recorded approach choice. Each component reports against them, however it plans its own work. This is our recommendation for programmes, not a finding from PMI's Pulse of the Profession 2024 or the 477-project study.
- Benefit dates: sequencing components by the date their benefit is due gives sprint-based and plan-based components the same clock.
- Gate decisions: who decides at each gate stays the same for every component, because the gate is a programme decision, not a team ritual.
- Funding: releasing funds against gates keeps spending tied to the same decision points whichever approach produced the work.
- Risk tracking: one RAID log across all components stops a dependency or risk disappearing at the boundary between two approaches.
- Approach choice: recording each component's approach in the programme management plan makes the choice visible and reviewable.
What goes wrong when components run different approaches?
The risk sits at the joins between components, and four joins need a check. These four checks are our recommendation for programmes, not a finding from PMI's Pulse of the Profession 2024 or the 477-project study.
- Status in different units: a sprint-based component may report velocity (work completed per sprint) while a plan-based one reports per cent complete, so the programme board cannot compare them. Ask both to report against the next gate and the next benefit date.
- Dependency dates: a predictive component may need a fixed date for an output that an agile component plans only a few sprints ahead. Record the dependency in the RAID log with a date both component leads have agreed, and review it at every gate.
- Funding logic: where one component is funded for capacity over time and another for a defined scope, release both at the same gates so neither escapes the programme's spending decisions.
- Handover: the team that will run the output may not be ready to receive it in increments. Question 6 in the sheet below tests for this.
How do you choose an approach for each component?
Score each component at its next gate. Questions 1 to 5 give predictive and agile signals: count them and read the result from the table below. Question 6 does not score; it decides how handover works. The sheet is our own recommendation. The questions and the three-component dependency threshold in question 4 are our judgement, not a validated instrument, so treat a borderline score as a prompt for discussion.
Six questions to ask for each component
Answer each question yes or no. A pass means the answer is yes under the stated test.
- Scope fixed?Can the scope be written as a list that the sponsor and the delivery team can both sign today, without expecting material change? Yes means a signed list exists. (Predictive signal)
- Hard external date?Does a contract, regulator or customer commitment set a date the component cannot miss? Yes means the date is written in the contract or regulation. (Predictive signal)
- Feedback steers scope?Must users or the client see working output before the scope is final? Yes means a review of working output is planned before scope is fixed. (Agile signal)
- Heavy dependencies?Do three or more other components wait on this component's outputs? The threshold of three is our own. (Predictive signal)
- Usable increments?Can a user use part of the output before all of it is finished? Yes means a named user group can use the first part. (Agile signal)
- Receiving team joins planning?Has the team that will run the output agreed to take part in planning reviews every cycle? Yes means the agreement is written down. This one does not count towards the score.

| Predictive signals (yes on 1, 2, 4) | Agile signals (yes on 3, 5) | Reading |
|---|---|---|
| 2 or 3 | 0 or 1 | Predictive |
| 0 or 1 | 1 or 2 | Agile |
| 2 or 3 | 2 | Hybrid: name which practices stay fixed and which iterate |
| 0 or 1 | 0 | Hybrid: name which practices stay fixed and which iterate |
If the answer to question 6 is no, treat handover as a dated gate, whatever the reading, because the receiving team has not agreed to iterate with you.
Worked example: three components
This example is illustrative. The components are invented to show the arithmetic and are not a real programme.
| Component | Q1 | Q2 | Q3 | Q4 | Q5 | Q6 | Predictive signals | Agile signals | Reading |
|---|---|---|---|---|---|---|---|---|---|
| Data migration for a regulatory filing | Yes | Yes | No | Yes | No | Yes | 3 | 0 | Predictive |
| Customer-facing app | No | No | Yes | No | Yes | Yes | 0 | 2 | Agile |
| Compliance training rollout to field offices | No | Yes | Yes | Yes | Yes | No | 2 | 2 | Hybrid, with handover as a dated gate |
All three components report to the same benefit dates, the same gates, the same funding release points and one RAID log. The training rollout is the hybrid case: a regulator sets the date by which field staff must be trained, and three other components wait on trained staff, so the date and the dependencies stay fixed. Its content is not signed yet, because pilot sessions shape the material, and offices can use the first wave of training before the rest is finished. The receiving teams have not agreed to iterate, so the final handover is a dated gate. The programme management plan records all three readings.
Which Augment Consultancy course gives a foundation for programme controls?
Program Management Essentials is our foundation course for project managers, programme managers and professionals overseeing multiple initiatives. It runs for 12 weeks across 10 modules, including risk management, stakeholder engagement, benefits planning and strategic alignment, with monthly live question-and-answer sessions. It is a foundation course, not PgMP® exam preparation.
If you are pursuing the PgMP® (Program Management Professional) or PfMP® (Portfolio Management Professional) credential from the Project Management Institute (PMI), we offer self-paced programmes, Fast Track group mentoring programmes and application writing support for each. More than 6,000 professionals have been mentored or trained by us.
You can see every programme in our course store.
Where should you start in your programme?
If your programme already runs agile and predictive components side by side, do not start by changing how the teams work. Start with the five controls. Check that every component reports against the same benefit dates, the same gate decisions and the same funding release points, and that its risks and dependencies sit in one RAID log. Where a control is missing, fix it first, because a gap there affects every component at once, whatever method it uses.
Then score each component with the six questions at its next gate rather than all at once. Treat a borderline result as a prompt to talk with the sponsor, not a verdict, and give any component without a written agreement from its receiving team a dated handover gate.
For a structured grounding in benefits planning, gates and programme risk, explore Program Management Essentials, our foundation course for professionals overseeing multiple initiatives.
Frequently asked questions
We recommend the programme manager proposes the approach and the sponsor approves it, recorded in the programme management plan. Who decides what once agile teams are running is covered in our page on who decides what across agile teams.



