Motivation behind Agile Software Development over Traditional Development

Motivation behind Agile Software Development over Traditional Development

Karun Madan (SD College, India)
DOI: 10.4018/978-1-4666-8510-9.ch007
OnDemand PDF Download:
No Current Special Offers


Out of the many revolutions in software development methodologies over the past years, no new methodology withstands completely in one way or the other. The failure rate of projects is still very high in spite of so much of revolutionary methodologies come in existence. Unsuccessful projects not only mean the incomplete projects even after deadline or outdated projects but there may be several other scenarios like project did not meet up the real requirements or lack of ability to deal with the changing requirements etc. In this kind of circumstances, projects were never successfully utilized, and another high percentage of projects again required massive rework to be utilizable. Factors like changing requirements and late testing and integration are few of the main causes of this high percentage of failure.This paper reveals how agile development is a way out to the issues linked with traditional software development. Agile development primarily focuses on the rapid delivery of enterprise worth in the form of working software.
Chapter Preview

Agile Principles

The Agile Manifesto is based on 12 principles (Beck et. al., 2001):

  • 1.

    Customer satisfaction is the prime priority by means of rapid and continuous delivery of useful workable software.

  • 2.

    Welcome changing requirements throughout the development process, even late in development to oblige customer’s competitive arena

  • 3.

    Working software is delivered frequently not only at the end, so weekly releases are preferred over releases after months of wait

  • 4.

    Close collaboration among the business people and developers on the daily basis

  • 5.

    Projects must be built around motivated individuals, Provide them the environment and support, more importantly show trust in them.

  • 6.

    Face-to-face discussion is the excellent form of conveying information among the teammates, so try to assemble them together under one roof frequently

  • 7.

    Working deployable software is the key measure of progress as compare to less effective documentation

  • 8.

    Sustainable development must be supported, all the team members of agile software development ought to maintain a constant pace

  • 9.

    Continuous attention to the technical brilliance and good design boosts the effect of agile software development.

  • 10.

    Simplicity- the art of make the most of the quantity of work not done is necessary.

  • 11.

    Self-organizing teams results in best architectures, requirements, and designs for the project.

  • 12.

    Regular adaptation to ever changing situations, then modify its behavior accordingly at regular intervals.

Complete Chapter List

Search this Book: