Agile Practices Survey Results: July 2009

Scott W. Ambler + Associates
Home | Articles | Books | IT Surveys | Podcasts | Contact Us | Announcements | Site Map
How to Measure Anything 2nd Edition This survey was performed the first week of July 2009 and there was 123 respondents. The survey was announced on several agile mailing lists, including the Extreme Programming (XP), Test-Driven Development (TDD), Scrum Development, Agile Modeling, Agile Databases, Agile China, and Agile Unified Process (AUP) mailing lists. The goal was to find out what agile developers were actually doing to compare it with what’s being talked about.

The Survey Results

Some findings include:

Figure 1. Most effective agile practices.

Most effective agile practices

Figure 2. Agile practices that were easiest to learn.

Agile practices that are easiest to learn

Figure 3. Agile practices that were hardest to learn.

Agile practices that are hardest to learn

Figure 4. Agile practices which were tried and abandoned.

Agile practices that were tried and then abandoned

Figure 5. Agile practices which people hope to adopt some day.

Agile practices people want to adopt

Figure 6. Average size of agile teams.

Average agile team size

Figure 7. Agile software development and regulatory compliance.

Agile and regulatory compliance

Figure 8. Agile software development and CMMI.

Agile and CMMI

Figure 9. Agile software development and geographical distribution.

Agile and geographic distribution


Survey questions

The Survey Questions (116 K)

Survey Data File

Raw Data (103 K)

Survey Presentation

Summary Presentation (206 K)

What You May Do With This Information

You may use this data as you see fit, but may not sell it in whole or in part. You may publish summaries of the findings, but if you do so you must reference the survey accordingly (include the name and the URL to this page). Feel free to contact me with questions. Better yet, if you publish, please let me know so I can link to your work.

Discussion of the Results

  1. I'm disappointed in the response rate being only 123 people. I suspect that the agile community has become tired of being surveyed constantly.
  2. The question about org size was misworded. As a result I suspect that most people answered what their team size was, particularly because the answers were very similar to that given for the question where I actually asked about team size and because previous surveys had very different answers for org size.
  3. 8 people dropped off at question #7, which asked about what phase (Initiation, construction, release, production,...) your agile project was in. "Phase" is a dirty word among some extremists, even though it's exceptionally obvious that agile projects go through phases (oops, I mean they exhibit rhythms), and it's disappointing that that many people would quit the survey just because I used terminology which goes against their "agile sensibilities".
  4. Different people find different practices easy to learn vs. hard to learn. So, there's an overlap in figures 2 and 3 as a result. This was expected to happen.
  5. This survey suffers from the fundamental challenges faced by all surveys.

Links to Other Articles/Surveys

  1. My other surveys

Why Share This Much Information?

I'm sharing the results, and in particular the source data, of my surveys for several reasons:

  1. Other people can do a much better job of analysis than I can. If they publish online, I am more than happy to include links to their articles/papers.
  2. Once I've published my column summarizing the data in DDJ, I really don't have any reason not to share the information.
  3. Too many traditionalists out there like to use the "where's the proof" question as an excuse not to adopt agile techniques. By providing some evidence that a wide range of organizations seem to be adopting these techniques maybe we can get them to rethink things a bit.
  4. I think that it's a good thing to do and I invite others to do the same.

Disciplined Agile Delivery: The Foundation for Scaling Agile Agile Modeling: Practices for Scaling Agile Agile Data: Practices for Scaling Agile EnterpriseUP: Agility at Scale Software Development Practices Advisor Scott Ambler + Associates Follow @scottwambler on Twitter!

Copyright 2009-2014 Scott W. Ambler

This site owned by Ambysoft Inc.