December 22, 2011 - FILED UNDER Agile Business

10 years of Agile: How are we doing?

It’s been ten years since the writing of the Agile Manifesto. Let’s take a look and see how far we have come.

Here are some of findings from a survey by VersonOne to see how well Agile has been adopted. The information was collected from 4,770 participants from 91 different countries. We’re all pretty busy these days, so instead of checking out VersonOne’s entire survey I’ve pulled out some highlights listed below:

Who has adopted Agile?

  • Not surprisingly, the majority of individuals who’ve adopted Agile are project managers (19%) followed by development managers at 10%. 22% of VPs/Directors of Development are leading their companies to begin adopting Agile into their workplace. 32% of enterprise companies with 250 or more employees are the forerunners of the Agile movement. The majority of companies had only 1 or 2 sites using Agile while 29% of participants stated that their company had 10 or more Agile teams.

    Whos Adopted Agile

    Whos Adopted Agile

What’s the average experience?

  • The majorities of respondents have been practicing Agile for 1-5 years and are either extremely or moderately knowledgeable about Agile development practices.

Which Methodology is used the most?

  •  Scrum methodologies took the lead at 58%. For those a little less familiar with Agile, Scrum refers to an incremental, iterative framework for project management. The use of scrum methodology is to help focus on the management of software development projects, and can even be used to assist in running software maintenance teams or even just as a general project/program management approach.

Leading Causes of Failed Agile Projects:

  • Many Agile products are unsuccessful because individuals within the organization lack experience with the method. 14% of those surveyed responded that the largest reason why their Agile projects failed is because there existed a lack of experience with Agile methods. Other leading causes for failure included the philosophy and or culture of the company conflicting with the values of being Agile as well as external pressure to follow traditional waterfall practices.
Leading Causes of Failed Agile Projects

Leading Causes of Failed Agile Projects

 What’s the Benefit from Implementing Agile?

  • After implementing Agile in the workplace, respondents stated that their company experienced improved managerial abilities as the biggest benefit of implementing Agile.

Although Agile has not been implemented or recognized in every workplace, in the ten years since its creation, Agile has quickly moved to the forefront of the corporate structure debate. It should be very exciting to see over the next few years how Agile adoption plays out.

Your Turn

 Have you implemented Agile into your workplace?

 How has it worked out for you?

Related

7sins_cta2_black bg

  • Scott

    If you want some historical perspective, check out what my friend @jimhighsmith, who wrote the Agile Manifesto website, has to offer on the subject
    “Celebrating 10 years of Agile, my 2001 interview with Martin Fowler” bit.ly/mZaT2B

  • copt

    You’re never really going to succeed with agile development unless you have a serious RAD platform to drive the process. We’ve found that Ebase Xi platform to be a key enabler (before that we were just speeding stuff up, never really making a step change). Xi is a true RAD platform (for browser based apps). Server uns on windows and unix. WYSIWYG UI development, workflow processing, out of the box integration with pretty much anything (databases, web services, you name it) and a built-in english-like scripting language to simplify business logic (no need to get into low level coding at all). The UI development part alone is a masterpiece…they’ve managed to abstract the whole CSS thing and make page layout a synch for non-CSS folks. They have a free Community Edition plus a very low price run-time concurrency model. Very cool. The latest version adds in mobile app/rich client development too.