It’s notable that the ratio of “that’s not really agile” to “this _is_ agile” comments in discussions like this is typically about 10:1. Everyone knows what agile isn’t but no one can seem to explain exactly what it _is_.
Furthermore, the “you’re holding it wrong” criticism of everyone who gets poor results from agile, which seems to be a majority of people attempting to use agile practices according to articles like this and comments ITT, is a major cop out. If 75% of people attempting to use a tool hurt themselves with it, you should start asking whether this was a well designed tool in the first place.
My solution: stop using the term “agile.” It’s so vague and means so many things to different people that it effectively means nothing. Instead, talk about specific practices (sprints, story points, etc) and be able to explain the purpose of each practice. This can clear away the agile fog and get people discussing actual trade offs rather than agile magic dust.
There is no one “Agile Methodology”. It’s meant to be a communication protocol you grow within your organisation based on the principals outlined in the manifesto.
The title of the article “Everyone claims they are following “agile methods” but few actually do” suggests that there is something called “agile methods” that can be followed. I don’t think I understand what you mean about it being a communication protocol. In any event, it seems beyond debate that the term “agile” is extremely widely misunderstood. I’m arguing that instead of tilting at windmills trying to correct everyone who is “understanding it wrong”, we give up, discard the term, and focus the pros and cons of specific, describable practices. Agile seems to be more of a feeling than a practice.
There are some codified system of rules and behaviors that people have developed to help their orgs gain agility e.g. Scrum, SAFe, etc. But there are probably an infinite ways to skin that cat. Doesn’t really matter which one you use just that everyone is using the same one.
Which leads me onto why it’s a communication protocol. Human systems/processes/procedures just organise the flow of information, often to help people make decisions. If everyone isn’t following the same set of rules and behaviours then there can be a breakdown in communication. Which usually screws things up (whether top down or bottom up)
Furthermore, the “you’re holding it wrong” criticism of everyone who gets poor results from agile, which seems to be a majority of people attempting to use agile practices according to articles like this and comments ITT, is a major cop out. If 75% of people attempting to use a tool hurt themselves with it, you should start asking whether this was a well designed tool in the first place.
My solution: stop using the term “agile.” It’s so vague and means so many things to different people that it effectively means nothing. Instead, talk about specific practices (sprints, story points, etc) and be able to explain the purpose of each practice. This can clear away the agile fog and get people discussing actual trade offs rather than agile magic dust.