Content deleted Content added
All of the external links are at best close to spam and should perhaps be removed; removing just the most blatant ones |
m punc fix |
||
Line 10:
* Responding to change over following a plan
The practitioners cite inspiration from new practices at the time including [[extreme programming]], [[Scrum (software development)|scrum]], [[dynamic systems development method]], [[adaptive software development]], and being sympathetic to the need for an alternative to documentation
Many software development practices emerged from the agile mindset. These agile-based practices, sometimes called ''Agile'' (with a capital A),<ref>{{cite web|url=https://www.rallydev.com/blog/engineering/agile-capital-vs-agile-lowercase |title=Agile With a Capital "A" Vs. agile With a Lowercase "a" |last=Rally |date=2010 |archive-url=https://web.archive.org/web/20160105105258/https://www.rallydev.com/blog/engineering/agile-capital-vs-agile-lowercase |archive-date=5 January 2016 |url-status=unfit |access-date=9 September 2015 }}</ref> include requirements, discovery, and solutions improvement through the collaborative effort of [[Self-organizing communities|self-organizing]] and [[cross-functional team|cross-functional]] teams with their [[Customer|customer(s)]]/[[End user|end user(s)]].{{sfn|Collier|2011}}<ref name="WhatIsAgile">{{cite web|url = http://www.agilealliance.org/the-alliance/what-is-agile/|title = What is Agile Software Development?|date = 8 June 2013|access-date = 4 April 2015|publisher = Agile Alliance}}</ref>
While there is much [[anecdotal evidence]] that the agile mindset and agile-based practices improve the software development process, the empirical evidence is limited and less than conclusive.<ref>{{cite journal|last1=Dybå|first1=Tore|last2=Dingsøyr|first2=Torgeir|title=Empirical studies of agile software development: A systematic review|journal=Information and Software Technology|date=1 August 2008|volume=50|issue=9–10|pages=833–859|doi=10.1016/j.infsof.2008.01.006|s2cid=2244031 |language=en|issn=0950-5849}}</ref><ref>{{cite journal|last1=Lee|first1=Gwanhoo|last2=Xia|first2=Weidong|s2cid=26477249|date=2010|title=Toward Agile: An Integrated Analysis of Quantitative and Qualitative Field Data on Software Development Agility|journal=MIS Quarterly|volume=34|issue=1|pages=87–114|doi=10.2307/20721416|jstor=20721416}}</ref><ref>{{cite journal |last1=Kroll |first1=J. |last2=Richardson |first2=I. |last3=Prikladnicki |first3=R. |last4=Audy |first4=J. L. |date=2018 |title=Empirical evidence in follow the Sun software development: A systematic mapping study |url=https://doi.org/10.1016/j.infsof.2017.08.011 |journal=Information and Software Technology |volume=93 |pages=30–44 | doi=10.1016/j.infsof.2017.08.011|hdl=10344/6233 |hdl-access=free }}</ref>
Line 19:
==History==
[[Iterative and incremental development|Iterative and incremental software development methods]] can be traced back as early as 1957,<ref name="craig2003">[[Gerald M. Weinberg]], as quoted in {{harvnb|Larman|Basili|2003|pp=47–56}}: "We were doing incremental development as early as 1957 in Los Angeles, under the direction of Bernie Dimsdale at [[Service Bureau Corporation|IBM's Service Bureau Corporation]]. He was a colleague of [[John von Neumann]], so perhaps he learned it there, or assumed it as totally natural. I do remember Herb Jacobs (primarily, though we all participated) developing a large simulation for Motorola, where the technique used was, as far as I can tell ... All of us, as far as I can remember, thought waterfalling of a huge project was rather stupid, or at least ignorant of the realities. I think what the waterfall description did for us was make us realize that we were doing something else, something unnamed except for 'software development.'"</ref> with evolutionary project management<ref name="EvolutionaryProjectManagement">{{cite web
|url=https://www.gilb.com/Project-Management
|access-date=2017-04-30
| |||