While I was writing
Brown Noise in Written Language, Part 2, twice I came across the word “agile.” First, the word “agility” was in the original sentence that I was criticizing.
Joel Garry picked up on it and described it as “a code word for ‘sloppy programming.’” Second, if you read my final paragraph, you might have noticed that I used the term “waterfall” to describe one method for producing bad writing. Waterfall is a reliable method for producing bad computer software too, in my experience, and for exactly the same reason. Whenever I disparage “waterfall,” I’m usually thinking fondly of “agile,” which I consider to be “waterfall’s” opposite. I was thinking fondly of “agile,” then, when I wrote that paragraph, which put me at odds with Joel’s disparaging description of the word. Such conflict usually motivates me to write something.
In my career, I’ve almost always had one foot in each of two separate worlds. These days, one foot is in the Oracle world. There, I have all my old buddies from having worked at
Oracle Corporation for over a decade, from companies like
Miracle and
Pythian, the
Oracle ACEs and ACE Directors,
Oracle OpenWorld,
ODTUG, and a
couple dozen or so user groups that I visit every year. The other foot is in the business of software. There, I have colleagues and friends from
37signals and
Fog Creek and
Red Gate and
Pragmatic Marketing, the
Business of Software conference, and the dozens of blogs and tweets that I study every day in order to fuel a company that makes not just software that meets a list of requirements, but software that makes you feel like something magical has been accomplished when you run it.
In my Oracle world, agile is a
dirty word. I have to actually be careful when I use it. To my Oracle practitioner colleagues, the A-word means, as Joel wrote, “sloppy programming.” In my business of software world, though, “agile” means wholesome golden goodness, an elegant solution to the absolutely most difficult problems in our field. I’m not being facetious one little bit here, either. The two most important influences in my professional life in the past decade have been, far and away:
- Eli Goldratt’s The Goal: A Process of Ongoing Improvement
- Kent Beck’s Extreme Programming Explained: Embrace Change (2nd Edition)
Far and away.
I don’t mention this among most of my Oracle friends. I don’t blurt out the A-word to them, any more than I’d blurt out the F-word at my parents’ dinner table. To talk with my Oracle friends about the goodness of “A-word development” would go over like an enthusiastic hour-long lecture on
urophagia.
A lot of really smart people are very anti-“agile.” I’m pretty sure that it’s mostly because they’ve seen project leaders in the Oracle market segment using the A-word to sell—or justify—some really bad decisions (see Table 1). So the word “agile” itself has been co-opted in our Oracle culture now to mean sloppy, stupid, unprofessional, irresponsible, immature, or naive. That’s ok. I’ve had words taken away from me before. (Like “
scalability,” which today is little more than some vague synonym for “fast” or “good”; or “
methodology,” which apparently people think sounds cooler than “method.” ...Ok, I am actually a little angry at the agile guys for that one.) That doesn’t mean I can’t still use the concepts.
Table 1.
| What people think agile means | What agile means |
|---|
| No written requirements specification; therefore, no disciplined way to match software to requirements. | You write your requirements as computer programs that test your software instead of writing your requirements in natural language documents that a human has to read and interpret to re-test your software every time a developer commits new source code. |
| No testing phase; therefore, no testing. | You test your software before every commit to your source code repository, by running your automated test suite. |
| No written design specification; therefore, developers just “design” as they go. | You iterate your design along with your code, but design changes are always accompanied by changes to the automated test programs (which, remember, are the specification). |
| Rapid prototyping always results in the production code being a fragile—well—rapid fragile, prototype. | When you can’t know how (or whether) something will work, you build it and find out—but only the parts you know you’ll really need. You use the knowledge learned from those experiences to build the one you’ll keep. |
Agile is not a synonym for sloppy. On the contrary, you're not really doing agile if you’re not extraordinarily disciplined. I think that is why a lot of people who try agile hit so hard when they fail. I hope you will check out
Balancing Agility and Discipline: A Guide for the Perplexed, coauthored by
Barry Boehm (yes,
that Barry Boehm) if you feel perplexed and in need of guidance.
As with any label, I hope you’ll realize that when you use a word that stands for a complex collection of thought, not everyone who hears or reads the word sees the same mental picture. When this happens, the word ceases being a tool and becomes part of a new problem.
