Kiran Hiwarkar.et.al. Int. Journal of Engineering Research and Applications www.ijera.com ISSN: 2248-9622, Vol. 6, Issue 3, (Part - 6) March 2016, pp.80-85 www.ijera.com 80|Page Comparative Analysis of Agile Software Development Methodologies-A Review Kiran Hiwarkar 1 , Aditya Doshi 2 , Rahul Chinta 3 , Manjula R 4 1,2,3 ( Post Graduate Students Department Of Computer Science Engineering, VIT University, Tamilnadu,India) 4 (Associate Professor At Department Of Computer Science Engineering, VIT University, Tamilnadu, India) ABSTRACT Software development methodology consists of dividing the software development process or work into different phases in order to achieve better planning and management. As the software development proceeds, factors such as requirements, needs, priorities, underlying technology may change. Thus development process must be highly dynamic and a good software development methodology must adapt to these evolving and changing requirements. Traditional software development models are unable to handle such dynamic requirements. To cope up with such dynamic requirements a set of software development methodologies referred as „Agile Software development methodologies‟ are used. Comparison between different Agile software development methods will help in the selection of appropriate development model given a particular scenario. Keywords: ASD, DSDM, FDD, Scrum, XP I. INTRODUCTION Today‟s situation of software development with frequently changing requirements, where the traditional method fails in many scenarios. The most common traditional approach for developing software is “Waterfall Model”. The major drawbacks of this method are, it uses downward approach for development, development of complete software at one time, most of the energy is wasted in the documentation and taking signs and approvals and in the traditional approach we can‟t move next until we complete previous stage, almost one third of the time and resources are spent on the testing [4] this scenario leads to delay in the delivery of the final product. Now a day‟s software developing and maintaining plays an important role in all the industries. So the development need to more accurate and fast thus methodology need to be changed according to the changing scenario. Converse to the traditional approach the “Agile Methodology” works better in the current scenario of frequently changing requirement.” Agile” means fast and incremental approach for developing projects with strong focus and customer‟s involvement [3]. In this methodology documentation of the project considered as the non- productive work as it has no direct value at the end of the software development. Agile system is with little paper work oriented and more focused on the coding. In this methodology source code is considered as the way of communication and documentation between man to computer and people to people [3]. Agile is nothing but group of the methods which are mostly based on the iterative work flow. Main moto of the agile methodology is continuous and fast delivery of the project. This methodology is not prediction oriented but it is more adaptive. Agile is designed in such a way that it works well in the frequently changing requirements [2]. The main advantage of this method over the traditional one are increase in the development speed and reduction in the cost. Some of the method which follows the Agile principle but in practice works slightly different are “Extreme Programming”, “Lean Software Development”, “Scrum”, “Adaptive Software Development”, “Dynamic System Development Method,” “Crystal”, “Kanban”, “Feature Driven Development” [5]. This survey is mainly focused on the comparison of the widely used agile methods such as “Extreme Programming”, “Scrum”, “Adaptive Software Development”, “Dynamic System Development”, “Feature Driven Development”. II. LITERATURE REVIEW Software development methodologies are in use since the very inception of software industries. The term software engineering was result of “software crisis” [18]. The Software crisis presents several issues that were prominent in the software industry in 1960s, 1970s, and 1980s. Some of the important issues were: - • Projects not being completed within given time and budget. • Inefficient and low quality product. • Product Unable to satisfy customer requirements. Ensure that any miscellaneous numbering system you use in your paper cannot be confused with a reference [4] or an equation (3) designation. RESEARCH ARTICLE OPEN ACCESS