Hybrid delivery is a designed operating choice: which work is baselined and changed formally, which work learns in increments, and how those two systems meet without lying to each other.
Name the seams before you name the ceremonies
Typical honest hybrids: a fixed regulatory dossier with an adaptive product behind it; a predictive vendor lead-time with adaptive integration; a fixed launch event with a backlog that can thin. Write the seam in one sentence. If you cannot, you do not have a hybrid. You have two religions sharing a budget.
At the seam, define the artefacts both sides will respect. Perhaps the adaptive team offers a forecast range and a committed increment; the predictive side offers a change-controlled interface and a date. If each side only produces artefacts for its own church, the first delay will become a blame festival.
Governance must be bilingual. A monthly steerco can still exist. It should not demand story-level change requests, and it should not pretend a construction milestone can 'pivot' because a coach said so. Ask for decisions at the right granularity. Everything else is tourism.
Two clocks, one outcome
Predictive work runs on a baseline clock: critical path, float, earned value if you are in that world. Adaptive work runs on a flow clock: increment, review, reorder. The program or project manager's job is to translate. 'The interface is late two weeks on the vendor path; the backlog must drop the dependent slice or we miss the campaign.' That sentence is hybrid management. Two status dialects with no translation is how executives hear noise.
Integration events are sacred. Joint reviews, joint risk, a single definition of what 'ready for the other side' means. Do not let the adaptive team say 'done' when the predictive side cannot consume the output. Done at the seam is done for the other clock, not done for your board.
Risk belongs on both clocks. A vendor slip is a predictive risk with a date trigger. A discovery that the user does not want the feature is an adaptive risk that should stop spend. Putting both only on the Gantt, or only on the board, hides one of them. Hidden risk does not become smaller because your tool cannot display it.
The usual ways hybrid becomes a lie
The Gantt is the real plan and the sprint is decoration. Or the opposite: the backlog is the real plan and the contractual milestones are treated as optional until Legal arrives. Both are accidental hybrids. Someone has to say which commitment is binding.
Staffing a hybrid with people who have only ever done one side, then mocking the other side in Slack, is a People-domain failure with Process symptoms. Pair them. Translate. If you need a specialist to run the compliance clock, hire one. Do not ask a Scrum Master to invent a dossier by instinct.
When the stem offers 'pick one method for the whole programme,' check whether the work is actually uniform. If it is not, the best next action is to tailor by work type and explain the seam to the sponsor — not to force a purity that will be smuggled around by Tuesday.
Summary & next steps
Design the seam, translate the two clocks, and define done for the other side. Accidental hybrid is two methods in a trench coat. Deliberate hybrid is a sentence the sponsor can repeat.
Next: stakeholder dilemmas — competing interests, ethics, and the next action when every option disappoints someone with a title.