0% found this document useful (0 votes)
2K views

2010 State of Agile Development Survey Results

The fifth annual "State of Agile Development" survey was conducted between August 11th and October 31, 2010. 40% of respondents work at companies that have been practicing agile for over 2 years. The median size of development organizations was 80.

Uploaded by

Peter Saddington
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2K views

2010 State of Agile Development Survey Results

The fifth annual "State of Agile Development" survey was conducted between August 11th and October 31, 2010. 40% of respondents work at companies that have been practicing agile for over 2 years. The median size of development organizations was 80.

Uploaded by

Peter Saddington
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10
“WYERSIONONE STATE AGILE || 2010 SURVEY 5TH ANNUAL INTRODUCTION A qile The fifth annual “State of Agile Development” survey was conducted between August ith and October 31, 2010. Sponsored by VersionOne, respondents were recruited from mailing lists, websites and other software development industry fora, The survey data includes information from 4,770 participants from 91 countries. The data was analyzed and prepared into a summary report by Analysis.Net Research, an independent survey consultancy. «Gai 2010 ' »y_WVERSIONONE | RESPONDENT ZZ DEMOGRAPHICS CURRENT COMPANY POSITION Respondents were most commonly project managers, followed by other ‘managerial staff involved in software development. 1g | 9 a EXPERIENCE WITH AGILE HOW MANY YEARS HAS HOW MANY YEARS, DEVELOPMENT PRACTICES YOUR COMPANY BEEN HAVE YOU BEEN knowledgeable about PRACTICING AGILE? PRACTICING AGILE? jathat they 40% of respondent Nearly half of respondents have remely knowledgeable” that have been prac 92 years of agile 2 years. © ccrnesety ewowLenceAate © Less rian rvear @ css rHanrvear © MovERATELY KNOWLEDGEABLE © 1zveA8s © rzveans @ kwowieoceaaLe © zsveans © 2 sveans sJ@if 2010 ofS 2010 f 2y_ \WVERSIONONE aA | AGILE IN | THE ENTERPRISE AGILE ADOPTION The median size of development 0-20 20-50 50-250 250+ WHO DECIDES? 90% manage VP/Dir. Of Development Development Manager Project Manager clo/cto Team Lead Developer President/CEO/COO Architect Product Manager Consultant/Trainer Other irstat | aastester | Mf oO 2 g 3 a x g sJ@if 2010 «Gai 2010 ' »y_WVERSIONONE HOW MANY TEAMS ADOPTED AGILE? s are scaling their agile initiatives ~ 29% of respondents O+ agile teams. @ o-sTEAMS @ 5-10 TEAMS, @ 10-25 TEAMS @ 25+ TEAMS NUMBER OF SEPARATE SITES/LOCATIONS USING AGILE Most companies had only 1to 2 sites using agile 0-2 @ 25 @ 5-10 @ 10+ @ PERCENTAGE OF COMPANY’S. PROJECTS USING AGILE About half of s in respondents’ companies use agile o-20% 20-50% 50.95% 95-100% shi} 2010 ar sft 2010 f 2y. SWVERSIONONE Se F us | D ETHODS & PRACTICES ge 2 7 2 AGILE METHODOLOGY MOST CLOSELY FOLLOWED variants were by far the most common agile gies employed. scRUM SCRUM/XP HYBRID ‘CUSTOM HYBRID OTHER EXTREME PROGRAMMING (XP) DONT KNOW ‘SCRUMBAN LEAN FEATURE DRIVEN DEVELOPMENT (FOD) AGILEUP AGILE TECHNIQUES EMPLOYED Core agile tenets iteration plan testing were respondents, Continuous integration Automated Builds velocity Refactoring oaing Standards Test Driven Development (TDD) ‘Open Workareas Digital Taskboara sJ@if 2010 suMvEY 2010 A LEADING CAUSES OF FAILED AGILE PROJECTS Lack of experience with agile methods Company philosophy/culture at odds with core agile values Don't know ermal pressure to follow tractional waterfall practices Lack of cultural transition Lack of management support Unwilingness of the team ‘New to agile/naver't completed an agile project Insufficient taining 22” , of respondents reported they had not experienced failed agile project, BARRIERS TO FURTHER AGILE ADOPTION As with any significant process change, the biggest barrier seen to the adoption of Agile Development was the ability to change organizational culture followed by general resistance to change, S1* II | Abii to change organizational culture a aT a a 2. a 1 TS" edge consaris 12* None. 6B otter CGoneralresistance to change Availabilty of personnel with necessary sis Management support Project comolty or size ‘Customer collaboration Confidence in abit to scale agile Perceived te to transition sumvey 2010 2 SWVERSIONONE Se 10% 15% GREATEST CONCERNS, ABOUT ADOPTING AGILE ‘The most common concerns listed by respondents when they were considering deploying agile practices was a loss of management control, management opposed to change or concerns regarding lack of upfront planning, Lostofmanagementcontol I 36> Lackotvotont pleco 33 Management opposed to change EN 52° Lackotdocunentation NN 28% Lackotpredetabity [IN 27> Lackolengineeing dicoine III 25% Development team opposed to change NN) 21° Gunity ofersineeng talent ENE 16 Other Inabty to sale Regulatory comolance Reduced sftvare quality No concerns vewrnoncem 5 sft 2010 f “WVERSIONONE REASONS FOR ADOPTING AGILE © Notimporant at ll @ Somevhatimpertant © Very important @ HighestImportance ccolate tine vatet | ‘Simpify Development Process Enhance Software Maintanabilty/Extensibilty Improved Team Morale OVERALL CONSENSUS REGARDING ADOPTION OF AGILE elt 66” FASTER | SAME ake tae) Seaton) sJ@if 2010 sft 2010 BROUGH 2y. SWVERSIONONE BENEFITS OBTAINED FROM IMPLEMENTING AGILE While the most common reason for adopting agile was improved t market, respondents cited that they actually experienced improved managerial abilities as the ductivity and time to biggest benoft of implementing age © vorticon @ Hihiione @ Vase @ Soden @ imens © Sint tems mero Project iby Inosve Team Mole cena Tevato Mat Inna Potty Enc Stare Quay Sire Deleon Proce Improvfnrease Engineering Die Enhance Software Maintainabilly/Extensibility 70% sf pends showed ser OUTSOURCED Prod teeta mat DEVELOPMENT PROJECTS Manage Distributed Teams Reduce Cost 32” try DYN shi} 2010 concn 7 suite 2010 BROUGHT 2. )WVERSIONONE | TOOLS SPECIFIC TOOLS CURRENTLY USED Excel VersionOne Microsoft Project Jira/Greenhopper Other HP Quality Center Microsoft TFS In-house/Custom Google Docs Vendor ¥ Bugzilla IBM ClearCase Rational Vendor X XPlanner IBM Rational Team Concert Mingle Target Process g x g w 40% 50 60% “PREVIOUSLY VENDORS (ND “Y" REGUESTED NOT TO BE IDENTIFIED IN STATE OF AGILE SURVEYS, “RESPONDENTS WERE ALLOWED TO ANSWER FOR MULTIPLE TOOLS shtil® 2010 womocan &

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy