Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Agile software development
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
====Public surveys==== One of the early studies reporting gains in quality, productivity, and business satisfaction by using agile software developments methods was a survey conducted by Shine Technologies from November 2002 to January 2003.<ref>{{cite web|url=http://www.shinetech.com/attachments/104_ShineTechAgileSurvey2003-01-17.pdf|title=Agile Methodologies Survey Results|date=January 2003|publisher=Shine Technologies|archive-url=https://web.archive.org/web/20100821225423/http://www.shinetech.com/attachments/104_ShineTechAgileSurvey2003-01-17.pdf|archive-date=21 August 2010|url-status=dead|access-date=3 June 2010|quote=95% stated that there was either no effect or a cost reduction ... 93% stated that productivity was better or significantly better ... 88% stated that quality was better or significantly better ... 83% stated that business satisfaction was better or significantly better}}</ref> A similar survey, the ''State of Agile'', is conducted every year starting in 2006 with thousands of participants from around the software development community. This tracks trends on the perceived benefits of agility, lessons learned, and good practices. Each survey has reported increasing numbers saying that agile software development helps them deliver software faster; improves their ability to manage changing customer priorities; and increases their productivity.<ref>{{cite web|url=http://stateofagile.versionone.com/why-agile/|title=2013 State of Agile report: Why Agile?|date=27 January 2014|publisher=stateofagile.com|archive-url=https://web.archive.org/web/20140828012224/http://stateofagile.versionone.com/why-agile/|archive-date=28 August 2014|url-status=dead|access-date=13 August 2014}}</ref> Surveys have also consistently shown better results with agile product development methods compared to classical project management.<ref>[http://www.status-quo-agile.net Status Quo Agile], Second study on success and forms of usage of agile methods. Retrieved 1 July 2015</ref><ref>{{cite web|url=http://www.drdobbs.com/architecture-and-design/191800169;jsessionid=2QJ23QRYM3H4PQE1GHPCKH4ATMY32JVN?queryText=agile+survey|title=Survey Says: Agile Works in Practice|last=Ambler|first=Scott|author-link=Scott Ambler|date=3 August 2006|work=Dr. Dobb's|access-date=3 June 2010|quote=Only 6% indicated that their productivity was lowered ... No change in productivity was reported by 34% of respondents and 60% reported increased productivity ... 66% [responded] that the quality is higher ... 58% of organizations report improved satisfaction, whereas only 3% report reduced satisfaction.}}</ref> In balance, there are reports that some feel that agile development methods are still too young to enable extensive academic research of their success.<ref>{{cite web|url=http://www.agilemodeling.com/essays/proof.htm|title=Answering the "Where is the Proof That Agile Methods Work" Question|date=19 January 2007|publisher=Agilemodeling.com|access-date=2 April 2010}}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)