Editing Agile software development (section)

=== Large-scale, offshore and distributed ===
Agile software development has been widely seen as highly suited to certain types of environments, including small teams of experts working on [[greenfield project]]s,<ref name="boehm2004">{{cite book|last=Boehm|first=B.|author-link=Barry Boehm|author2=R. Turner|title=Balancing Agility and Discipline: A Guide for the Perplexed|publisher=Addison-Wesley|location=Boston, MA|year=2004|isbn=978-0-321-18612-6|pages=55–57|author2-link=Richard Turner (software)}}</ref><ref name="beck1999">{{cite book|last=Beck|first=K.|author-link=Kent Beck|title=Extreme Programming Explained: Embrace Change|publisher=Addison-Wesley|location=Boston, MA|year=1999|isbn=978-0-321-27865-4}}</ref> and the challenges and limitations encountered in the adoption of agile software development methods in a large organization with [[Legacy system|legacy infrastructure]] are well-documented and understood.<ref>{{cite web|last=Evans|first=Ian |title=Agile Delivery at British Telecom|url=http://www.methodsandtools.com/archive/archive.php?id=43| access-date =21 February 2011}}</ref>

In response, a range of strategies and patterns has evolved for overcoming challenges with large-scale development efforts (>20 developers)<ref name="ambler2006"/><ref name="sstc2007">Schaaf, R.J. (2007). Agility XL [http://www.sstc-online.org/Proceedings/2007/pdfs/RJS1722.pdf Systems and Software Technology Conference 2007] {{webarchive|url=https://web.archive.org/web/20160313105019/http://sstc-online.org/proceedings/2007/pdfs/rjs1722.pdf |date=13 March 2016 }}, Tampa, FL</ref> or distributed (non-colocated) development teams,<ref name="BridgingTheDistance">{{cite web|url=http://www.drdobbs.com/architecture-and-design/184414899 |title=Bridging the Distance |publisher=Sdmagazine.com |access-date=1 February 2011}}</ref><ref name="AgileOffshore">{{cite web|first=Martin |last=Fowler |url=http://www.martinfowler.com/articles/agileOffshore.html |title=Using an Agile Software Process with Offshore Development |publisher=Martinfowler.com |access-date=6 June 2010}}</ref> amongst other challenges; and there are now several recognized frameworks that seek to mitigate or avoid these challenges.

There are many conflicting viewpoints on whether all of these are effective or indeed fit the definition of agile development, and this remains an active and ongoing area of research.<ref name="ambler2006">W. Scott Ambler (2006) [http://www.drdobbs.com/184415491 Supersize Me] in Dr. Dobb's Journal, 15 February 2006.</ref><ref name="oopsla2002">Agile Processes Workshop II Managing Multiple Concurrent Agile Projects. Washington: OOPSLA 2002</ref>

When agile software development is applied in a distributed setting (with teams dispersed across multiple business locations), it is commonly referred to as [[distributed agile software development]]. The goal is to leverage the unique benefits offered by each approach. Distributed development allows organizations to build software by strategically setting up teams in different parts of the globe, virtually building software round-the-clock (more commonly referred to as follow-the-sun model). On the other hand, agile development provides increased transparency, continuous feedback, and more flexibility when responding to changes.