Why I Still Use Agile with Capital A
In short: It helps prevent chaos.
Let’s dive in.
Before we start, I need to emphasize that, in my case, using “Agile” with the capital “A” is not some marketing trick to sell more Agile products or services. I currently work full time as a civil government employee in Indonesia. I admit that I’m passionate about Agile, but not to an extent that I am actively selling products or services related to Agile, at least not right now. It was never my intention to make Agile seem more special than it is. It’s really about making communication clear and precise.
Let’s start by understanding the difference between “Agile” and “agile.” “Agile” with a big “A” refers to a specific way of doing things and a specific mindset. It’s referring to Agile as defined in the Manifesto for Agile Software Development though in reality it can be applied in other areas outside of software development. It’s all about being flexible, working together, pursuing simplicity, making progress step by step, and more. “Agile” with a capital “A” is about this approach.
On the flip side, “agile” with a small “a” is a handy word to describe being quick, adaptable, and able to handle change, no matter what you’re doing. The definition of “agile” can be found in any English dictionaries. It’s not tied to anything particular, so we can use it in lots of different situations.
While “agile” describes flexibility and adaptability, it can sometimes lead to work spiraling out of control simply for the sake of being “quick, adaptable, and able to handle change, no matter what you’re doing”. “Agile” sets a clear framework, ensuring that adaptability is guided by well-defined principles, preventing haphazard changes and maintaining a balance between structure and flexibility. This is what I meant when I said using “Agile” helps prevent chaos.
The matter of differentiating between “Agile” and “agile” is about making sure people understand what we mean. Being clear in our communication is important, no matter what we’re talking about. Here are some examples:
- Everyday conversation: When we’re talking about someone’s ability for adapting to changes, we can just use “agile” without the capital letter. It’s simple and gets the point across without going into any specific rules or methods.
- In written materials: When we’re writing down ideas or instructions, getting the capitalization right helps our readers know what we mean. This is, in my opinion, the most important part because the use of capitalization is explicitly shown.
- General discussions: If we’re in a casual discussion, using “Agile” with a big “A” might signal that we’re specifically talking about Agile practices along with its values and principles.
To conclude, whether we choose “Agile” or “agile” is all about keeping it clear and straightforward. Capitalizing “Agile” spotlights a particular set of values, principles, and practices, while “agile” describe quick thinking and adaptability without being tied to any rules. From where I’m standing, I’d say getting this small detail right in everyday language helps keep things crystal clear, no matter what you’re talking about.
