Agile Fragile | Human Agile model

Agile Fragile.

Human First Reformation, Before Transformation

The drift Product first. People later. The drift. Enterprise agile budgets 55% of the conversation for delivery, velocity, and dashboards. Only 18% reaches the humans building it. We forgot the order.

What the room shows Green charts. Breaking teams. Stand-ups get tracked. Burnout gets called personal resilience. Honest feedback in a retro feels career-risky. The rollout looks green. People are paying for it.

The correction Human People come before the product. In the room before the rollout is designed, not on a slide after the date is set.

Adapt Subtract Dark Agile theater first. Agility built with teams, not pushed on a programme timeline.

Implement Delivery that protects humans, not just dashboards. Product is evidence. Human is the architecture.

Scale Grow only after the human gate clears. High delivery with a low human score is still Dark Agile.

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 enterprises adapt, implement, and scale under one roof: agile delivery change and AI adoption together. 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. AI readiness reviews repeat the pattern: about 52% on tools and automation metrics, 22% on compliance, and only 14% on the humans carrying the adaptation. Agile without AI is incomplete. AI without agile discipline is incompetent. Product became the architecture. People became a line item.

That is a 37-point people gap. In programme reviews I keep hearing the same story: teams became velocity, customers became metrics, and leaders tracked progress while people absorbed the cost. Nobody names it in the steering committee. Everybody feels it in the retro.

Under scrutiny and governance, people call the delivery side Dark Agile, forced agile, or fake agile, and the AI side Dark AI, forced AI, or fake AI. I charted the human cost on the leaders page.

Explore

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

Human Agile Model Model Architecture, human gate, Figure HF-1 foundations diagram, Index scoring Human Agile Index Diagnostic Eight questions. Dark, transitional, or human. Field notes Story How enterprise agile lost the humans Industry proposal Proposal With human, for human. Read the model proposal. For sponsors Leaders When the rollout looks green and people are breaking

Our story

Agile was meant to help organizations. AI is meant to amplify them. Organizations are made of humans. Right now, under the combined transformation tabernacle, 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. Then AI mandates stacked on top before the agile wound healed. That is not technology failing. That is people failing while transformation takes the credit.

The Human Agile model started as notes from that drift: how to adapt, implement, and scale with humans inside while agile and AI change run together. 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. One human gate before you scale. How to use the model · strain charts on the leaders page.

55%

enterprise focus on product & delivery

18%

typical focus on the team building it

point people gap vs manifesto intent

Index questions on human practice only

Take the Index

Proposed by

View Bio Anjish Bhondwe Enterprise agile field work · Model author Read The proposal How engagement could work

What our survey reveals

Anonymous survey across telecom, financial services, retail, and technology. 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 the full survey

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

Transitional

Read the model Contact

Share your score

Industry domain Submit anonymously

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.