InfoQ

News

'State of Agile' Survey Open for Participation

Posted by Chris Sims on Jul 02, 2008 05:31 AM

Community
Agile
Topics
Adopting Agile
Tags
Statistics ,
Surveys
VersionOne, a maker of agile project management tools, has announced that the third annual 'State of Agile Development' survey is open for participation. The online survey is intended to gauge the value of agile development practices in the field. Results will be announced on August 4th, at the Agile 2008 conference in Toronto.

This year's survey takes about 10 minutes to complete and will be open until July 21. Participants may remain anonymous, or may choose to provide an email address so that VersionOne can email them the results. 

The survey covers:

  • Personal experience
  • Your company's experience and level of involvement with agile
  • Which practices are in use
  • Motivations for adopting agile
  • Results achieved

The first survey , in 2006, had 722 participants from 47 countries. Of the companies represented, 84% were using agile somewhere in the organization. On average, participants had been using agile methods for 2.3 years.

When asked to identify the role of the initial champion of agile development, the results were:

VP / Director of Development 28%
Project Manager 18%
Team Lead 13%
President / CEO 11%
Architect 7%
CIO 5%
Consultant 5%

The full results of the 2006 survey [pdf] are available for download.

Last year nearly 1,700 people from 71 countries participated in the second survey. Of the companies represented, 73.2% were using agile somewhere in the organization.

Asked how long they had been practicing agile development, respondents said:

Greater than 5 years 12%
2 - 5 years 26.1%
1 - 2 years 20.9%
6 - 12 months 16.6%
Less than 6 months 16%
Never 8.4%

And what role as the initial champion of agile development?

Team Lead / Dev. Manager 22%
VP / Director of Development 19%
C-Level Executive 18%
Project Manager 15%
Architect 8%
Developer 6%

The full results of the 2007 survey [pdf] are available for download.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

No comments

Watch Thread Reply

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.