Editing Agile software development (section)

==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&nbsp;... 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 
 |url-status=dead 
 |archive-url=https://web.archive.org/web/20160327214807/http://www.gilb.com/Project-Management 
 |title=Evolutionary Project Management (Original page, external archive) 
 |archive-date=27 March 2016 
 |publisher=Gilb 
}}</ref><ref>{{cite web
|url=http://concepts.gilb.com/tiki-page.php?pageName=Evolutionary-Project-Management 
|title=Evolutionary Project Management (New page)
|access-date=2017-04-30
|publisher=Gilb}}</ref> and [[adaptive software development]]<ref name="edmonds1974">{{Cite journal
|last=Edmonds
|first=E. A.
|year=1974
|title=A Process for the Development of Software for Nontechnical Users as an Adaptive System
|journal=General Systems
|volume=19
|pages=215–18}}</ref> emerging in the early 1970s.<ref>{{Cite journal|last=Gilb|first=Tom|s2cid=33902347|date=1981-04-01|title=Evolutionary development|journal=ACM SIGSOFT Software Engineering Notes|language=en|volume=6|issue=2|pages=17|doi=10.1145/1010865.1010868}}</ref>

During the 1990s, a number of ''lightweight'' software development methods evolved in reaction to the prevailing ''heavyweight'' methods (often referred to collectively as [[Waterfall model|''waterfall'']]) that critics described as overly regulated, planned, and [[Micromanagement|micromanaged]].<ref>{{Citation |title=Heavyweight project organizationHEAVYWEIGHT PROJECT ORGANIZATION |date=2000 |url=https://doi.org/10.1007/1-4020-0612-8_400 |encyclopedia=Encyclopedia of Production and Manufacturing Management |pages=261–262 |editor-last=Swamidass |editor-first=P. M. |place=Boston, MA |publisher=Springer US |language=en |doi=10.1007/1-4020-0612-8_400 |isbn=978-1-4020-0612-8 |access-date=2022-06-22|url-access=subscription }}</ref> These lightweight methods included: [[rapid application development]] (RAD), from 1991;<ref>{{cite book | title=Rapid Application Development | publisher=Macmillan | author=Martin, James | year=1991 | isbn=978-0-02-376775-3 | url=https://archive.org/details/rapidapplication00mart }}</ref><ref>{{cite book | title=Inside RAD: How to Build a Fully Functional System in 90 Days or Less | publisher=McGraw-Hill |author1=Kerr, James M. |author2=Hunter, Richard | year=1993 | page=3 | isbn=978-0-07-034223-1}}</ref> the [[Unified Process|unified process]] (UP) and [[dynamic systems development method]] (DSDM), both from 1994; [[Scrum (software development)|Scrum]], from 1995; Crystal Clear and [[extreme programming]] (XP), both from 1996; and [[feature-driven development]] (FDD), from 1997. Although these all originated before the publication of the ''Agile Manifesto'', they are now collectively referred to as agile software development methods.<ref name="LarmanGuide">{{Cite book 
|last=Larman 
|first=Craig 
|year=2004 
|title=Agile and Iterative Development: A Manager's Guide 
|publisher=Addison-Wesley 
|isbn=978-0-13-111155-4 
|page=27 
}}</ref>

Already since 1991 similar changes had been underway in [[Agile manufacturing|manufacturing]]<ref>Iacocca Institute (1991). "21st Century Manufacturing Enterprise Strategy: An Industry Led View". Iacocca Institute, Lehigh University, Bethlehem, PA.</ref><ref>Presley, A., J. Mills and D. Liles (1995). "Agile Aerospace Manufacturing". Nepcon East 1995, Boston.</ref> and [[Agile management|management thinking]]<ref>{{Cite journal |last=Sanchez |first=Luis |date=November 2010 |title=A Review of Agile Manufacturing Systems |url=https://www.researchgate.net/publication/261652716 |journal=International Journal of Production Research |issue=39(16):3561-3600}}</ref> derived from [[Lean manufacturing|Lean management]].

In 2001, seventeen software developers met at a resort in [[Snowbird, Utah|Snowbird]], [[Utah]] to discuss lightweight development methods. They were: [[Kent Beck]] (Extreme Programming), [[Ward Cunningham]] (Extreme Programming), [[Dave Thomas (programmer)|Dave Thomas]] ([[The Pragmatic Programmer|Pragmatic Programming]], Ruby), [[Jeff Sutherland]] (Scrum), [[Ken Schwaber]] (Scrum), [[Jim Highsmith]] (Adaptive Software Development), [[Alistair Cockburn]] (Crystal), [[Robert C. Martin]] ([[SOLID]]), [[Mike Beedle]] (Scrum), Arie van Bennekum, [[Martin Fowler (software engineer)|Martin Fowler]] ([[OOAD]] and [[UML]]), James Grenning, [[Andy Hunt (author)|Andrew Hunt]] (Pragmatic Programming, Ruby), [[Ron Jeffries]] (Extreme Programming), [[Jon Kern]], Brian Marick (Ruby, [[Test-driven development]]), and [[Stephen J. Mellor|Steve Mellor]] ([[Shlaer–Mellor method|OOA]]). The group, The Agile Alliance, published the ''Manifesto for Agile Software Development''.<ref name="AgileManifesto" />

In 2005, a group headed by Cockburn and Highsmith wrote an addendum of [[project management]] principles, the PM Declaration of Interdependence,<ref>{{cite web|url=http://pmdoi.org|title=Declaration of Interdependence|last=Anderson|first=David|year=2005|archive-url=https://web.archive.org/web/20180127094805/http://www.pmdoi.org/|archive-date=27 January 2018|url-status=dead|access-date=4 October 2018}}</ref> to guide software project management according to agile software development methods.

In 2009, a group working with Martin wrote an extension of [[software development]] principles, the [[Software craftsmanship|Software Craftsmanship Manifesto]], to guide agile software development according to [[professional]] conduct and mastery.

In 2011, the Agile Alliance created the ''Guide to Agile Practices'' (renamed the ''Agile Glossary'' in 2016),<ref>{{Cite news|url=https://www.agilealliance.org/how-you-can-help-the-agile-alliance-help-you/|title=How You Can Help Agile Alliance Help You|last=McDonald|first=Kent|date=1 November 2016|work=Agile Alliance Blog|access-date=4 July 2017}}</ref> an evolving [[Open source|open-source]] compendium of the working definitions of agile practices, terms, and elements, along with interpretations and experience guidelines from the worldwide community of agile practitioners.