Wednesday, May 6, 2009

Agile Culture: Where Should a Newbie Start?

This post stemmed from a post by Joelle Godfrey, Agile Culture: Where Should a Newbie Start?

After reading the article I asked ASPE President David Mantica to give me his thoughts...
There are a number of problems in life, one of the biggest problems is humans' crazy desire to make everything so darn confusing and over complicated. Ayn Rand was so right when she showed true genus tied to John Galt’s one-equation solution to static electricity. We are always trying to over complicate things to show our intelligence, when true genus is being able to take the complicated and make it simple.

Joelle Godfrey's post does a fantastic job of showing the very basic concepts of Agile for a beginner. Agile, in its purest form is one of those KISS (Keep It Simple, Stupid) solutions of true genus, but as with anything over the years it has gotten more and more complicated. Godfrey likens Agile and the different “flavors” of Agile to a nation and different districts. I liken Agile to an open source methodology and the different flavors as productized variants of the methodology. Much like Linux is the base open source Unix operating system and Red Hat and Suse Linux are different productized variants.

A basic understanding of Agile as a management method is critical before a professional can dig deeper into it to roll out a specific methodology flavor. The Agile Management movement is not for everyone. One of the main concepts that will stop many professionals in their tracks is the concept that co-workers and support staff must be treated like “adults”. When was the last time your manager treated you like an adult. Furthermore, some people can’t even define what an “adult” is. I have been asking that question in a number of presentations and getting some pretty interesting answers.

2 comments:

Tryllid said...

Thank you for the response.

I have a follow up question: is there ever a place for agile and waterfall in the same company? Or is Waterfall going to go the way of the dinosaurs?

I can see value in both approaches. Does everything need to be thrown out? I saw the following video the other day that spoke to the value of both approaches:
http://bit.ly/GBc2r

Speaking as a Moderate
Joelle Godfrey
http://jgodfrey.wordpress.com

JT Moore said...

Joelle,

Yes, there is definitely room for both Agile and Waterfall in the same company. Waterfall is still a better process for very complicated, highly regulated projects where every action within the project needs to be monitored and even (based on regulatory compliance issues) backed up.

I have seen organizations practice Agile in one area of the organization and Waterfall in another, and they build “middleware processes” to communicate information between the two processes.

In the end, I believe Agile will be folded into a Waterfall structure, with the Agile concepts becoming more of an overall management philosophy within a Waterfall process.

I don’t ever see Waterfall going away totally.

David