Студопедия
Случайная страница | ТОМ-1 | ТОМ-2 | ТОМ-3
АрхитектураБиологияГеографияДругоеИностранные языки
ИнформатикаИсторияКультураЛитератураМатематика
МедицинаМеханикаОбразованиеОхрана трудаПедагогика
ПолитикаПравоПрограммированиеПсихологияРелигия
СоциологияСпортСтроительствоФизикаФилософия
ФинансыХимияЭкологияЭкономикаЭлектроника

Experience and adoption

Scrum-ban | Rapid application development | The James Martin RAD Methodology | Dynamic systems development method | Four stages of the DSDM V4.2 Project life-cycle | Unified Process | Iterative and Incremental | Extreme programming | Agile software development | Quality focus |


Читайте также:
  1. Experience
  2. Foreign experience of resource saving technologies
  3. Previous Experience

Surveys[edit]

One of the early studies reporting gains in quality, productivity, and business satisfaction by using Agile methods was a survey conducted by Shine Technologies from November 2002 to January 2003.[38] A similar survey, the State of Agile, is conducted every year starting in 2006 with thousands of participants from around the software development community. The State of Agile survey tracks trends on the benefits of agile, trends, lessons learned, and preferred practices and agile methodologies. From the 2013 results released in January 2014, the survey concludes that 73% of respondents say agile software helps them complete software projects faster; 92% say agile improves their ability to manage changing customer priorities; and 87% say agile improves their development team's productivity.[39] Yet another survey conducted in 2006 by Scott Ambler, the Practice Leader for Agile Development with IBM Rational's Methods Group reported similar benefits.[40] Others claim that agile development methods are still too young to require extensive academic proof of their success.[41]

Large-scale and distributed Agile[edit]

Large-scale agile software development remains an active research area.[42][43] Agile development has been widely seen as being more suitable for certain types of environment, including small teams of experts.[18][44]:157 Positive reception towards Agile methods has been observed in Embedded domain across Europe in recent years.[45]

Some things that may negatively impact the success of an agile project are:

· Large-scale development efforts (>20 developers), though scaling strategies[43] and evidence of some large projects[46] have been described.

· Distributed development efforts (non-colocated teams). Strategies have been described in Bridging the Distance [47] and Using an Agile Software Process with Offshore Development. [48]

· Forcing an agile process on a development team.[49]

· Mission-critical systems where failure is not an option at any cost (e.g. software for avionics).

The early successes, challenges and limitations encountered in the adoption of agile methods in a large organization have been documented.[50]

Agile offshore[edit]

In terms of outsourcing agile development, Michael Hackett, senior vice president of LogiGear Corporation has stated that "the offshore team... should have expertise, experience, good communication skills, inter-cultural understanding, trust and understanding between members and groups and with each other."[51][52]

Common Agile Pitfalls[edit]

Teams implementing Agile often face difficulties transitioning from more traditional methods such as Waterfall development. Below are problems often faced by teams implementing Agile processes:


Дата добавления: 2015-08-27; просмотров: 77 | Нарушение авторских прав


<== предыдущая страница | следующая страница ==>
Comparison with other methods| Fixed time, resources, scope and quality

mybiblioteka.su - 2015-2024 год. (0.006 сек.)