I hear this sentence more and more often.

Usually from people who never really did Scrum, or people who only know it through stories, slides, and hearsay.

In practice, they did something Scrum‑a‑like.
A bit of terminology. A few meetings. Some tickets in a tool.
Just enough to say “we tried.”

What they actually did was Alibi Agile.
Agile to please management.
Agile as a label.
Agile without understanding that you can be agile without Scrum —
and that you can also kill Scrum while keeping all its artifacts.

They wanted the promises:

  • improved time‑to‑market
  • agility (the buzzword, not the behavior)
  • efficiency and productivity
  • transparency

But not the price.

No organizational change.
No shift in decision‑making.
No change in mindset.
And preferably no overhead.

Scrum Was Never Alive There

When people declare that “Scrum is dead”, they are not observing a natural end.
They are issuing a verdict.

Not on a framework, but on its legitimacy.

In doing so, what they are really sentencing is their own failure to create an organizational environment in which Scrum could have been allowed to live.

The so‑called agile transformation ended in a miscarriage.
What remained looked familiar: the names, the roles, the events.
But the conditions were never there.

Some of the same people will go on and declare that “Agile is dead.”
That statement is even more revealing.

Scrum is agile.
Agile is not Scrum.

Declaring both dead at the same time is not insight.
It is a confession.

A Brief Dismissal

Yes, there are cases where Scrum was never the right tool.
That’s not failure.
That’s lack of jurisdiction.

Case dismissed.

Adaptation vs. Opportunism

No, Scrum does not have to be implemented by the book.
Sometimes that is neither possible nor desirable.

Scrum‑a‑like can be fine.

But there is a line — and it is crossed more often than people admit.

There is a difference between adapting Scrum and neutralizing it.

Adaptation asks:
What problem are we trying to solve, and which effect do we need to preserve?

Opportunism asks:
What should we remove, shrink, or replace in order to preserve the existing order?

When you change something — a coaching intervention, a workshop format, a framework — one rule applies, without exception:

Whatever you change, the intended effect must survive the change.

That effect can disappear in three ways:

  • by dropping an element entirely
  • by distorting it until it becomes ritual
  • by replacing it with something that looks similar but serves a different purpose

The outcome is always the same.

The form remains.
The language remains.
The effects are gone.

At that point, Scrum hasn’t been adapted.
It has been rendered harmless.

What follows are not mistakes.
They are reliable patterns.

Dropping Elements — and Losing Their Effects

This is where most “Scrum is dead” stories actually begin.

No Retrospectives

No inspection.
No adaptation.

Expected effect: increased efficiency and productivity
Observed result: nothing

No Backlog Refinement

Vague items.
Inaccurate estimates.
Planning reduced to guesswork.

Expected effect: transparency
Observed result: fiction

Reducing Elements to Rituals

Sprint Planning

Reduced to a PO pushing items into a sprint.

Take it or leave it.

Deadly when combined with missing refinement.

Expected effect: predictability
Observed result: none

Retrospectives

The same three questions.
Every single time.

Or shortened until nothing remains but politeness.

Expected effect: improvement
Observed result: boredom

Replacing Elements with Look‑Alikes

Retro Replaced by Code Review

Code review checks what was built.
Retrospectives inspect how people work together.

Replace one with the other, and collaboration never improves.

Expected effect: efficiency
Observed result: unchanged behavior

Review Replaced by Demo

A demo is optional.
The review is not.

The review compares plan and outcome, updates forecasts, involves stakeholders, and adapts backlog priorities.

Remove that, and the backlog becomes static.

Expected effect: agility
Observed result: status quo

Forgetting the Mindset Part

Some patterns repeat reliably.

QA as a Quality Gate

Develop something.
Throw it over the fence.
Hope it doesn’t come back.

Whether it’s thrown to QA or later to UAT, the pattern is the same: quality is externalized so the team doesn’t have to own it.

Expected effect: faster delivery
Observed result: delays and rework

Two Product Owners

One from IT.
One from business.

Responsibility diluted into a committee.

Expected effect: better decisions
Observed result: slower decisions and political games

Organizational Sabotage

Scrum does not fail gracefully.
It collapses.

What follows are points of structural failure.

  • Product Owners without mandate
  • Product Owners as renamed project managers
  • Product Owners doing the job on top of everything else
  • Status meetings and jour‑fixes that never disappeared

Expected effect: ownership and transparency
Observed result: control and reporting

Command and control was never gone.
Scrum just got in the way for a while.

The Human Consequences

In these setups, the outcome is predictable.

You find:

  • skeptics
  • indifferent people
  • people who genuinely want it to work

The skeptics leave when the alibi becomes annoying.
The motivated leave when they realize nothing will change.

What remains is a system perfectly aligned with itself.

So… Is Scrum Dead?

No.

Scrum is not dead.
It was tolerated, carefully declawed, and eventually discarded.

Not because it failed.
But because it started to interfere.

With opacity.
With unilateral control.
With the comfort of the good old way of working.

Scrum didn’t die.

It simply stopped being useful to the people now celebrating its absence.