InfoQ

News

Presentation: Agile in Practice: What Is Actually Going On Out There?

Posted by Abel Avram on Sep 05, 2008 08:26 AM

Community
Agile
Topics
Adopting Agile ,
Agile Techniques
Tags
Surveys ,
agile2008

In this presentation filmed during Agile 2008, Scott Ambler talks about actual data resulting from surveys made during 2006-2008, showing how Agile is perceived and implemented within organizations. Some of the topics surveyed are: the adoption rate of Agile, the effectiveness of Agile approaches, the effectiveness of various techniques.

Watch:  Agile in Practice: What Is Actually Going On Out There?(37 min)

Scott has conducted a series of surveys for Dr. Dobb’s Journal over the last three years on various aspects of Agile development. The results show how Agile is understood and used by people, how many are using Agile, what techniques they are using, etc.

Some of the results presented by Scott are:

  • 69% of the organizations have adopted an Agile technique.
  • Project success rate was: 83% for co-located teams, 72% for near located teams, 60% for far located teams.
  • 60% of IT managers and developers consider that repeatable results are more important that repeatable processes.

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.

11 comments

Reply

Agile is the new waterfall by Dan Tines Posted Sep 6, 2008 3:01 PM
Re: Agile is the new waterfall by David Zhu Posted Sep 6, 2008 8:11 PM
Re: Agile is the new waterfall by Shih-gian Lee Posted Sep 6, 2008 10:39 PM
Dr. Dobb's link is dead by Michel Löhr Posted Sep 9, 2008 7:59 AM
Re: Dr. Dobb's link is dead by Deborah Hartmann Posted Sep 15, 2008 10:03 AM
Excellent! Very enlightening! by Olivier Gourment Posted Sep 10, 2008 8:45 PM
Re: Excellent! Very enlightening! by Carlos Ortega Posted Sep 16, 2008 1:46 AM
Re: Excellent! Very enlightening! by Olivier Gourment Posted Sep 16, 2008 2:34 PM
Re: Excellent! Very enlightening! by Perry Hertler Posted Sep 23, 2008 1:24 PM
Do you know a report based in a higher number of companies? by A A Posted Sep 13, 2008 3:34 PM
Re: Do you know a report based in a higher number of companies? by Deborah Hartmann Posted Sep 15, 2008 9:42 AM
  1. Back to top

    Agile is the new waterfall

    Sep 6, 2008 3:01 PM by Dan Tines

    ...and somewhat cultish.

  2. Back to top

    Re: Agile is the new waterfall

    Sep 6, 2008 8:11 PM by David Zhu

    Why said like that?
    Our team management is changing to Agile, is there no difference with waterfall??

  3. Back to top

    Re: Agile is the new waterfall

    Sep 6, 2008 10:39 PM by Shih-gian Lee

    Why said like that?
    Our team management is changing to Agile, is there no difference with waterfall??


    There is a difference. But, many organizations use Agile in waterfall way. The sad part is they don't know about it.

  4. Back to top

    Dr. Dobb's link is dead

    Sep 9, 2008 7:59 AM by Michel Löhr

    Can this link be fixed?

  5. Back to top

    Excellent! Very enlightening!

    Sep 10, 2008 8:45 PM by Olivier Gourment

    Overall, the first half of the presentation is a must-hear for anybody who is wondering why they should care about Agile/Lean.
    Scott presents very interesting results of a Dr Dobbs 2008 survey:

  6. - more managers think they are doing Agile than their developers
  7. - success rate is higher with colocated teams than distributed teams

  8. - Agile teams write as many documents as their traditional counterparts


  9. THANKS!



    PS: I completely missed the point with Modeling and TDD. Can anybody shed some light on this?

  • Having a look to the "Agile Project Success Rates %" slide there are 539 agile projects, which combined with the previous ones gave me a maximum of 125 companies (not hundreds by the way). I might miscalculated it, but if I am true, do you know any other report based on a higher number of surveys, please?

    Cheers!

  • This recent news item points you to a recent, larger survey by VersionOne software. Their sample did include companies NOT using their software.

  • Back to top

    Re: Dr. Dobb's link is dead

    Sep 15, 2008 10:03 AM by Deborah Hartmann

    Sorry, not sure which link you mean. Please email me the url at deborah@infoq.com and I'll get it out there. Thanks!

  • Back to top

    Re: Excellent! Very enlightening!

    Sep 16, 2008 1:46 AM by Carlos Ortega

    I think Scott tried to relate or compare the concepts of Design using UML / Modeling techniques vs the generation of the Design by using Test Driven Development and Refactoring.

    The basic idea in this sense is that before agile practices, the design was made by taking the requirements as input, applied some techniques and generate the design (and architecture) using models/diagrams as the main output artifact.
    While if you use TDD, it comes that the design emerges as consequence of the continuous application and evolution of doing Unit Testing and Refactoring to the code you write.

  • Back to top

    Re: Excellent! Very enlightening!

    Sep 16, 2008 2:34 PM by Olivier Gourment

    Thank you Carlos. What is Scott's point regarding these practices in real life? Why oppose both techniques?



    Specifying tests should not prevent people from creating some models? I agree that tests are more important than models, but models are still very often required as an aid to development, team members coordination and maintenance...



    I guess I will have to listen to that part again... :-)

  • Back to top

    Re: Excellent! Very enlightening!

    Sep 23, 2008 1:24 PM by Perry Hertler

    Olivier,

    I believe the point Scott was making is that since the majority of professing agilists don't do TDD then TDD is not a good practice and the converse is true for modeling.

    The person in audience questioned the validity of the survey because the majority of respondents do detailed documentation. In my opinion, that is a good question and Scott didn't answer it to my satisfaction.

    Maybe Scott's point is that the agile practices that are not adopted by the masses should be cut?

  • Educational Content

    JRuby: The Pain of Bringing an Off-Platform Dynamic Language to the JVM

    Charles Nutter discusses bringing JRuby to the JVM, why Ruby is hard to implement, JIT compilation, precompilation, core Ruby implementation, Java library access, library challenges and future plans.

    Performance Anti-Patterns in Database-Driven Applications

    Alois Reitbauer specifies several architectural anti-patterns that one should stay away from and which can downgrade an application’s performance.

    Making TDD Stick: Problems and Solutions for Adopters

    Teams in large organizations still struggle to adopt TDD. In this article Mark Levison shares problems he uncovered when he surveyed teams, and his own strategy to introduce TDD into an organization.

    Testing is Overrated

    In this talk from RubyFringe, Luke Francl asks: is developer-driven testing really the best way to find software defects? Or is the emphasis on testing and test coverage barking up the wrong tree?

    VM Optimizations for Language Designers

    John Pampuch discusses the HotSpot compiler, the history of Java performance, HotSpot development philosophies and challenges, optimization, JVM library improvements, and tips for better performance.

    Keith Braithwaite, an Agile Skeptic

    In this interview, Keith Braithwaite, an Agile developer, consultant and trainer, says that we should show a good deal of skepticism towards today’s Agile practice.

    Workflow Orchestration Using Spring AOP and AspectJ

    This article demonstrates how to build and orchestrate highly configurable and extensible yet light-weight embedded process flow using AOP techniques with Spring AOP and Aspect J.

    Embrace Uncertainty

    Jeff Patton explains why one needs to embrace uncertainty in order to succeed with his/her Agile project and how to avoid some of the common mistakes leading to project failure.