Agile: To Be or Not to Be
I was the guest speaker for a leading software development organization and the topic of Agile was being discussed in a workshop during the day before my speech. They had some early successes with Agile and were now briefing the entire organization on the principles and how they could be used as they transitioned to a more “Agile” shop.
One of the presenters was saying very bad things about the waterfall methodology as if it was useless. Since they had not mailed my check and I was a guest I just clenched my teeth as it was not my place to comment. Towards the end of the presentation a respected senior leader stood up and said “I hear you…but what you are describing we have been doing for over twenty years...”
BINGO! Agile is simply a form of iterative development.
For you younger readers out there software developers have been doing iterative development since the 1960’s. Below is my opinion. Please note it is just that.
A. The ends of the methodology spectrum are iterative and waterfall.
B. You can have many versions in between iterative and waterfall. Each organization has to strike a balance on where they want to be in this spectrum based on their capability, customers and critical nature of the project.
If a pilot told me the plane’s navigation software was developed with Agile I would unbuckle my seat belt and head for the door. If a smart phone app was being developed with the strict methodology used for navigation software in aircraft it would be obsolete when released.
It is not always the same answer for every project or organization.
All the arguments about which methodology is “better” are pointless because it is situation dependent. Each comes with risks and benefits that must be weighed.
C. I agree with what is in the Agile Manifesto BUT the overwhelming majority of what is in there is not new or even close to being new. It is assembled just like quality principles were assembled into TQM and Six Sigma for that matter. Nothing new in TQM or Six Sigma. The Agile manifesto is just the combination of things into a methodology to make it easier for some organizations to embrace and implement... just like a diet plan provides a framework for you to eat less.
D. No organization really has to have TQM or Six Sigma or "The Flavor of the Day" to execute the principles of quality, just like no organization has to have Agile to do iterative development.
E. It is a tried and true consultant revenue generating model to take existing knowledge...massage it into a "system," give it a catchy name and sell it to the masses. You know you have done this at the highest level (Cha-Ching) when people get certified in your system. I am not throwing rocks at the ScrumMasters and Six Sigma Black Belt holders out there, as a PMP I am living in a glass house.
Project management is simply Structured Organized Common Sense (SOCS). You can use different structures successfully…just don’t violate the common sense part. Violating the common sense part is how you get into real trouble.
Dr. James T. Brown PMP PE, author, The Handbook of Program Management - McGraw-Hill