InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

'State of Agile' Survey Shows Wider Agile Adoption

Posted by Chris Sims on Sep 08, 2008

Sections
Process & Practices
Topics
Agile
Tags
VersionOneSoftware ,
Process Adoption ,
Surveys

The results of Version One's 3rd annual 'State of Agile' survey are in. According to the survey, agile practices are being used more widely and with impressive results. More than half of the respondents indicated that 90 - 100% of their organization's agile projects have been successful, and 93% indicated that agile practices had enhanced their ability to respond to changing priorities.

This year's survey was based on 2319 completed surveys, representing 80 countries. This compares to around 1700 surveys from 71 countries last year, and 722 surveys from 47 countries in 2006. The vast majority of respondents reported that they are actively involved in agile development, and most reported a year or more of experience practicing agile development methods.

The role most likely to be the initial champion for agile development was the VP/Director of Development, with a three-way tie for second place between 'Project Manager', 'Development Manager' and 'CIO/CTO'. The methodology most commonly used was Scrum, with 'Scum/XP Hybrid' coming in second.

The survey provided some interesting 2008 vs. 2007 comparisons regarding which particular practices where being employed. Almost universally, a greater percentage of respondents were employing each practice. The only exception was refactoring, which was used by 59% of respondents both this year and last. Practices that enjoyed the greatest increase in adoption were:

Taskboard Up 31%
Iteration Planning Up 21%
Daily Standup Up 20%
Retrospectives Up 20%

The practices that were most widely adopted were:

Iteration Planning 86%
Unit Testing 77%
Daily Standup 75%
Release Planning 72%

The good news is that the vast majority of respondents indicated that the vast majority of their agile projects succeed, with 55% of respondents reporting a 90 - 100% success rate.


What Percentage of the Organization's Agile Projects Succeed?
Percentage of Agile Proects that Succeed


The benefits most widely cited by the survey participants were:

Enhanced Ability to Manage Changing Priorities 93%
Improved project Visibility 83%
Increased Productivity 74%
Improved Team Morale 74%

The full survey results are available on the Version One website, as are the 2007 survey results as well as the 2006 survey results.

  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

No comments

Watch Thread Reply

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.