Something strange is happening in boardrooms and engineering all-hands meetings across the industry. The word "agile" — once spoken with near-religious reverence — has become persona non grata. Some companies have quietly banned the term from internal communications. Others are more blunt: "Agile hasn't worked for us."
Back in 2018, the narrative was that agile would "eat the world." It was positioned as the next great organizational transformation, a universal solvent for everything from slow delivery to misaligned strategy. Seven years later, the backlash is in full swing. The "Agile is Dead" movement has real momentum.
But here's the thing: what died wasn't agile. What died was a specific, bloated, overly prescriptive version of agile that was never going to survive contact with organizational reality. The principles are alive and well — they've just matured. And understanding how they matured matters if you're trying to connect strategy to execution in a modern organization.
Five mistakes that gave agile a bad name
Miquel Rodriguez, Head of Business Agility at NetMind, recently shared a candid retrospective on what went wrong with the agile movement. Speaking at Flight Levels Day, he identified five specific mistakes that fueled the backlash — and they're worth examining because most organizations made at least three of them.
Mistake one: focusing on agile adoption rather than solving real problems. The goal became "go agile" rather than "solve this specific organizational problem." When adoption is the objective, you get ceremonies without purpose, roles without authority, and boards without meaning. The question was never "Why are we doing this?" — it was just "Let's go agile."
Mistake two: equating agile with Scrum. Ask many executives whether their organization is agile and the answer is: "Yes, we have Scrum Masters." That's like saying you're healthy because you own a gym membership. Scrum is one implementation pattern. Agile is a way of thinking about work. Collapsing the two created a false sense of progress.
Mistake three: treating agile as a team-level concern. This is perhaps the most consequential error. The first wave of agile optimized teams. Individual squads got faster, but the organization around them didn't change. Work still got stuck between teams, between departments, between strategy and execution. You can have the fastest teams in the world and still deliver the wrong things slowly.
Mistake four: running agile transformations like waterfall projects. Fixed scope, fixed timeline, fixed deliverables. The irony is painful. Organizations adopted an adaptive methodology using the most rigid approach imaginable. "What needs to be done? Deadlines? Tell me how to do it." That's not transformation — it's compliance.
Mistake five: relying on exhaustive frameworks. Frameworks that claim to have all the answers — every role defined, every meeting prescribed, every artifact specified. Rodriguez describes them as a Swiss Army knife: nice because it can do everything, but you wouldn't use one to build a house. These frameworks became the new waterfall, just with different vocabulary.
The pendulum swings
Rodriguez uses a vivid metaphor: organizational trends move like a pendulum. The agile movement swung to one extreme — heavy, prescriptive frameworks that promised comprehensiveness but delivered rigidity. Now the pendulum is swinging back. Some organizations are abandoning structure entirely, reverting to ad hoc decision-making dressed up as "pragmatism."
Neither extreme works. What's needed is something in the middle: lightweight thinking models that help you ask the right questions without prescribing every answer. Not a Swiss Army knife, but the right set of purpose-built tools, used with craftsmanship.
This is the third wave of agile. Not team agility. Not framework agility. Business agility — the ability of an entire organization to sense change, make decisions, and execute strategy coherently across every level.
What business agility actually requires
If agile's first wave was about teams and its second wave was about scaling, the third wave is about connecting strategy to execution with traceability and transparency.
Rodriguez's experience at NetMind illustrates this well. When NetMind was acquired by BTS, a Swedish consultancy, the strategy changed overnight. New business units emerged. Priorities shifted. The leadership team realized they needed a way to make strategy visible and operational — not a static PowerPoint from the January kickoff, but a living system that connected vision to mission to priorities to outcomes to actual initiatives.
The approach they took was rooted in a simple hierarchy: vision flows to strategy, strategy to annual objectives, objectives to quarterly targets, targets to projects, projects to deliverables and tasks. Nothing revolutionary on paper. But the discipline of making this hierarchy explicit — of actually visualizing it, assigning ownership, and creating cadences for review — changed how the organization operated.
What matters isn't the specific framework. What matters is the set of activities that make strategy executable: visualizing the current situation, creating focus on what matters right now, establishing interactions where decisions actually get made, measuring progress, and continuously improving the system itself.
The data backs this up
The "Agile is Dead" narrative is loud, but the numbers tell a different story. Around 95% of organizations now report using agile practices in some form, according to the latest State of Agile surveys. Agile-managed projects still post a 75% success rate compared to roughly 56% for traditional project management. The global market for agile development tools is projected to reach $9.2 billion. Agile isn't disappearing — it's becoming infrastructure.
But here's the more revealing statistic: 84% of those same organizations acknowledge they're still below a high level of agile competency. That's the gap. Near-universal adoption, but widespread immaturity. The problem was never whether organizations would adopt agile. The problem was always what they thought adoption meant.
The shift now happening is from activity-based agility to outcome-driven agility. For years, organizations measured velocity, story points, and ticket throughput — proxies for productivity that said nothing about whether the right work was getting done. The mature version of agile asks a different question: not "how fast are we moving?" but "are we solving the right problems?" That's why OKRs, flow metrics, and strategy alignment are replacing burndown charts as the currency of agile leadership.
And this shift isn't confined to engineering anymore. The 2025 State of Agile report documents agile principles spreading into marketing, HR, operations, and finance — departments that were never part of the original Scrum playbook. When agile escapes the engineering silo and becomes an organizational capability, that's not death. That's maturation.
From methodology to capability
The most useful distinction in this entire debate comes down to a single reframe: agile is not a methodology. It's a capability.
A methodology is something you implement. You pick a framework, assign roles, schedule ceremonies, and declare victory. A capability is something you build over time. It lives in how decisions get made, how information flows, how quickly an organization can change direction when the context shifts.
Dave Thomas, co-author of the Agile Manifesto, was one of the first to publicly declare "Agile is Dead" — but his argument was precisely this point. He wasn't saying the principles had failed. He was saying the industry had turned a set of values into a product to sell: certifications, consulting engagements, and framework licenses that had little to do with actual agility.
The third wave corrects for this. It treats agility as something that spans levels of the organization — not just how teams work, but how strategy connects to execution, how coordination happens between teams, and how leadership creates the conditions for fast, informed decision-making. Rodriguez frames this as applying five core activities (visualize, focus, interact, measure, improve) at every level of the organization, not just within a single squad. That's a fundamentally different proposition than rolling out Scrum to 50 teams and hoping for the best.
The organizations getting this right aren't asking "are we agile?" They're asking "can we see our strategy, trace it to active work, and course-correct when something changes?" That question doesn't require a framework. It requires discipline, transparency, and the right data.
What this means for your organization
Agile isn't dead. But the version of agile that focused exclusively on team-level practices, that confused frameworks with thinking, that treated transformation as a project with a deadline — that version deserved to die.
What's replacing it is more demanding but also more valuable: the discipline of connecting strategy to execution across an entire organization, with real visibility, real cadences, and real accountability. It requires you to answer harder questions: What is our strategy, really? How do our initiatives trace back to it? Where are the gaps between what we said we'd do and what we're actually doing?
The pendulum doesn't have to swing to another extreme. It can settle in the middle — where lightweight thinking meets operational rigor, where 95% adoption meets the competency to actually use it well, where agility stops being a methodology you buy and becomes a capability you build.
That's not the death of agile. That's agile, grown up.