BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ
News Articles Presentations Podcasts Guides

Topics

Choose your language

QCon New York

Find real-world practical inspiration from the world’s most innovative software leaders. Attend in-person.
QCon San Francisco

Learn what's next in software from world-class leaders pushing the boundaries. Attend in-person or get video-only pass to recordings.
The Software Architects' Newsletter

Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.

InfoQ Homepage News Has Agile Crossed the Chasm?

Building an Efficient Cloud Application Architecture (Live Webinar June 22, 2023) - Save Your Seat

Has Agile Crossed the Chasm?

Bookmarks

Jul 27, 2007 1 min read

Write for InfoQ

Join a community of experts. Increase your visibility.
Grow your career.Learn more
Earlier this month Scott Ambler released the results of his 2007 Agile Adoption Survey. This is the 2nd year that Scott has executed the survey, which attempts to provide readers with a consistent view on the adoption of Agile practices over the period. 

In summary the Survey tells us:
  • 69% of respondents indicated that their organizations are doing one or more agile projects.  Of those that hadn't yet started, 24% believed their organizations would do so within the next year;
  • 44% indicated a 90%+ success rate at agile projects, 33% indicated between 75 and 90%.  It appears that agile seems to be working out;
  • Co-located agile projects are more successful on average than non-co-located, which in turn are more successful than projects involving offshoring;
  • 98.6% of agile teams adopted iterations, and 83% had iteration lengths between 1 and 4 weeks;
  • Smaller teams had higher success rates than larger teams;
  • 85% of organizations doing agile had more than one project completed, so it's gone beyond the pilot project stage in most organizations;
  • Iterative development & regular delivery of working software was considered to be the most valuable of the Agile Practices;
Unsurprisingly, the findings of Scott’s survey highlight a lot of what the community already knows (collaboration and communication is king, co-located teams work better than split teams) but also highlights some interesting points:
  • Promiscuous and ad hoc paired programming is more of a reality than fixed pairs.
  • A distinct absence of database refactoring practices, despite code refactoring scoring highly in the "Value To Business" part of the survey.
Scott’s findings are in line with the Agile mantra, although the focus of this year’s report seems to be on practices rather than the adoption of the practices and thus is difficult to compare with the preceding year’s survey, as Scott openly admits:
Although there is an increase from last year's agile adoption rate, I'm reticent to compare the figures because I asked the question significantly differently.
With this in mind, how should we measure the adoption of agile practices, and how as a community can we get a unified picture of the landscape and group behaviours in which we operate?

A complete presentation of Scott's findings can be found here.

Rate this Article

Adoption
Style

This content is in the Agile topic

Related Topics:

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • ad hoc

    by Remember Objective,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    * A distinct absence of database refactoring practices, despite code refactoring scoring highly in the "Value To Business" part of the survey.

    It's because they don't know the art of SQL. Most programmers are not aware of how much you can do with SQL, therefore write a lot of compensating code/xml/garbage that greatly worsens the situation (because it introduces even more code dependencies on the database remaining the way it is, which was their original excuse for not refactoring the database now and then).

    Back to top
  • Re: ad hoc

    by Maris Fogels,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    "It's because they don't know the art of SQL. Most programmers are not aware of how much you can do with SQL, therefore write a lot of compensating code/xml/garbage that greatly worsens the situation"

    If I recall correctly, Scott himself has stated that the problem is an utter lack of tooling support from database vendors. Knowledge of SQL alone will not keep a large project's database flexible, tested, and published under revision control.

    Scott talks about this and other issues facing agile databases in his presentation "Scott Ambler on Database Refactoring". I highly recommend it.

    Back to top

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT