Your stand-up routine lasts 45 minutes. No one in that room thinks it's a stand-up routine. You're basically giving a status update with unnecessary details. Also, the individual inquiring about what is blocking you is not actually helping to resolve the issue.
The framework isn't the problem
People enjoy criticizing Agile methods, such as the lengthy 45-minute daily stand-up meetings. The 45-minute standups, the story points that somehow became a performance review, the sprint that never ends. However, blaming Agile would be similar to blaming the hammer for the hole in your wall. Despite everything, statistics show that people are still using it. Digital.ai's 17th Annual State of Agile Report from January 2024 surveyed 788 software pros and found 71% of organizations use Agile. The most painful aspect is that only 11% of practitioners in the same report were "very satisfied" and 33% more were "somewhat satisfied". Therefore, fewer than half of the individuals who use it feel satisfied with it. This is not due to a failure of the framework but rather a failure of trust.
Ceremonies become cameras when trust runs out
An event is what you make of it. The same standup can feel like a quick check-in or a daily interrogation. It's not about the ritual. It's about the person with the stopwatch and their intentions. In June 2023, Bradley Momberger of Bitovi hit the nail on the head with this, describing what we might call "faux Agile," where a product owner or manager becomes, in his words, "the single chokepoint for all communication."
An even clearer indication of the issue at hand is: the tools "are designed for the micro-managers on the team and not trustful enough of developers to do the right things."
If the board is there to monitor you and not support you, then it's not Agile you are talking about, but rather surveillance using a Jira license. 🎥
The report also identifies "developer burnout", "unrelenting demand", and a "disconnect between Agile practitioners and the business" as primary barriers. None of those are process issues. They are symptoms of the experience of low trust.
"You're doing Agile wrong" is a smell
They will come around kicking and screaming if they have to. Tell them they are going about it all wrong and you may as well have suggested sacrificing a chicken at the next stand-up. It's actually a confession. A perfect explanation came from an article in InfoWorld in 2016: "the issue with most agile implementations, isn't with agile, it's with Agile, the Capitalized Methodology". Little-a agile is a set of values. Big-A Agile is what your Vice President purchased a consulting package for. The defense mechanism of "you're doing it wrong" never asks who made a weapon out of the ritual. It simply shields the trademark.
Metrics are the honest tell
Observe how your velocity chart behaves. It will tell you what your organization truly desires. The governance advice from DevSamurai is clear: "Agile metrics should not be used for surveillance. It is for awareness."
Axify.io echoed it in June 2025, warning that "metrics can feel like surveillance if you're not careful" and to treat them "as a team support tool, not a punishment tool."
A September 2025 Medium analysis added its own warning, advising "Transparency Over Surveillance" because "when metrics become weapons, teams hide problems instead of fixing them."
If you use the numbers as a weapon, people will find ways to manipulate the numbers. Here's how I read it now:
→ Metrics used for awareness build trust
→ Metrics used for judgment kill it
→ Once trust dies, every ceremony curdles into a checkpoint
What we actually do about it
In my startup, we have asynchronous standup meetings almost every day. We communicate when something is blocking us. We don't fake busyness for the sake of looking busy. We use story points as a way to estimate the effort and complexity of a task, in order to help with planning and to measure our own velocity and progress. This did not call for a new structure. It called for the faith that adults will bring issues to light if you don't penalize them for it. Fatigue caused by Agile is a real thing. However, it's not the actual mechanics of Agile causing the fatigue, it's the constant oversight and pressure. If you were to switch from Scrum to Kanban, a manager without trust will start measuring the time you were spending on each task, But it wasn't really the framework that did that. Here is a question for you to ponder: which ceremony within your team lost its function as a tool and instead started acting as a camera, reflecting what is truly going on?
Top comments (0)