“We work agile” is one of the most reliably misleading things a team can say.
Not because agile is a bad idea — it is not. When it works, it is one of the most effective ways to build software and run projects. But in our experience, the word is used in two very different ways, and only one of them has anything to do with the methodology.
The first version looks like this: short iterations, a clear backlog, working software delivered at the end of every sprint, and actual users giving actual feedback before the next cycle starts. The process exists to serve delivery, not the other way around.
The second version looks like this: daily stand-ups, a board full of tickets, retrospectives that produce no change, and a release that is always “nearly ready.” Nobody can quite remember the last time something went live. There is no plan — but there is an explanation for why plans are not needed, because “we are agile.”
We have sat in enough of those rooms to know the difference quickly.
The litmus test is not complicated.
Do you ship at the end of every sprint? Not a demo to internal stakeholders. Not a build that could theoretically be released. Something in production that real users can touch.
And do you gather feedback from those users? Not assumptions, not analytics inferred from usage data weeks later — but deliberate, structured contact with the people who are supposed to benefit from what you built.
If both answers are yes, you are doing something genuinely useful regardless of what you call it.
If the answer to either is no — consistently, not occasionally — then agile is not your methodology. It is your excuse. The stand-ups and sprints and retrospectives are rituals filling the space where structure, ownership, and a real plan should be.
The teams that struggle here are often not lazy or indifferent. They are often genuinely confused about what agile asks of them. It asks for discipline, not the absence of it. It asks for faster feedback loops, which only work if you are actually closing those loops. It asks for a plan that is held loosely — not for no plan at all.
Getting this right is not about coaching the team harder or adding more ceremonies. It is about asking two questions honestly: are we shipping? Are we listening?
Everything else follows from that.