Content deleted Content added
m Reverted 1 edit by EmiNEMilLemanSusanAnarBANM4Kurs (talk) to last revision by ClueBot NG |
|||
| (13 intermediate revisions by 9 users not shown) | |||
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
Line 153:
No matter which development method is followed, every team should include a [[customer representative]] (known as ''product owner'' in [[Scrum (software development)|Scrum]]). This representative is agreed by stakeholders to act on their behalf and makes a personal commitment to being available for developers to answer questions throughout the iteration. At the end of each iteration, the [[project stakeholder]]s together with the customer representative review progress and re-evaluate priorities with a view to optimizing the [[Rate of return|return on investment]] (ROI) and ensuring alignment with customer needs and company goals. The importance of stakeholder satisfaction, detailed by frequent interaction and review at the end of each phase, is why the approach is often denoted as a [[Customer centricity|customer-centered methodology]].<ref>{{Cite book |last1=Jain |first1=Parita |last2=Sharma |first2=Arun
|last3=Ahuja |first3=Laxmi |title=2018 7th International Conference on Reliability, Infocom Technologies and Optimization (Trends and Future Directions) (ICRITO) |chapter=The Impact of Agile Software Development Process on the Quality of Software Product |date=August 2018
==== Information radiator ====
Line 496:
*{{cite book |first1=Torgeir |last1=Dingsøyr |first2=Tore |last2=Dybå |first3=Nils Brede |last3=Moe |title=Agile Software Development: Current Research and Future Directions |url=https://books.google.com/books?id=JRhGAAAAQBAJ |date=2010 |publisher=Springer |isbn=978-3-642-12575-1 }}
*{{cite book|last=Fowler|first=Martin|chapter=Is Design Dead?|chapter-url=http://www.martinfowler.com/articles/designDead.html|pages=[https://archive.org/details/extremeprogrammi0000succ/page/3 3–18]|editor-first=Giancarlo|editor-last=Succi|editor2-first=Michele|editor2-last=Marchesi|title=Extreme Programming Examined|year=2001|publisher=Addison-Wesley|isbn=978-0-201-71040-3|ref={{harvid|Succi|Marchesi|2001}}|url=https://archive.org/details/extremeprogrammi0000succ/page/3}}
*{{cite journal |first1=Craig |last1=Larman |last2=Basili |first2=Victor R. |s2cid=9240477 |title=Iterative and Incremental Development: A Brief History |journal=IEEE Computer |volume=36 |issue=3 |pages=47–56 |date=June 2003 |doi=10.1109/MC.2003.1204375 |bibcode=2003Compr..36f..47L }}
*{{cite journal | publisher = MITRE | title =Handbook for Implementing Agile in Department of Defense Information Technology Acquisition | journal =The Mitre Corporation | url=https://www.mitre.org/publications/technical-papers/handbook-for-implementing-agile-in-department-of-defense-information-technology-acquisition| date =8 September 2013 | last1 =Casagni | first1 =Michelle | last2 =Benito | first2 =Robert | last3 =Mayfield | first3 =Kathleen M. | last4 =Northern | first4 =Carlton }}
*{{cite book|first=Alan|last=Moran|title=Managing Agile: Strategy, Implementation, Organisation and People|url=https://books.google.com/books?id=I6l_BwAAQBAJ|date=2015|publisher=Springer|isbn=978-3-319-16262-1}}
Line 514:
* [https://www.agilealliance.org/agile101/agile-glossary/ Agile Glossary] of the Agile Alliance
* [http://martinfowler.com/articles/newMethodology.html The New Methodology] - [[Martin Fowler (software engineer)|Martin Fowler]]'s description of the background to agile methods
| |||