Javier Castro

Posted on Nov 3

Hybrid Agile Is Already Winning. That Doesn't Mean Teams Are Doing It Right.

#agileframeworkspractice

Most organizations have stopped arguing about agile versus waterfall. The problem is the truce they've negotiated is making both sides worse.

The meeting that crystallized the problem for a lot of delivery leads happened sometime around 2022, in an enterprise program room that smelled of catered sandwiches and mild institutional dread. On one wall: a burndown chart. On the other: a Gantt chart that stretched so far into the future it required scrolling. Both were accurate. Neither was informing any actual decision. The Scrum team was iterating. The governance board was gating. Nobody in the room was sure whether those two activities were connected in any meaningful way.

This is where the hybrid delivery model has landed at scale — not as a thoughtful synthesis of two philosophies, but as a kind of methodological détente. Burn velocity on one screen, RAID log on the other, and a program manager somewhere in the middle manually translating between them.

The Numbers Don't Lie, But They're Being Generous

According to the 18th State of Agile Report, 74% of organizations now say they use hybrid or homegrown delivery models — a number that deserves some skepticism, because "hybrid" is doing a lot of heavy lifting as a term. It covers everything from genuinely sophisticated blended frameworks to what are essentially waterfall projects with daily standups bolted on.

As one trend observer from the 17th State of Agile noted, more and more organizations are claiming a hybrid approach — not sticking to one framework — particularly in heavily regulated industries where rules require working around certain constraints.

The academic literature is equally candid about why this happened. Agile's neglect of documentation and its challenges in managing physical product iterations hindered long-term maintenance and compliance, driving the need for hybrid models. Risks like "difficulty in adjusting schedules to customer timelines" and "imperfect sprint planning" revealed gaps in pure agile frameworks — gaps that hybrid methodologies emerged to fill by combining agile's flexibility with traditional methods' predictability.

Fair enough. Nobody serious is arguing that a pharmaceutical firm should run two-week sprints on regulatory submissions, or that an aerospace contractor should treat DO-178C certification evidence as optional. Integrating agile methods into safety-critical aerospace development presents substantial challenges: strict compliance requirements like DO-178C demand documentation, traceability, and comprehensive verification activities that pure Scrum simply doesn't account for. The regulated world genuinely needs structure that pure Scrum does not natively provide.

But the claim worth sitting with is this: the hybrid model hasn't failed because it's conceptually wrong — it's failing because most organizations are using it as permission to do nothing particularly well. They've kept the governance overhead of waterfall and discarded the discipline, while adopting the ceremonies of agile and discarding the empiricism.

The Architecture of a Comfortable Compromise

Water-Scrum-Fall — one of the most common hybrid patterns — segments projects into planning using waterfall, iterative development through Scrum, and delivery through waterfall phases, retaining flexibility while adding structure. In theory, that's a reasonable arrangement. In practice, it usually produces the worst of both: fixed scope decided upfront by people who haven't talked to users, executed in sprints that feel adaptive but can't actually change direction, then shipped through a release process governed by an enterprise release board that meets quarterly.

Forrester documented this pattern over a decade ago and gave it the name that stuck. Agile adoption frequently diverged from the original Agile Manifesto because it was practitioner-led — practitioners focused on the domain they knew best, software development, while release management and project planning stayed firmly in waterfall territory.

That observation has aged impeccably. The sprint ceremonies moved into development teams. The governance artifacts stayed with the PMO. And the connective tissue between them — the bit that was supposed to make the whole thing coherent — never quite materialized. Research examining real-life Water-Scrum-Fall implementations in large enterprises found that modified agile methodologies are used but their benefits are not fully unlocked: hybrid approaches still require rigorous upfront analysis that strongly limits agility in subsequent phases, and customer feedback loops are frequently omitted entirely.

When Hybrid Actually Works

The counterargument — and it's a real one — is that for certain organizations, getting both methodologies to coexist at all is a legitimate achievement.

Halliburton, for example, implemented an agile-based process for software development while still allowing projects to comply with the corporate standard waterfall process framework — mapping agile into the existing waterfall structure, adjusting the framework to allow agility, and extracting real value from the approach. That's not a small thing inside a company with the regulatory and procurement complexity that comes with being a major oilfield services provider. Sometimes the win is just getting agile ceremonies recognized as a legitimate delivery method within an otherwise rigid system.

Agile transformations go "at risk" when parts of the organization that aren't ready to transition are forced to do so prematurely. Organizations need to plan an orderly transition by allowing both methodologies to coexist for a period of time. This is the sensible, practitioners'-eye view: pragmatism over ideological purity, especially when the alternative is blowing up a compliance-dependent delivery process that actual regulators will scrutinize.

Success in hybrid methodologies hinges on leadership support, tailored process integration, and continuous improvement mechanisms. The emphasis on tailored matters. Off-the-shelf SAFe layered onto a team that has never done a real retrospective is not a hybrid model. It's a bureaucratic expansion of something that was already struggling.

Frameworks like SAFe, LeSS, and Disciplined Agile Delivery reintroduce management layers for portfolio governance, program increment planning, and compliance auditing. Industries such as finance, healthcare, and aerospace operate under compliance frameworks that may fundamentally alter the feasibility of pure self-management. You cannot Scrum your way through an FDA audit. Something has to give, and what gives is usually some agile purist's insistence on no documentation outside the working software.

The Problem No One Wants to Name Out Loud

Here's where things get uncomfortable: a lot of what gets called "hybrid" is really just organizational inertia wearing progressive clothing.

Enterprises commonly use home-grown frameworks or something inspired by an industry-standard framework, while some still have traditional PMO teams operating like it's 2005. Org-wide agile mandates don't reliably produce business impact, so teams are left to deliver in a discordant manner because of the underlying system complexity.

That discordance has a cost that rarely shows up on sprint velocity metrics. When the governance layer and the delivery layer are operating on different cadences, with different vocabularies and different definitions of "done," the integration cost falls on individual contributors. A tech lead who spends two days per sprint updating a status report in a format the PMO can process is doing hybrid integration work that no framework accounts for. It just appears as reduced team capacity.

Most organisations have responded to the gap between management and agile by staying with plan-driven waterfall and hybrid approaches that have a track record of going well over budget while delivering much less value than predicted. The evidence suggests that slapping agile ceremonies onto a waterfall structure isn't closing the performance gap — it's creating a more complicated failure mode, one with both a burndown chart and a variance report to misread.

Performance and scalability issues are key drivers of agile's evolution, as these methodologies struggle at enterprise levels. Frameworks like SAFe and LeSS were developed to address scalability, but they introduced complexity and rigidity that counteract agile's flexibility. This is the structural irony at the center of the hybrid conversation: the frameworks built to make agile work at scale have, in many implementations, simply recreated the planning overhead they were supposed to replace.

What Good Hybrid Looks Like (And Why It's Rare)

Hybrid models that work integrate agile's iterations with plan-driven documentation to ensure regulatory adherence without sacrificing agility — particularly when combined with DevOps practices for continuous compliance. Hybrid models like MAHD enforce iterative validation cycles and modular design to meet regulatory standards without sacrificing agility.

The operative phrase is "without sacrificing agility." Not "agility minus the governance overhead" or "governance plus some standups." The real hybrid practitioner knows exactly which constraints are non-negotiable — a regulatory gate, an audit artifact, a fixed external release date — and protects genuine adaptability in everything else. The sprint backlog actually changes based on learning. The compliance checkpoint is automated where possible. The program increment isn't just renamed "waterfall planning with a PI ceremony."

Recent systematic research finds that hybrid methodologies represent a mature evolution rather than a transitional phase, validated by their effectiveness in achieving stakeholder success comparable to pure agile. That's genuinely encouraging, but the emphasis belongs on "mature" — it implies that early-stage, poorly implemented hybrid doesn't reach that bar.

Poor implementations often accompany unpreparedness by companies to fully adopt agile and the absence of senior roles like Scrum Masters who could educate teams and organizations in proper agile practices. The hybrid model rewards expertise and punishes improvisation, which is somewhat the opposite of how most organizations have treated the adoption decision.

The Truce That Nobody Signed

The uncomfortable truth about the hybrid delivery model is that it became the default not because organizations resolved the tension between adaptability and control, but because they got tired of having the argument. Hybrid is the peace treaty that allowed the transformation budget to be spent, the framework consultants to be paid, and the leadership deck to say "agile" without the IT department getting too anxious.

That's not inherently cynical — avoiding a culture war has genuine value, and coexistence between methodologies is sometimes the most honest reflection of where an organization actually is. But the truce has a price: it lets mediocre implementations hide behind a label that implies sophistication.

A team running two-week sprints inside a six-month waterfall phase, updating a RAID log nobody reads, with customer feedback arriving once at the end — that's not a hybrid model. That's a waterfall project that bought some Jira licenses.

The organizations getting genuine value from hybrid delivery are the ones who made explicit, uncomfortable decisions about which constraints are real and which are just habit. Everything else is just methodology branding.

DEV Community