Making Agile Development and Offshoring Practice Successful on Global Software Development Project

Making Agile Development and Offshoring Practice Successful on Global Software Development Project

Edward Chen (University of Massachusetts Lowell, USA)
Copyright: © 2013 |Pages: 13
DOI: 10.4018/978-1-4666-3966-9.ch007
OnDemand PDF Download:
No Current Special Offers


Two significant trends have been gaining momentum in software development: the utilization of Agile development methodologies, and the continuing trend of companies to outsource development work offshore. These two trends have changed the way companies develop software and business applications. This chapter seeks to evaluate how a company can successfully manage both trends in conjunction with each other on global business. The primary question addressed is whether the benefits derived from Agile development methodologies and the savings from outsourced software development efforts cancel each other out when applied together, or whether they create a synergy greater than the sum of the parts. In order to answer this question, this chapter intends to examine several relevant business practices and industry experiences. From lessons learned, we identify factors which seem to influence a successful combination of Agile methodology and offshoring in global software development projects.
Chapter Preview

Agile Development

Jones (2006) identifies that among the 30 most significant issues in software engineering which have persisted and haunted software development companies for over 30 years are:

  • Only 50% of all the customer’s requirements are known at the initiation of the project

  • Once development is underway, there is a 2% scope increase every month (scope-creep)

  • A total of 20% of the initial requirements are postponed for implementation and delivery only in the next release

  • Documentation is very expensive (2nd most expensive activity)

  • New customer requirements for post-delivery applications grows every year

Organizations used to following a structured life cycle for software product development find themselves at a crossroads between quickly meeting customer demands and keeping tight control over the development process. The traditional model for software product development, commonly known as the Waterfall Development Model, provides a well-defined process for software development teams to meet customer requirements. However, this model has limited some organizations’ ability to deliver on customer’s expectations in a timely fashion.

The Agile software development model took shape when IS researchers started to challenge the assumptions of the Waterfall model. They take inspiration from Lean Manufacturing methods to tackle some of the major software development problems (Cohen, Lindvall, & Costa, 2004). The Agile development model yields great benefits to organizations seeking to provide iterative and incremental releases to their customers. There are multiple ways to attain agility. Many methods have been suggested in the extant literature after they have been implemented successfully in the industry. Among those proposed Agile models, Scrum and Extreme Programming are two of the most popular Agile development methods (Succi, & Marchesi, 2001; Marchesi, Succi, Wells, Williams, & Wells, 2003).

Complete Chapter List

Search this Book: