Editing Agile software development (section)

===Measuring agility===

==== Internal assessments ====
The ''Agility measurement index'', amongst others, rates developments against five dimensions of product development (duration, risk, novelty, effort, and interaction).<ref>{{cite conference |doi=10.1145/1185448.1185509|book-title=ACM-SE 44 Proceedings of the 44th annual Southeast regional conference |page=271 |year=2006 |last=Datta |first=Subhajit |isbn=1595933158 |title=Agility measurement index: a metric for the crossroads of software development methodologies}}</ref> Other techniques are based on measurable goals<ref>{{cite web|url=http://www.smr.co.uk/presentations/measure.pdf|title=Assessing Agility|author=Peter Lappo|author2=Henry C.T. Andrew|access-date=6 June 2010|archive-url=https://web.archive.org/web/20090915040232/http://www.smr.co.uk/presentations/measure.pdf|archive-date=15 September 2009|url-status=dead}}</ref> and one study suggests that [[Velocity (software development)|velocity]] can be used as a metric of agility. There are also agile self-assessments to determine whether a team is using agile software development practices (Nokia test,<ref>{{cite web|url=http://agileconsortium.blogspot.com/2007/12/nokia-test.html|title=Nokia test, A scrum-specific test|author=Joe Little|date=2 December 2007|publisher=Agileconsortium.blogspot.com|access-date=6 June 2010}}</ref> Karlskrona test,<ref>{{cite web|url=http://mayberg.se/learning/karlskrona-test|title=Karlskrona test, A generic agile adoption test|author=Mark Seuffert|author2=Mayberg, Sweden|publisher=Mayberg.se|access-date=5 April 2014}}</ref> 42 points test).<ref>{{cite web|url=http://www.allaboutagile.com/how-agile-are-you-take-this-42-point-test/|title=How Agile Are You? (Take This 42 Point Test)|publisher=allaboutagile.com/|access-date=3 April 2014|archive-url=https://web.archive.org/web/20140505223335/http://www.allaboutagile.com/how-agile-are-you-take-this-42-point-test/|archive-date=5 May 2014|url-status=dead}}</ref>

====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&nbsp;... 93% stated that productivity was better or significantly better&nbsp;... 88% stated that quality was better or significantly better&nbsp;... 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&nbsp;... No change in productivity was reported by 34% of respondents and 60% reported increased productivity&nbsp;... 66% [responded] that the quality is higher&nbsp;... 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>