Agile Is a Framework, Not a Religion

Agile is a framework, not a religion. Its purpose is to help teams reason about work, not to replace thinking with ritual. When organizations treat agile practices as dogma, they trade adaptability for compliance and creativity for theater. The real discipline is not following a single methodology, but choosing the right tools for the job. That includes how projects are managed.

I've spent over two decades working in development across waterfall, lean, kanban, and agile environments, and I've seen how different approaches work in practice.

Agile for software development teams can be extremely effective when it's practiced in alignment with the original values of the Agile Manifesto for Software Development, which prioritizes individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.

The core of agile is about adaptive, iterative delivery and team-centric collaboration grounded in its manifesto and principles — values that were developed by practitioners who wanted an alternative to heavyweight, documentation-driven processes.

But here's the simple truth too few people will say out loud: not all projects are actually agile. Some types of work do not fit that model, and imposing agile practices on those contexts doesn't make the work more agile, it just makes the process more complicated and less efficient.

For example, standups in agile frameworks were designed as a simple, frequent way for a team to synchronize around work and surface obstacles together. In agile contexts like Scrum, this daily meeting is meant to be a short collaboration among team members focused on progress toward a shared goal and any impediments that might block that progress — it's not meant to be a formal status update for managers or stakeholders. The intent is to help the team adjust its plan for the day, highlight dependencies, and identify opportunities to help one another. This is a team-centric planning and coordination moment, not a reporting session.

When they are treated as mandatory status updates, or when parallel standups are held across multiple teams for the same scope of work, they quickly shift away from their original purpose. Instead of enabling quick alignment and unblocking, they become meetings that interrupt flow, duplicate information, and pull people into repetitive updates rather than collaborative problem solving. That is not agility — that is bureaucracy dressed up as collaboration.

True agile practices create value by helping teams deliver outcomes faster and adaptively, by empowering people to focus on meaningful work, by shortening feedback loops, and by keeping the customer at the center. When adopting agile practices creates more overhead than clarity, then it's worth asking whether you are actually being agile or just following the script.