A Survey of Agile Transition Models

A Survey of Agile Transition Models

Imran Ghani (Universiti Teknologi Malaysia, Malaysia), Dayang Norhayati Abang Jawawi (Universiti Teknologi Malaysia, Malaysia), Naghmeh Niknejad (Universiti Teknologi Malaysia, Malaysia), Murad Khan (Universiti Teknologi Malaysia, Malaysia) and Seung Ryul Jeong (Kookmin University, South Korea)
Copyright: © 2016 |Pages: 24
DOI: 10.4018/978-1-4666-9858-1.ch008
OnDemand PDF Download:
No Current Special Offers


Nowadays, since business environment is highly dynamic, software necessities are continuously being improved in order to meet the needs of modern industrialized world. Therefore, IT organizations seek for a quick way of software delivery and for adapting to the necessary technological changes. From this ideal viewpoint, traditional plan-driven developments lag behind to overcome these conflicts. The purpose of this chapter is to present the existing models and frameworks which guide organizations to adopt agile methods. This may help organizations to follow professionals' suggestions during their migration from traditional systems to agile development.
Chapter Preview

1 Introduction

Since the purpose of organizations are improving return on investment (ROI) and controlling the risk of projects failure effectively, Agile software development has become as the most debated solution in the last decade and many companies are transforming from traditional development to Agile developments methods like SCRUM(Druckman, 2011).

For the first time, the word agile was utilized incorporation with software process in 1998 (Aoyama, 1998).The ability of sensing and rapidly responding to business scenarios in order to remain creative and aggressive in an unsteady and quickly changing business environment is agility(Highsmith, 2002). The agile attitude for developing is the agility of development teams, development process and their environment (Boehm & Turner, 2004). This approach integrates shared ideals of various stakeholders and a philosophy of regular providing the customers with product features in short time-frames (Moniruzzaman & Hossain, 2013; Southwell, 2002). This frequent and regular feature delivery is achieved by team based attitude (Coram & Bohner, 2005).

Beck et al. (Beck et al., 2001) expressed that customers are unable to define their requirements exactly due to the rapid change in the world of technology and companies which are used the new technologies in their products. Therefore, agile approaches are intended to cover the changing needs in software technology environment. In 2001(Ambler, 2002), a group of 17 software consultants with different backgrounds created the Agile Software Development Alliance to define a manifesto for agile software development principles. Agile methods stressed on the unexpectedness challenges in practice based on the communication among people and their innovation instead of processes. The main purpose of agile methods is to improve and increase the responses time to requirements, environmental changes and achieve the deadlines (Rao, Naidu, & Chakka, 2011). Beck et al. (Beck et al., 2001) expresses agile software development manifesto as the following:

  • 1.

    Individuals and interactions over processes and tools

  • 2.

    Working software over comprehensive documentation.

  • 3.

    Customer collaboration over contract negotiation.

  • 4.

    Responding to change over following a plan.

Agile software development methods illustrate a series of processes that have been produced by experts (Ågerfalk, Fitzgerald, & In, 2006).Dynamic Systems Development Method (DSDM) (Stapleton, 2003) is recognized as the first method for agile development by Larman and Basili(Larman & Basili, 2003). Other best known methods are Extreme Programming (XP) (Beck, 2000), Scrum (Takeuchi & Nonaka, 1986), Crystal Methodologies Family (Cockburn, 2006), Agile Modeling (Ambler, 2002), Feature-Driven Development (FDD) (Anderson, 2004), and Adaptive Software Development (Highsmith, 2013).

Complete Chapter List

Search this Book: