Follow @RoyOsherove on Twitter

Good Agile, Bad Agile

Steve Yegge, an employee at Google, has a very interesting post where he separates "Bad Agile" from "Good Agile". I urge you to read this long post as it contains many points that try to explain what "Bad Agile" is.

There's a lot I want to talk about in regards to that post, but first it's important to read it (and it's 180+ comments) to get an idea of Steve's thoughts.

Regardless of his thoughts, he describes Google as the ultimate place to work for. The stuff he mentions that goes on there sounds really great. I'd love to take a tour of the place some day.

Steve thinks that "Google" is the new "Good Agile", and that the word "Agile" is too overloaded and should be ridden of.

Personally I think that he has some valid points, but I tend to disagree with many other points he makes.

Funnily enough, he mentions two practices that Agile Advocates use:

"I would caution you to be skeptical of two kinds of claims:
- "all the good stuff he described is really Agile"
- "all the bad stuff he described is the fault of the team's execution of the process"

You'll hear them time and again. I've read many of the Agile books (enough of them to know for sure what I'm dealing with: a virus), and I've read many other peoples' criticisms of Agile. Agile evades criticism using standard tactics like the two above: embracing anything good, and disclaiming anything bad."

True, I think this is a real concern. As a pragmatist, I try to be realistic with Agile practices, and I've never seen companies follow an exact methodology to the letter, but instead use a bunch of practices from several places, and integrate them into their teams. It's a much more reasonable place to be than turning your whole world upside down, and you can always add more agility when you need it.

I am tempted to label all the good things he wrote in that post as "Agile". Seriously, they do feel like it. But just because he said "beware of these claims" doesn't mean they aren't correct. It's a sign of a great writer when he can predict the reactions of the reader and the people reacting to it, and pre-answer those concerns.

Do you think he's right? Wrong? both?  Your comments are welcome.

I'll be writing more about this in the coming days.

DataFresh - Database rollback library for unit tests

How to get disqualified as an MVP