• Corpus ID: 16314221

A Comparison between Agile and Traditional Software Development Methodologies

@inproceedings{Awad2005ACB,
  title={A Comparison between Agile and Traditional Software Development Methodologies},
  author={Manal Ahmed Awad},
  year={2005}
}

• M. Awad
• Published 2005
• Computer Science

Agile and Traditional software development methodologies, both are being used in different 8 projects of software development industry. Agile software development technology is an 9 incremental software development process. On the other hand, Traditional software 10 development methodologies or plan-driven software can be explained as a more formal 11 approach to software development. These methodologies come with a fully completed set of 12 systems requirements followed by an architectural and high leveldesign development and 13 inspiration.This research focuses on the software development life cycle, role and 14 responsibilities of agile and traditional software development methodologies and their 15 technical practices. It performs a comparison between both the software development 16 methodologies. Here a questionnaire is used to collect data from the various experts of 17 different IT related organizations of Bangladesh. In the questionnaire, there are three sections 18 to bring out the individual knowledge from different organization, methodology knowledge of 19 the respondents and software development experience of the respondents. The respondents are 20 mainly software engineer, system analyst, software developer etc. A comparison is also 21 performed between this survey result and a survey done by Ambler. 22 terms— 24 On the other hand, Traditional software development methodologies or plan-driven software can be explained 25 as a more formal approach to software development. These methodologies come with a fully completed set 26 of systems requirements followed by an architectural and high leveldesign development and inspiration. This 27 research focuses on the software development life cycle, role and responsibilities of agile and traditional software 28 development methodologies and their technical practices. It performs a comparison between both the software 29 development methodologies. Here a questionnaire is used to collect data from the various experts of different IT 30 related organizations of Bangladesh. In the questionnaire, there are three sections to bring out the individual 31 knowledge from different organization, methodology knowledge of the respondents and software development 32 experience of the respondents. The respondents are mainly software engineer, system analyst, software developer 33 etc. A comparison is also performed between this survey result and a survey done by Ambler. 34 The analysis demonstrates the effect responds for agile methodologies, more than 80% responds for traditional methodologies and slightly more than 44 10% responds for the other mix technologies for a specific organization. 45 The findings of this project research study also confirm the appropriateness of the use of agile methodologies for 46 small scale projects, traditional and agile methodologies for medium scale projects and traditional methodologies 47 for large scale projects of an organization. 48 which involve 475 more than 50 software developers agile seems to be working in a negative manner. This was shown in a study 476 conducted by ambler (2008). Cockburn (2008) iii. Software Risk Software project risk may result in lots of 477 problems. Budget and plan overruns and unable to meet the expectations of the uses and many more (Renhui 478 and Fengyong, 2007). There are few categories of risk according to Renhui and Fengyong (2007), and there are;? 479 Team risk ? Environmental risk of organization ? Demand risk ? Plan and control risk ? User risk ? Complexity 480 risk 481 of change of during development phase through customer agile 485 best methodology as it can respond to changes faster. 486