Impact of Agile Methodology on Software Development Process

More documents

Recommendations

Info

ISSN 2249-6343International Journal <strong>of</strong> Computer Technology and Electronics Engineering (IJCTEE)Volume 2, Issue 4, August 2012D. Iterative and incremental deliveryProject delivery is divided into small functional releases orincrements to manage risk and to get early feedback fromcustomers and end users. These small releases are deliveredon a schedule using iterations that typically last between oneand four weeks each. Plans, requirements, design, code andtests are created initially and updated incrementally as neededto adapt to project changes. S<strong>of</strong>tware functionality progresscan be checked and monitored much more frequently ratherthan at end <strong>of</strong> long milestones.E. Flexibility <strong>of</strong> DesignFlexibility defines ability to change directions quickly. Ashandling change in requirements is the main feature <strong>of</strong> agilemethodology, design has to be made flexible that can handlechanges easily. Flexibility is based on the developmentprocess used for the project.F. Improvement in QualityTest-driven development and refactoring is used.Refactoring leads to higher code reuse and better quality. Allaspects <strong>of</strong> s<strong>of</strong>tware are improved, from design andarchitecture to performance <strong>of</strong> the products <strong>of</strong> each sprint.Improved communication leads to faster turnaround time forblocking bugs.VI. LIMITATION OF AGILE METHODOLOGYNothing in this world is without any shortcoming orlimitation. Here are some <strong>of</strong> the limitations and shortcomings<strong>of</strong> agile methodologies we got based on the literature. Main emphasis is on development rather than design anduser. It basically focuses on processes for gettingrequirements and developing code and does not focus onproduct design. High testing lead times and low test coverage. Many teams requiring high coordination andcommunication from project managers. Does not scale well to large projects, as numerousiterations are needed to complete the desiredfunctionality. Too much time may be devoted to any single, smallfeature. On a large scale project, opportunity cost to employ agilemethods may be too high for a foregone production onmore pr<strong>of</strong>itable and lean projects. Management Overhead is increased because a successfulapplication <strong>of</strong> an agile methodology relies heavily onstrong teamwork, the project manager must remaininvolved in the dynamics <strong>of</strong> the team.VII. CONCLUSION<strong>Agile</strong> s<strong>of</strong>tware development stresses in - evolvingrequirements accomplished by direct user involvement in thedevelopment process, rapid iterations, small and frequentreleases. The improvements in s<strong>of</strong>tware development processinclude more stable requirements, earlier fault detection, lesslead times for testing, increased communication, andincreased adaptive capacity. Different methodologies requiredifferent changes to the management and s<strong>of</strong>twaredevelopment cultures [26].There are number <strong>of</strong> factors thatcan directly and indirectly influence the development projectsin agile framework. Adopting agile developmentmethodologies has a positive impact on both the productivityand the quality. Hence, development team and customer bothare satisfied with its implementation in s<strong>of</strong>tware developmentprocesses.REFERENCES[1] Andrew Begel, Nachiappan Nagappan, “Usage and Perceptions <strong>of</strong><strong>Agile</strong> S<strong>of</strong>tware Development in an Industrial Context:An ExploratoryStudy”, First International symposium on empirical s<strong>of</strong>twareengineering and measurement, pp. 255-264, 2007.[2] Peter Maher, “Weaving <strong>Agile</strong> S<strong>of</strong>tware Development Techniques intoa Traditional Computer Science Curriculum”, Proc. <strong>of</strong> 6 th IEEEInternational Conference on Information Technology: NewGeneration, pp. 1687-1688, 2009.[3] Anfan Zuo, Jing Yang, Xiaowen Chen, “Research <strong>of</strong> <strong>Agile</strong> S<strong>of</strong>twareDevelopment Based on Formal Methods”, International Conference onMultimedia Information Networking and Security, pp. 762-766, 2010.[4] Michael J Rees, “A Feasible User Story Tool for <strong>Agile</strong> S<strong>of</strong>twareDevelopment”, Proc. Of 9 th Asia-Pacific S<strong>of</strong>tware EngineeringConference (APSEC’ 02), 2002.[5] Outi Salo, Pekka Abrahamsson, “Integrating <strong>Agile</strong> S<strong>of</strong>twareDevelopment and S<strong>of</strong>tware Process Improvement: a Longitudinal CaseStudy”, pp. 193-202, 2005.[6] Xia<strong>of</strong>eng Wang, “The Combination <strong>of</strong> <strong>Agile</strong> and Lean in S<strong>of</strong>twareDevelopment: An Experience Report Analysis”, IEEE <strong>Agile</strong>Conference, pp. 1-9, 2011.[7] Richard Mordinyi, Eva Kuhn, Alexander Schatten, “Towards anArchitectural Framework for <strong>Agile</strong> S<strong>of</strong>tware Development”, 17 th IEEEInternational Conference and workshops on Engineering <strong>of</strong> ComputerBased Systems, pp. 276- 280, 2010.[8] Jeffrey A. Livermore, “Factors that impact implementing an <strong>Agile</strong>S<strong>of</strong>tware Development <strong>Methodology</strong>”, pp. 82-85, IEEE 2007.[9] A. Ahmed, S. Ahmad, Dr. N. Ehsan, E. Mirza, S.Z. Sarwar, “<strong>Agile</strong>S<strong>of</strong>tware Development:<strong>Impact</strong> on Productivity and Quality” , pp.287-290, IEEE 2010.[10] Ying Wang, Dayong Sang, Wujie Xie, “Analysis on <strong>Agile</strong> S<strong>of</strong>twareDevelopment Methods from the View <strong>of</strong> Informationalization SupplyChain Management”, 3 rd International Symposium on IntelligentInformation Technology Application Workshops”, pp. 219-222, 2009.[11] Tobin J. Lehman, Akhilesh Sharma, “S<strong>of</strong>tware Development as aService: <strong>Agile</strong> Experience”, Annual SRII Global Conference, pp.749-758, IEEE 2011.[12] Pirjo Nakki, Kaisa Koskela, Minna Pikkarainen, “Practical model foruser-driven innovation in agile s<strong>of</strong>tware development”, Proc. Of 17 thInternational Conference on Concurrent Enterprising, pp. 1-8, 2011.[13] O. Salo, P. Abrahamsson, “<strong>Agile</strong> methods in European embeddeds<strong>of</strong>tware development organisations: a survey on the actual use andusefulness <strong>of</strong> Extreme Programming and Scrum”, IET S<strong>of</strong>tware, pp.58-64, Vol. 2, No. 1, Feb. 2008.[14] Tore Dyba, Torgeir Dingsoyr, “What do we know about <strong>Agile</strong> S<strong>of</strong>twareDevelopment”, IEEE S<strong>of</strong>tware, pp. 6-9, Sep./Oct. 2009[15] <strong>Agile</strong> Alliance, http://www.agilealliance.org/[16] <strong>Agile</strong> Manifesto and <strong>Agile</strong> Principles, http://agilemanifesto.org/[17] “<strong>Agile</strong> S<strong>of</strong>tware Development” Wikipedia,http://en.wikipedia.org/wiki/<strong>Agile</strong>_s<strong>of</strong>tware_development[18] Behrouz Far, “S<strong>of</strong>tware Reliability Engineering for <strong>Agile</strong> S<strong>of</strong>twareDevelopment”, pp. 694-697, IEEE 2007.[19] Kazuhiro Matsuo, Shota Anzawa, “Project Practices <strong>of</strong> <strong>Agile</strong> S<strong>of</strong>twareDevelopment for Under Graduate Development”, 40th ASEE/IEEEFrontiers in Education Conference, Session S2D1-S2D2, Oct. 2010.[20] Subhas C Misra, Uma Kumar, Vinod Kumar, Gerald Grant, “TheOrganizational Changes Required and the Challenges Involved inAdopting <strong>Agile</strong> Methodologies in Traditional S<strong>of</strong>tware DevelopmentOrganizations”, pp. 25-28, IEEE 2006.49
ISSN 2249-6343International Journal <strong>of</strong> Computer Technology and Electronics Engineering (IJCTEE)Volume 2, Issue 4, August 2012[21] Vladan Devedzic and Sasa R. Milenkovic, “Teaching <strong>Agile</strong> S<strong>of</strong>twareDevelopment: A Case Study”, IEEE transactions on education, vol. 54,no. 2, pp. 273-278, May 2011.[22] Osama Sohaib, Khalid Khan, “Integrating Usability Engineering and<strong>Agile</strong> S<strong>of</strong>tware Development: A Literature Review”, InternationalConference On Computer Design And Appliations (ICCDA 2010),Vol. 2, pp. 32-38, IEEE 2010.[23] Markus Kohlbacher, Ernst Stelzmann, Sabine Maierh<strong>of</strong>er, “Do <strong>Agile</strong>S<strong>of</strong>tware Development Practices Increase Customer Satisfaction inSystems Engineering Projects?”, IEEE International SystemsConference (SysCon), pp. 168 - 172 IEEE 2011.[24] Jiangping Wan, Weiping Luo, Xiaoyao Wan, “Case Study on CriticalSuccess Factors <strong>of</strong> <strong>Agile</strong> S<strong>of</strong>tware Process Improvement”, pp.628-631, IEEE 2011.[25] The Rules <strong>of</strong> Extreme Programming,http://www.extremeprogramming.org/rules.html[26] Kristin Fergis, “The <strong>Impact</strong> <strong>of</strong> an <strong>Agile</strong> <strong>Methodology</strong> on S<strong>of</strong>twareDevelopment Costs”, Project Report, EAS 499 Senior CapstoneProject, April, 2012.[27] Nayan Jyoti Kar, “Adopting <strong>Agile</strong> Methodologies <strong>of</strong> S<strong>of</strong>twareDevelopment”, SETLabs Briefing, Infosys Technologies, vol. 4 no. 1,pp. 1-9, July-Sep. 2006.[28] Feature Driven Development and <strong>Agile</strong> Modelling,http://www.agilemodeling.com/essays/fdd.htm[29] Robert Imreh, Mahesh S. Raisinghani, “<strong>Impact</strong> <strong>of</strong> <strong>Agile</strong> S<strong>of</strong>twareDevelopment on Quality within Information TechnologyOrganizations”, Journal <strong>of</strong> Emerging Trends in Computing andInformation Sciences, Vol. 2, No. 10, pp. 460-475, October 2011.[30] Sharifah Syed-Abdullah & Mike Holcombe & Marian Gheorge, “The<strong>Impact</strong> <strong>of</strong> an <strong>Agile</strong> <strong>Methodology</strong> on the Well Being <strong>of</strong> DevelopmentTeams”, Empir S<strong>of</strong>tware Eng, pp. 143-167, Springer 2006.Gaurav Kumar is a Research scholar (S<strong>of</strong>tware Engineering) atDepartment <strong>of</strong> Computer Science & Engineering, Guru JambheshwarUniversity <strong>of</strong> Science & Technology, Hisar, Haryana, India. He has done M.Tech (Information Technology) and B.E. (Computer Science &Engineering). He is Gate Qualified in 2007. He has 4 years teachingexperience and 2 years industrial experience.Dr. Pradeep Kumar Bhatia is Associate Pr<strong>of</strong>essor at Department <strong>of</strong>Computer Science & Engineering, Guru Jambheshwar University <strong>of</strong> Science& Technology, Hisar, Haryana, India. He has guided many research scholarsand M.Tech scholars. His areas <strong>of</strong> specialization are S<strong>of</strong>tware Engineeringand Computer Graphics. He has done many projects sanctioned fromUGC.He has more than 18 years teaching experience.50
Page 3: ISSN 2249-6343International Journal

Impact of Agile Methodology on Software Development Process

Create successful ePaper yourself

Delete template?

Save as template?