Agile Fragile.

Human First Reformation, Before Transformation

Human is the architecture

We forgot people come before the product.

The budget nobody audits

What I kept hearing in programme reviews, against what the Manifesto actually meant.

What agile meant. The Manifesto put humans first: about 55% of its weight on people inside the work, 23% on product and delivery as proof, 17% on process. People were the architecture. Product showed it worked.

What I see now. Most transformations flipped that. Programme reviews spend about 55% of their airtime on velocity, roadmaps, and dashboards, 18% on ceremony, and only 18% on the humans carrying the change. Product became the architecture. People became a line item.

That is a 37-point people gap. Same story in every org I have worked in: teams became velocity, customers became metrics, leaders tracked progress while people absorbed the cost. Nobody names it in the steering committee. Everybody feels it in the retro.

When the budget owns the rollout, people call it Dark Agile, forced agile, or fake agile. I charted the human cost on the leaders page.

Explore

The model, the Index, and notes from the room.

Our story

Agile was meant to help organizations. Organizations are made of humans. Right now, in most enterprise IT work I see, people are the least trained, least protected, and least heard part of the change.

I did not set out to invent another framework. I watched agility get performed on dashboards while engineers burned out, retros turned into tracking, and good people left quietly. That is not agile failing. That is people failing while agile takes the blame.

The Human Agile model started as notes from that drift. Read the model or see the budget gap. Green delivery with a low human score is still Dark Agile.

Agile Fragile is where I put those notes in public. If it matches what you see, tell me. I am Anjish Bhondwe.

Read the full story

Measure the gap

Eight questions. One honest read of whether your org practices agile with people inside, or performs it for dashboards.

Three bands: Dark Agile, Transitional, Human Agile. Four moves if you want to act on what you find. One human gate before you scale. The budget story sits in the drift section. The strain charts are on the leaders page.

55%

enterprise focus on product & delivery

18%

typical focus on the team building it

37

point people gap vs manifesto intent

8

Index questions on human practice only

Take the Index

What people told me

What people told me in interviews. Not complaints about agile. Proof that the social system broke while the dashboard stayed green.

"Leadership sees green dashboards. We see people crying in the bathroom. Both are true in the same building."
People lead, technology
"I was burnt out before the transformation. After it, I had sprints on top of the work I already could not finish."
Engineer, financial services
Read more field voices

Human Agile Index™

Eight questions. Does your organization practice agility with humans inside, or perform it for dashboards while the team carries 18% of the attention?

The Index is mine. If you want to use it in research or client work, ask first. Intellectual property.

Starting

Are people in the room when agile change is designed?

Is agile built with teams, or pushed on a timeline?

Do people feel valued in the transformation?

Are dashboards for learning or judgment?

Is burnout a design problem or a people problem?

Can teams reject ceremony that does not help?

Do leaders enable teams or track and report?

Does agile work for your people, not against them?

Your score

0%

Transitional

Share your score

Stay in the loop

Get updates as the Human Agile model develops.

Something went wrong. Email hello@agilefragile.com directly.

Got it. I will be in touch.