ISSN 2249-6343Internati<strong>on</strong>al Journal <str<strong>on</strong>g>of</str<strong>on</strong>g> Computer Technology and Electr<strong>on</strong>ics Engineering (IJCTEE)Volume 2, Issue 4, August 2012Jeffrey et al [8] shows that XP is used heavily in theorganizati<strong>on</strong>. After that in order <str<strong>on</strong>g>of</str<strong>on</strong>g> decreasing usage, Scrum isused, then feature driven development, dynamic developmentmethodology, adaptive s<str<strong>on</strong>g>of</str<strong>on</strong>g>tware development, and then otheragile methodologies which are modified as per company areused.As further dem<strong>on</strong>strated by A. Ahmed et al [9], scrum isused most comm<strong>on</strong>ly, 50% <str<strong>on</strong>g>of</str<strong>on</strong>g> the projects are d<strong>on</strong>e withactive stakeholder participati<strong>on</strong>. 66.7% participants wereagreeing that productivity has improved and quality isimproved by 50%.Based <strong>on</strong> a study, Pirjo et al [12] shows that agile methodsare good for some programming envir<strong>on</strong>ments, but not for all.Projects that involve large teams, well-defined requirements,clients needing high assurance and large code-bases, thetraditi<strong>on</strong>al plan-oriented project pr<str<strong>on</strong>g>of</str<strong>on</strong>g>ile works well.Therefore, <str<strong>on</strong>g>Agile</str<strong>on</strong>g> methods produces best results in case <str<strong>on</strong>g>of</str<strong>on</strong>g>when the team is small, the requirements are not yet welldefined, the project code base is small and the customer isinterested in seeing significant progress. However, as as<str<strong>on</strong>g>of</str<strong>on</strong>g>tware project transiti<strong>on</strong>s from a small prototype to a largestable system with a large team, with promises to keep anddates to meet, then agile methods al<strong>on</strong>e is not sufficient thensome additi<strong>on</strong>al mechanism is needed.O. Solo et al [13] show that adopti<strong>on</strong> <str<strong>on</strong>g>of</str<strong>on</strong>g> agile processesincreases with company size. Also the adopti<strong>on</strong> <str<strong>on</strong>g>of</str<strong>on</strong>g> agilemethods in large and distributed envir<strong>on</strong>ments is beingaddressed more frequently. 54% <str<strong>on</strong>g>of</str<strong>on</strong>g> the participants used XPand the 5 factors in XP used are open <str<strong>on</strong>g>of</str<strong>on</strong>g>fice space, codingstandards, 40h week, c<strong>on</strong>tinuous integrati<strong>on</strong> and collectivecode ownership. 27% used Scrum practices and the remainingused other practices <str<strong>on</strong>g>of</str<strong>on</strong>g> <str<strong>on</strong>g>Agile</str<strong>on</strong>g>.Tore et al [14] report that XP is seemed difficult tointroduce in large, complex organizati<strong>on</strong>s but easier in otherorganizati<strong>on</strong> types. Pair programming is inefficient and XPworks best with experienced development teams. Also there islack <str<strong>on</strong>g>of</str<strong>on</strong>g> attenti<strong>on</strong> to design and architectural issues.Behrouz Far [18] mapped the s<str<strong>on</strong>g>of</str<strong>on</strong>g>tware reliabilityengineering into an agile development process. As per thestudy, test driven development seems to be incompatible withthe reliability model.Subhas et al [20] proposed a framework for identifying theimportant changes required and challenges involved foradopting agile s<str<strong>on</strong>g>of</str<strong>on</strong>g>tware development practices in traditi<strong>on</strong>aldevelopment organizati<strong>on</strong>s.Markus et al [23] highlights the negative impact <str<strong>on</strong>g>of</str<strong>on</strong>g> changein requirements <strong>on</strong> customer satisfacti<strong>on</strong>. The mainc<strong>on</strong>tributi<strong>on</strong> <str<strong>on</strong>g>of</str<strong>on</strong>g> their paper pertains to the interacti<strong>on</strong> effectsbetween change in requirements and agile methods <strong>on</strong>customer satisfacti<strong>on</strong>. They found that work climate, finalproduct adaptability and willingness to adapt to change have apositive moderating effect <strong>on</strong> the relati<strong>on</strong>ship between changein requirements and customer satisfacti<strong>on</strong>.Rober Imreh et al [29] c<strong>on</strong>cludes that agile s<str<strong>on</strong>g>of</str<strong>on</strong>g>twaredevelopment has a significant impact <strong>on</strong> quality. Theyidentified some <str<strong>on</strong>g>of</str<strong>on</strong>g> the major quality impacts <str<strong>on</strong>g>of</str<strong>on</strong>g> <str<strong>on</strong>g>Agile</str<strong>on</strong>g>S<str<strong>on</strong>g>of</str<strong>on</strong>g>tware <strong>Development</strong> and various approaches <str<strong>on</strong>g>of</str<strong>on</strong>g>remediati<strong>on</strong> have been recommended within theorganizati<strong>on</strong>al, methodical and cultural framework andindustry best practices.The study performed by Sharifah Syed et al [30] showsthat agile methodology is more people-oriented than processoriented in a more volatile envir<strong>on</strong>ment. Excepting thesatisfacti<strong>on</strong> <str<strong>on</strong>g>of</str<strong>on</strong>g> the developers this is helpful <strong>on</strong>ly when therequirements are uncertain or volatile.V. BENEFITS OF AGILE IN SOFTWARE DEVELOPMENT PROCESSThe key benefits <str<strong>on</strong>g>of</str<strong>on</strong>g> agile methodology in s<str<strong>on</strong>g>of</str<strong>on</strong>g>twaredevelopment processes due to which agile methodologyshould be adopted while developing s<str<strong>on</strong>g>of</str<strong>on</strong>g>tware are shown in thefigure1 and explained in detail thereafter.A. Handling Change <str<strong>on</strong>g>of</str<strong>on</strong>g> RequirementsPlanning phase is dramatically improved. First, becausecustomers are directly involved in the development process,that is, customers c<strong>on</strong>trol the processes <str<strong>on</strong>g>of</str<strong>on</strong>g> projects through<strong>on</strong>-site interacti<strong>on</strong>, requirements truly reflect the currentneeds <str<strong>on</strong>g>of</str<strong>on</strong>g> the end users.B. Fault Detecti<strong>on</strong>As testing is performed during each iterati<strong>on</strong>, faults aredetected earlier and can be fixed before it increases in severitythan with a plan-driven process model. Also, c<strong>on</strong>tinuoustesting allows c<strong>on</strong>tinuous testing feedback, which furtherimproves code developed in future iterati<strong>on</strong>s.C. Increased PerformanceDaily standup meetings provide an opportunity toexchange valuable informati<strong>on</strong> and to fine tune improvementsc<strong>on</strong>tinuously. The ability to discuss complex projects throughsimple stories and simple design encourages teamwork.Better communicati<strong>on</strong> leads to increased knowledge sharing,self organizing teams, team morale as employees begin totrust and gain the trust <str<strong>on</strong>g>of</str<strong>on</strong>g> their team members. This increasesteam productivity and generates better performance in terms<str<strong>on</strong>g>of</str<strong>on</strong>g> good Return <strong>on</strong> Investment than the sum <str<strong>on</strong>g>of</str<strong>on</strong>g> all individualoutput.Figure1: <str<strong>on</strong>g>Agile</str<strong>on</strong>g> S<str<strong>on</strong>g>of</str<strong>on</strong>g>tware <strong>Development</strong> Methodologies with Benefits48