The backstory.

Agile was built for organizations. Organizations are made of humans. Agile Fragile is where I write that down as the Human Agile™ model. I am Anjish Bhondwe.

What I have seen

People are the least trained, least attended, and least protected part of enterprise agile adoption.

Across coaching, implementation, and scaling work at enterprise level, the same pattern kept landing. Agility performed on dashboards for leadership. The rollout looked green. People were breaking. Nobody said it in the programme review. I mapped the budget numbers on the home page and the human strain on the leaders page.

Pressure

Speed, competition, budgets

Leadership pressure turns agile into an instrument. Roll out faster. Show progress sooner. Hit the milestone. The human cost is treated as resistance, not signal.

Blind spot

Product focus. Delivery focus. Horse blinkers.

When the organization stares at product and output, people disappear from view. We forgot people come before the product. They are still on the org chart. They are no longer in the center of the design.

Harm

Burnt out. Pushed out. Ignored. Manipulated.

Interviews across organizations surfaced the same stories. People asked to adopt agile without agency. Punished for honesty in retrospectives. Replaced when velocity dipped. This is not agile failure. It is human failure dressed in agile language.

"I raised concerns in the retro. Two months later I was managed out. The retro is not for learning here. It is for tracking."
Developer, telecom

Read the full survey

Dark Agile

People become headcount. Not humans who build, receive, or change.

Jeffries called it Dark Scrum. At enterprise scale it is Dark Agile. Same disease, bigger dashboards. Field interviews also name forced agile (budget-dictated rollout) and fake agile (ceremony without belief). See human impact mapping or the divide

What agile actually said

Agile never started as a delivery machine.

Individuals

Over process

Individuals

  • Listed first in the manifesto
  • Buried under rollout pressure
  • Pushed to change, rarely encouraged

Collaboration

Over contracts

Collaboration

  • Stay close to the customer
  • Ship, learn, adjust
  • Humans still in the room

Trust teams

Motivated individuals

Trust teams

  • Build around motivated individuals
  • Give environment and support
  • Trust them to get it done

How it went wrong

From customer focus to product metrics to human-centred design. The three-stage drift and budget audit are documented on the model page and home page, not repeated here.

The drift

We kept the shipping. We dropped the humans.

Product only

What we kept

Product only

  • Dashboards and rollouts
  • Customers became metrics
  • Teams became velocity

Humans left

What we lost

Humans left

  • Still on the slide, not in the center
  • Progress became output
  • We abandoned who it was written for

The answer

Put both humans back, before the next rollout.

Reinforce the human element when product and delivery take the wheel. That is why Human Agile exists.

Read the Human Agile Model

Receives

The customer. Human. Back in the journey.

Delivers

The team. Human. Back in the room.

Both

From design through scale. Both sides of the promise.

Measure the drift

Trust never left the page. It left the room.

Take the Index
Agile Manifesto
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
The Twelve Principles of Agile Software
Ron Jeffries
Too often, at least in software, Scrum seems to oppress people. As a result, everyone suffers. Most often, the developers suffer more than anyone.
Dark Scrum, 2016

Read the full advocate archive

Here's the model

Human Agile Model