The Framework Wars Are Over
For the better part of two decades, the agile community has argued about frameworks. Scrum versus Kanban. SAFe versus LeSS. Agile versus waterfall. The debates generated heat, conference talks, and tribal identity — but rarely helped organisations deliver better.
In 2026, the debate is over. Not because one side won, but because reality intervened.
The most effective organisations we work with are not "agile organisations" or "waterfall organisations." They are organisations that have figured out how to blend iterative delivery with structured governance in a way that fits their context. That blend is what we call hybrid delivery. If you are mid-transition, our agile consultancy services can help you design the right model.
What Hybrid Delivery Actually Means
Hybrid delivery is not "doing agile badly" or "waterfall with standups." It is a deliberate design choice that recognises a simple truth: different types of work benefit from different approaches.
- A product team iterating on a customer-facing application benefits from short sprints, continuous discovery, and frequent releases.
- A regulatory compliance initiative benefits from defined milestones, formal sign-offs, and documented evidence trails.
- A large-scale transformation programme benefits from both — iterative delivery within workstreams, governed by portfolio-level stage gates.
Hybrid delivery gives you the flexibility to apply the right approach at the right level, rather than forcing a single methodology across fundamentally different types of work.
Why Pure Agile Struggles in Certain Contexts
This is not an anti-agile argument. The principles behind the Agile Manifesto — customer collaboration, responding to change, working software, empowered teams — remain as relevant as they have ever been. But the practical application of those principles sometimes collides with legitimate business requirements:
- Regulated industries: Financial services, healthcare, and defence organisations operate under regulatory frameworks that require documented approvals, audit trails, and stage gates. These are not optional.
- Multi-vendor environments: When multiple suppliers are working to a shared contract, fixed milestones and integration points are essential for coordination.
- Board and investor governance: Executive stakeholders need visibility into progress against committed timelines and budgets. Agile's resistance to upfront commitments creates tension at portfolio level.
- Capital expenditure models: Organisations that budget annually and capitalise development costs need milestone-based reporting structures that map to financial calendars.
The mature response is not to abandon agile. It is to preserve iterative learning inside broader governance structures.
How to Design a Hybrid Model That Works
Effective hybrid models share three characteristics:
1. Agile Inside, Governance Outside
Teams deliver in sprints or iterations internally. They own their process, their backlog, and their daily cadence. But they report progress against portfolio-level milestones that align with organisational governance. The team is agile. The portfolio is governed. Our article on bridging the gap between strategy and execution explores this dynamic in detail.
2. Clear Decision Points
Stage gates in a hybrid model are not approval bureaucracy. They are decision points where the organisation asks: "Given what we now know, should we continue, pivot, or stop?" The difference from traditional stage gates is that the input is working software and validated learning, not a 200-page business case.
3. Adaptive Planning at Every Level
Annual strategic planning sets direction. Quarterly OKRs set focus. Sprint planning sets execution. Each level is progressively more detailed and more adaptable. The annual plan does not change every week, but the sprint plan does.
The Hybrid Maturity Spectrum
Organisations typically move through three stages:
- Stage 1 — Compliance hybrid: "We do agile but still have to fill in the old reports." Teams run sprints while producing waterfall-era documentation. Painful, but common in early transitions.
- Stage 2 — Coordinated hybrid: Agile delivery is embedded in teams, and governance processes have been adapted to accept agile-style inputs. Stage gates use demos and validated outcomes, not sign-off documents.
- Stage 3 — Integrated hybrid: The governance framework and the delivery framework are designed as a unified system. Portfolio management, budgeting, and compliance all operate in cadence with iterative delivery. This is the target state.
Practical Tips for Getting Hybrid Right
- Start with the work, not the framework. Map your portfolio into work types (exploration, execution, compliance, maintenance). Apply the appropriate approach to each.
- Design governance for decisions, not approvals. Every gate should answer a question: continue, pivot, or stop. If the gate only exists to collect signatures, remove it.
- Protect team autonomy. Governance happens at portfolio level. Within their sprint, teams operate with full autonomy over how they deliver.
- Invest in translation. Someone needs to bridge the language gap between agile teams and governance stakeholders. That might be a delivery lead, an agile coach, or a portfolio manager.
Use OKRs as the connective tissue. OKRs work beautifully in hybrid models because they connect strategic direction to quarterly execution without prescribing how teams deliver. Our OKR services are designed to operate within exactly this kind of environment.
The Framework-Agnostic Advantage
At McKenna Agile Consultants, we have always been framework-agnostic. We do not sell a specific methodology. We diagnose the organisation, understand its constraints, and design a delivery approach that fits. If your current transformation has stalled, you might recognise the patterns in our article on why agile transformations fail.
In 2026, that position is not unusual — it is the mainstream. The organisations winning today are those that stopped arguing about frameworks and started designing systems that work. If you are unsure where to start, our agile assessment can help you understand your current maturity and design a practical path forward.
Ready to put this into practice? Book a free 30-minute consultation with McKenna Agile Consultants. No sales pitch — just a conversation about where you are and what would actually help.
