Content deleted Content added
m Added a recent statistic Tags: Reverted Visual edit |
m Reverted 1 edit by EmiNEMilLemanSusanAnarBANM4Kurs (talk) to last revision by ClueBot NG |
||
| (5 intermediate revisions by 4 users not shown) | |||
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 363:
==Experience and adoption==
Although agile software development methods can be used with any programming paradigm or language in practice, they were originally closely associated with object-oriented environments such as Smalltalk, Lisp and later Java, C#. The initial adopters of agile methods were usually small to medium-sized teams working on unprecedented systems with requirements that were difficult to finalize and likely to change as the system was being developed.
===Measuring agility===
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}}
| |||