Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News Interview with VersionOne CEO Robert Holler on the State of Agile Survey Results

Interview with VersionOne CEO Robert Holler on the State of Agile Survey Results

Following on from the interview with VersionOne CEO Robert Holler about the Winter 2014 product release, Holler also discuss the 8th State of Agile survey results with this reporter.

Some of the results in the survey results are:

  • 3501 responses collected
  • 66% from North America, 20% from Europe the rest from other parts of the world
  • 88% of respondents identify themselves as at least “knowledgeable” about agile techniques
  • 88% of organizations represented are practicing agile development
  • 72% or organizations have been practicing agile for over 2 years (19% over 5 years)
  • 52% of respondents said they are using agile to manage the majority of their projects
  • 76% of respondents are using distributed agile teams
  • Scrum and Scrum variants are the predominant methodology (73% across Scrum, Scrum/XP and Scrumban)
  • Agile portfolio management is increasing (32% practicing or plan to practice)
  • 73% or respondents say agile projects have faster time to market
  • 92% or respondents say implementing agile improved their ability to manage changing priorities

InfoQ: What was surprising to you in the survey results?

When looking at the results, I look for two things – what’s the commonality from year to year and what the exceptions are from year to year.
The common elements lie in some key areas – the key benefits, why are people choosing agile, what are the most used methodologies and what the primary success factors are.
The top benefits: 1) The ability to manage changing priorities, 2) increased productivity and 3) improved project visibility. Respondents have consistently through the years reported these as the main benefits of heading down the agile path.
Why people are transitioning to agile: the top four are 1) to accelerate time to market, 2) manage changing priorities,3) better alignment between the business and IT, and 4) productivity.
Most used methodology: Scrum continues to dominate.
Key success factors, especially as you start scaling: executive sponsorship, training & education, common tooling infrastructure (management tools and technical tools like continuous integration and source control)
A common theme that permeates the entire report is the fact that this is a cultural change, it’s a human change, it’s not an overnight binary change and the barriers to adoption are primarily human issues as opposed to technology or practice issues.
Looking at what’s evolving based on the survey results over the years, there are three key elements - knowledge, experience and the practices.
Knowledge: awareness of agile concepts and agile development is now pretty pervasive. Two years ago 81% of respondents knew about agile, which meant that 19% did not – now 88% have heard of agile; that’s a significant change over the last two years.
Experience: companies with two or more years of experience have grown from about 50% to over 72%, so nearly three-quarters of organizations have more than two years of experience using agile, which points directly to maturity.
Personal experience with agile of two plus years has gone from 55% two years ago to 64% of respondents.
Another element of experience – last year the number of organizations with more than 10 teams practicing agile was around 30% and this year it’s around 38% which means that agile is certainly starting to scale and mature in organizations.
Practices: One of the most interesting changes is the number of organizations with distributed teams practicing agile a year ago was 35% this year it’s 76% - a huge change. This is clearly a significant change year over year and is simply the reality of scaling to more teams, more projects, more departments – software development is being done across distributed teams. It’s not ideal; we’d prefer that it not be the case, but it is reality. In today’s world distributed teams are the way that a majority of software development is being done.

InfoQ: In your own teams, how distributed are you?

We’ve got 10-15% of our folks distributed around the country, but even within our core organization in Atlanta, Georgia, we have two shops – one in the suburbs and an office downtown – so our team is invariably split between the two sites. This has meant that we’ve had to understand what collaboration means and what we have to do to make it work. We’ve got good sound systems, good audio-video, big screens, dual-working stations – you name it, we’ve taken the steps to get people engaged and ensure we have as much high-bandwidth collaboration going on as possible given the fact that team members are in multiple locations.

InfoQ: That sounds like advice to others as well. Given the 76% of organizations using agile across distributed teams, what do the survey results tell us about the effectiveness of distributed teams?

Looking at the rest of the survey, there is still great consistency in the benefits from prior years – significant time to market improvements, significant productivity improvements, significant visibility improvements. So, whether I’m distributed or not, adopting agile will improve outcomes no matter what. Am I as productive as I would like being distributed? No, but I think teams today have learned to overcome many of the challenges – clearly the higher bandwidth channels are better but by overlaying an agile process with the inherent degree of collaboration, the rhythm, the visibility & transparency and the incremental nature is improving the face of software development. I think agile has helped overcome the “team in the dark” scenario tremendously and we’re doing much better today at software development than we used to, whether collocated or distributed.
The other thing I noticed in the survey is the continuing progression and success of a couple of practices. The use of Kanban boards continues to climb (from 32% to 39% using Kanban). Recently the concept of APM (Agile Portfolio Management/Agile Program Management) has gone from about one-quarter of companies to almost one-third (32%) in the past year, which offers additional validation that agile is scaling fast. This is where we feel that companies like VersionOne can make the biggest difference – it’s in the scaled context that products and infrastructure like ours can really help in terms of enabling success.

The next item in this series will discuss the AgileLIVE webinar series.


Rate this Article