Ambysoft logo

2015 Q1 Agile State of the Art Survey Results

Follow @scottwambler on Twitter!

How to Measure Anything This survey was performed in early 2015 until under the title "2015 Q1 Agile State of the Art Survey". The survey was announced in my Twitter feed, and several LinkedIn discussion forums (Disciplined Agile Delivery, Agile and Lean Software Development, Agile CMMI, and Scrum Practitioners ).

The Survey Results

Some findings include:

Figure 1. Iteration lengths on agile teams.

Average Iteration lengths

Figure 2. Iternal release cadences on agile teams.

Internal release cadence on agile teams

Figure 3. Production release cadences on agile teams.

Production release cadence on agile teams

Figure 4. Technical debt avoidance strategies.

Technical debt avoidance strategies

Figure 5. Technical debt removal strategies.

Technical debt removal strategies

Figure 6. Technical debt funding strategies.

Technical debt funding strategies

Figure 7. Technical debt awareness.

Technical debt awareness


Survey questions

The Survey Questions

Survey Data File

Raw Data

Survey Presentation

Summary Presentation

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. 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.