Pondering the Agile “Don’t Know” Methodology

February 9, 2012 Matthew Badgley

If you haven’t already heard the buzz, the State of Agile Development Survey 2011 is now out and it is packed full with some great information.   The survey is a helpful resource to quantify what people are doing and the value they have realized or have not realized through their particular agile implementation.  As part of teaching agile methodology and speaking to the delivery methods used, I often reference this pie chart, which shows the Agile Methodology Used, and I just updated my training materials with these latest results.  One thing really jumped out at me and made me go, “huh?”  It was that 8% of the respondents answered “Don’t Know” to the question, “what agile methodology do you use?”  That’s roughly 500 of the 6,000+ respondents.  And like any good agile metric, seeing this only made me ask questions and hypothesize as to why so many folks answered “Don’t Know.”

The first thought I had is training.  Yes, coming from a guy who does coaching, that is the first thing I thought of.  But not for the reasons you may think.  If you think about it, the number of teams applying agile methods is climbing the blade of the hockey stick. As someone who has seen the benefits in product outcomes and overall organizational morale, I think this is great!  But the challenge is, with adopting agile it does require training the team members so that they, the TEAM, can make the transition successful and help adapt, adjust and evolve the agile methods used to fit their development environment.  In agile development, the TEAM owns the process and the TEAM is empowered to make it successful.  This is much different than traditional project management where you can focus training on just the project managers and folks in leadership positions.  The team just needs to know where to report time, and how to write up their status reports.  So, if the team has not been trained on what agile is, and the surrounding methods and processes, then I can understand when you ask them, “Do you do agile?” … “Yes.” “What agile method do you use?” … “I don’t know.”

The second reason I can think of why folks answered, “Don’t Know” is that they are leveraging multiple concepts from the various agile methodologies – including agile project management and traditional project management.  The survey did allow folks to answer “Hybrid” (9% of respondents answered), but in my discussions with teams lately – the application of Agile principles is the beginning focus with the adopting and adapting processes is much more flexible.  Teams are starting with one method and morphing to another, and in some cases leveraging a little bit from everything.  This approach can be good and bad, depending on the maturity of the team and the ability to continuously improve.

Besides the answer of “ignorant blissfulness,” the only other thought I had for the “Don’t Know” response are those that work at organizations that have heard about this Agile thing and decided that they will become Agile.  So they leveraged Find and Replace to put the word Agile in place of whatever methodology they were using before.

So, what are your thoughts?  If you participated in the State of Agile Survey this year, why did you answer “Don’t Know”?

The post Pondering the Agile “Don’t Know” Methodology appeared first on VersionOne Blog.

Previous Article
Agile Success Requires More than Just Standing Up
Agile Success Requires More than Just Standing Up

The Wall Street Journal recently published a piece on the Agile practice of daily stand-up (or daily Scrum)...

Next Article
Epics or Feature Groups?
Epics or Feature Groups?

When should you use an Epic versus a Feature Group (aka 'Theme')?" Either asset can be used for grouping in...