Agile didn't die. It dissolved. (And that's why your career feels weird.)

Here's the thesis this post stands on. Agile didn't die. It dissolved. The methodology label faded because the ideas won. They got absorbed into how good organisations work, which is exactly the outcome the original Manifesto authors hoped for. And that absorption is the real reason your job title keeps changing, your team keeps being renamed, and your résumé feels weird every two years.

"Is agile dead?" is the wrong question

It's a comforting question to ask. If agile is dead, we can move on. We can adopt the next thing (post-agile, product operating model, outcome teams, whatever the deck says this quarter) and feel like we're ahead of the curve. The death of agile is, paradoxically, a way to stay where we are.

The honest framing is harder. Agile didn't die. It diffused into the bloodstream so thoroughly that you can't see it anymore. Take iterative development. Twenty years ago it was a Scrum team's signature move; today it's how every modern software product is built. Daily standups aren't an agile ceremony anymore. They're how most knowledge work is coordinated, including in HR and finance departments that have never read the Manifesto. Cross-functional teams used to be a Scrum prescription. Now they're the default org design at any company younger than 20 years, and the underlying mechanics (alignment, working agreements, decision rights) are treated as table-stakes design questions in places that never used a sprint board.

This is what success looks like for any methodology that becomes infrastructure. Object-oriented programming, the relational database, the design system: each won by getting absorbed past the point of being remarkable. Nobody declares "OO is dead" while typing class for the eighth time today. You only get to declare a thing dead when it stays vivid enough to be killable.

The four ways it dissolved

If you squint at the last decade of agile, the absorption ran along four paths in parallel. We've watched these play out across dozens of transformations:

1. It got woven in

   Agile values stopped being a methodology you adopt and became part of how organisations describe themselves. "We're customer-obsessed." "We ship in small batches." "We don't punish failed experiments." These are agile sentences. Companies say them now without knowing they're saying them, and that's the win.

2. It hardened around what worked

   The framework hardened around the parts that survived. Scrum events that didn't pull their weight in real teams got quietly dropped. Estimation rituals that produced theatre instead of forecasts got replaced by flow metrics. The Manifesto's twelve principles aged better than the practices people built on top of them. That's also exactly how an enduring idea is supposed to behave.

3. It spread sideways into departments that never ran a sprint

   Agile is now present in departments that have never seen a sprint board. Hospital administration. Bank compliance. Diplomatic missions. School district leadership teams. We've run working-agreements sessions for groups whose own job descriptions include the words "non-agile." They apply the same moves a Scrum team would, just under different names. It's what alignment under uncertainty looks like, regardless of what you call the people doing it.

4. It started borrowing again

   Adjacent disciplines are now feeding agile back ideas faster than agile is feeding them out. Vertical leadership development. Polarity management. Relationship-systems coaching. AI-augmented product work. Each of these came from somewhere else, met the agile community, and became part of the practice. The agile mind is now a borrowing mind. That's exactly the mind it always claimed to be.

Why your career feels weird

So we agree agile is dissolved, not dead. Why does that make your career feel weird?

Because the labels you've been collecting (Scrum Master, Agile Coach, Release Train Engineer, Iteration Manager) were the labels of an identifiable methodology. When the methodology became invisible, the labels stopped being navigation aids. They're still real jobs and they still pay, but they no longer locate you in a clear professional landscape. The compass needle spins.

The macro numbers behind this aren't comforting. The average working person now changes jobs twelve times over a career and undergoes four to seven full career shifts. Not job changes; career changes. Those weren't the numbers when most current Scrum Masters first qualified. Half of those job changes will be inside the same company, between groups whose names didn't exist five years ago.

The Red Queen is the right metaphor for an agile career right now. The terrain is moving under your feet. Staying in place (keeping the same job title, the same scope, the same shape of credibility) requires more learning than it ever has before. Not because you're falling behind. Because the floor is rising.

The Agile Career Skills Wheel

A tool helps here. We've been running students through a self-assessment called the Agile Career Skills Wheel for two years. Ten spokes. Three rings of evidence per spoke: Learning, Applying, Guiding. The exercise takes about twelve minutes. The awkward pause is included, the one where you realise you're a zero on a spoke you assumed you'd score a one or two on.

What the wheel surfaces is unusually honest. Most senior practitioners we've handed it to score between twelve and eighteen out of thirty, despite identifying as "experienced." The pattern of the score matters more than the number: most of us are deep on two spokes, mid on three, and quietly zero on five. The career edge isn't getting your strong spokes from a two to a three. It's pulling one of your zeros up to a one.

The reason this matters in a dissolved-agile career is that the spokes you're zero on are usually the spokes the next role wants. Not your current role. The role one move ahead, the one the dissolved landscape is producing. Data fluency. Business fluency. Domain depth in an industry you don't currently work in. People-and-change leadership at a scale beyond your current team. The market quietly stopped paying for a perfect Scrum Master and started paying for a competent something-else.

What to do this week

There are a hundred ways to react to a dissolving methodology. You can declare it dead and pivot tone. You can keep the badge and run faster on the same treadmill. You can refuse to update and let the floor rise past you. None of those are good moves. The move we keep coming back to (for ourselves, for students, for clients who pay us specifically not to bullshit them) is the one Scrum has always recommended. Assess. Find the gap that pays back the most. Take the smallest concrete next step on it. Don't try to fix everything at once.

Agile didn't die. It dissolved. The career it created is dissolving with it, into something larger and stranger. We don't know exactly what's next. Anyone who tells you they do is selling you their version of it. But we know the move that puts you in shape to find out. Identify your zero. Take your five minutes. Then take the next five. The coaching mindset Brock writes about is the same posture pointed at your own career: curious, neutral, willing to be wrong about yourself. That's the running speed the Red Queen meant.

If the spokes you scored highest on are People & change, you might also like our Effortless Leadership programme, which is built around the same vertical-development thinking. And if you're nodding along but unsure where the next step lives, write back. Replies to the welcome email reach Erkan and Brock directly.