Introduction lot of people have been asking the question "What is Agile Software Development?" and invariably they get a different definition depending on who they ask. Here's a definition that conforms to the values and principles of the Agile Manifesto [1]. An iterative and incremental (evolutionary) approach to software development which is performed in a highly collaborative manner by self-organizing teams within an effective governance framework with "just enough" ceremony that produces high quality solutions in a cost effective and timely manner which meets the changing needs of its stakeholders [6].Agile software development is actually a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between selforganizing, cross-functional teams [4]. In 2001, the "agile manifesto" was written by the practitioners reveals which items are considered valuable by ASDMs [1]. As shown in Table 1.

Table 1 : Agile Manifesto (Source: [1]) a) Research Review Agile software development (ASD) is major paradigm, in field of software engineering which has been widely adopted by the industry, and much research, publications have conducted on agile development methodologies over the past decade. The traditional way to develop software methodologies follow the generic engineering paradigm of requirements, design, build, and maintain. These methodologies are also called waterfall-based taking from the classical software development paradigm. They are also known by many other names like plan-driven, (Boehm and Turner, 2004), [39]; documentation driven, heavyweight methodologies, and big design upfront, (Boehm, 2002), [16]. Boehm and Phillip [72] report that during their project development experience, requirements often changed by 25% or more. Due to constant changes in the technology and business environments, it is a challenge for TSDMs to create a complete set of requirements up front [26]. Williams and Cockburn,[18] also mentioned that one of problems of TSDMs is the inability to respond to change that often determines the success or failure of a software product. The agile approach to software development is based on the understanding that software requirements are dynamic, where they are driven by market forces (Fowler, Title 2002;); [16], [36]. Agile systems development methods emerged as a response to the inability of previous plan-driven approaches to handle rapidly changing environments (Highsmith 2002), [55]. Williams and Cockburn [18] state that agile development is "about feedback and change" , that agile methodologies are developed to "embrace, rather than reject, higher rates of change".

Agility is the ability to sense and response to business prospects in order to stay inventive and aggressive in an unstable and rapidly shifting business environment (Highsmith, 2002), [55]. The agile approach to development is about agility of the development process, development teams and their environment (Boehm & Turner, 2004), [39]. This approach incorporates shared ideals of various stakeholders, and a philosophy of regular providing the customers with product features in short time-frames (Southwell, 2002), [45]. This frequent and regular feature delivery is achieved by team based approach (Coram & Bohner, 2005), [47]. Agile teams consist of multi-skilled individuals (Fowler, 2002), [16]. The development teams also have on-site customers with substantial domain knowledge to help them better understand the requirements (Abrahamsson, Solo, Ronkainen, & Warsta, 2002), [37]. Multiple short development cycles also enable teams to accommodate request for change and provide the opportunity to discover emerging requirements (Highsmith, 2002), [55]. The agile approach promotes micro-project plans to help determine more accurate scheduling delivery commitments (Smits, 2006), [48].

M Lindvall, V Basili, B Boehm, P Costa, (2002), [17] summarize the working definition of agile methodologies as a group of software development processes that must be iterative (take several cycles to complete), incremental (not deliver the entire product at once), self-organizing (teams determine the best way to handle work), and emergent (processes, principles, and work structures are recognized during the project rather than predetermined). In the paper by (Abrahamsson, Warsta, Siponen & Ronkainen, 2003), in general, characterized agile software development by the following attributes: incremental, cooperative, straightforward, and adaptive [24]. Boehm, B., & Turner, R. (2005), generalize agile methods are lightweight processes that employ short iterative cycles, actively involve users to establish, prioritize, and verify requirements, and rely on a team's tacit knowledge as opposed to documentation [30].


# II.


# Agile Methods

For over a decade now, there has been an ever increasing variety of agile methods available includes a number of specific techniques and practices of software development. Agile methods are a subset of "iterative and evolutionary methods" [83,84] and are "based on iterative enhancement" [85]  The major methods include eXtreme Programming (Beck, 1999), [82], Scrum (K. Schwaber & Beedle, 2002), [53], Dynamic Systems Development Method (Stapleton, 1997), Adaptive Software Development (Highsmith, 2000), Crystal (Cockburn, 2002), and Feature-Driven Development (Palmer & Felsing, 2002). [58], [59], [60], [61]. Figure 1 shows an agile software development methodology process flow (Scrum). 


# Year

The Agile Manifesto articulates the common principles and beliefs underlying these methods (Cockburn, 2002), [16]. Among the first and perhaps best known agile methods are Scrum and XP , [49]. See Figure 2 shows the current rate of Agile methodologies used. Scrum is aimed at providing an agile approach for managing software projects while increasing the probability of successful development of software, whereas XP focuses more on the project level activities of implementing software. Both approaches, however, embody the central principles of agile software development [31]. Agile software development processes --such as the Rational Unified Process (RUP), Extreme Programming (XP), Agile Unified Process (AUP), Scrum, Open Unified Process (OpenUP), and even Team Software Process (TSP) --are all iterative and incremental (evolutionary) in nature [63]. Some these modern approaches, in particular XP and Scrum, are agile in nature. The agile methods are focused on different aspects of the software development life cycle. Some focus on the practices (extreme programming, pragmatic programming, agile modeling), while others focus on managing the software projects (the scrum approach) [12].


# III.


# Comparison Agile Software Development Methodologies over Traditional SDMs

There are many different characteristics between ASDMs and TSDMs. Boehm [16], for example, reports nine agile and heavyweight discriminators. He believes the primary objective of ASDMs is on rapid value whereas the primary objective of TSDMs is on high assurance.

Study performed S. Nerur, R. Mahapatra, G. Mangalaraj [22] state a comparison of traditional and agile development, they report seven issues to differentiate traditional and agile development. Their fundamental assumption of traditional development: "system are fully specifiable, predictable and are built through meticulous and extensive planning", whereas agile development: "high-quality adaptive software is developed by small teams using the principles of continuous design improvement and testing based on rapid feedback and change".

T. Dyba, & T. Dingsoyr, [74] summarize the differences between Agile development and traditional development basis on the of an unpredictable world, as well as emphasizing the value competent people and their relationships bring to software development. Agile methods address the challenge of an unpredictable world, emphasizing the value competent people and their relationships bring to software development [74].

Different researchers compare traditional and agile approaches, in their different perspectives, are summarized in Table 2 (All sources from additional information). Linear; Life-cycle model (waterfall, spiral or some variation)

Iterative; The evolutionarydelivery model

Style of development , [50] Anticipatory Adaptive

Requirements (Boehm, 2002); (Boehm and Turner, 2004), [16], [39] Knowable early, largely stable; Clearly defined and documented

Emergent, rapid change, unknown -Discovered during the project Architecture (Boehm, 2002); (Wysocki, 2009(Wysocki, , 2011) ) , [16], [56] Heavyweight 


# Predictability and optimization


# Exploration or adaptation

Change , [19] Tend to be change averse Embrace change

Team members (Boehm, 2002) , (Sherehiy, Karwowski, & Layer, 2007), [16], [41] Distributed teams of specialists; Plan-oriented, adequate skills access to external knowledge Agile, knowledgeable, collocated and collaborative; Co-location of generalist senior technical staff;

Team organization , [52] Pre-structured teams Self-organizing teams Client Involvement ), [21] Low involvement; Passive Client onsite and considered as a team member; Active/proactive Organization culture (Highsmith, 2002) , (Nerur, Mahapatra, Mangalaraj, 2005), [55], [22] Command and Control Culture


# Leadership and Collaboration Culture

Software development process (Salo, & Abrahamsson, 2007), [42] Universal approach and solution to provide predictability and high assurance Flexible approach adapted with collective understanding of contextual needs to provide faster development Measure of success (Highsmith, 2010), [1] Conformance to plan Business value delivered a) Major agile benefits in comparison to the traditional approach

In this section, we presenting list and explain some of agile benefits in comparison to the traditional approach which significantly improves software development in many ways. We try to provide an indepth understanding (in some cases with figures), of these merit issues:  Dagnino, 2002), they believe, Agile methods are iterative, evolutionary, and incremental delivery model of software development [30], [79], [29], [20], [80], [24], [81].

Entire application is distributed in incremental units called as iteration. Development time of each iteration is small (couple of weeks), fixed and strictly adhered to. Each iteration is a mini increment of the functionality and is build on top of previous iteration. Agile software development of short iterative cycles offers an opportunity for rapid, visible and motivating software process improvement [75]. Traditional approaches to the data-oriented aspects of software development; however, tend to be serial, not evolutionary and certainly not agile, in nature.  2005), generalize agile methods are lightweight processes that employ short iterative cycles, actively involve users to establish, prioritize, and verify requirements, and rely on a team's tacit knowledge as opposed to documentation [30]. G Perera, & MSD Fernando (2007), also describe Agile practice is a customer oriented, light-weight software development paradigm, best suited for small size development teams in projects under vague and changing requirements [65]. A number of agile software development methods such as extreme programming (XP), feature-driven development, crystal clear method, scrum, dynamic systems development, and adaptive software development, fall into this category [22]. Traditional Software Development Methods (TSDMs) including waterfall and spiral models are often called heavyweight development methods [26]. These methods involves extensive planning, predefine process phases, heavy documentation and long term design process. Lightweight methodologies put extreme emphasis on delivering working code or product while downplayning the importance of formal process and comprehensive documentation [23]. lifecycle based software development delivers the software only after entire completion of development process and before that clients have no clear idea and view of software to be developed. According to (Boehm & Turner, 2005), Fast cycles, frequent delivery: Scheduling many releases with short time spans between them forces implementation of only the highest priority functions, delivers value to the customer quickly, and speeds requirements emergence [30]. ASD methods are iterative and incremental development [4], and each successful completion of development iteration, it delivers software product increment to client, thus Agile software development is satisfying the customer through early and continuous delivery of the valuable software [66]. Traditional, emerged as a response to the inability of previous plandriven approaches to handle rapidly changing environments (Highsmith, 2002). As second principle of Agile Manifesto [1] --welcome changing requirements, even late in development?, all agile method(s) is well organized, accommodate to change requirements. According to B. Boehm, (2002), organizations -are complex adaptive systems in which requirements are emergent rather than pre-specifiable? and agile approaches -are most applicable to turbulent, highchange environments? [16]   In contrast, agile development framework allows both customers and developers to change the requirements throughout the project, but only the customers have the authority to approve, disapprove and prioritize the ever-changing requirements (Koch, 2005), [57]. In traditional SDMs it increases complexity for accepting changing requirements while developing, and also increases and delivery time, as well as cost to deliver software product. Agile requirements prioritization techniques to support and deal with frequent changes in priority lists which have been identified as success issue to accommodate over changes [73]. In traditional development, software product with all features will be delivered at a time only after completion of software project. Customers are actively involved, and get higher priority in agile approaches rather than any traditional approaches. There is face to face communication and continuous feedback from customer (product owner) always happen in agile approach.

Figure 9 : Active customer involvement in agile approach Customers appreciate active participation in projects as it allows them to control the project and development process is more visible to them, as well as, they are kept up to date [73]. This customer involvement mitigates one of the most consistent problems on software projects: "What they will accept at the end of the project differs from what they told us at the beginning". This interaction helps the customer to form a better vision of the emerging product. Along with the ability to visualize the functionality that is coming based on having seen what was built so far, the customers develop a better understanding of their own needs and the vocabulary to express it to the developers [9]. Agile projects require a meaningful client involvement in every part of the project to provide constant feedback in an open and honest way (Wysocki, 2009), [57]. This feedback is a key element of agile methodologies, which is why the customer must be committed, knowledgeable, collaborative, representative, and empowered to avoid risk of failure (Boehm, 2002), [16]. People are the primary drivers of agile projects and agile teams work best when people are physically close and document preparation and dissemination are largely replaced by face-to-face communication and collaboration , [21].


# vii. Reduce cost and time

The study reports conducted by B. Bahli and ESA Zeid [77] that the development team found using the waterfall model to be an "unpleasant experience", while XP (an agile method) was found to be "beneficial and a good move from management". The XP project was delivered a bit less late (50% time-overrun, versus 60% for the traditional), and at a significantly reduced cost overrun (25%, compared to 50% cost overrun for the traditional project). Agile development involves less cost of development as rework, management, documentation and other non-development work related cost is reduced. Figure 11 : Design phase composition between waterfall and agile development According to (Boehm & Turner, 2005), agile approach design is simple which involves Designing for the battle, not the war. The motto is YAGNI (You Aren't Going to Need It). The antimotto is BDUF (Big Design Up Front). Strip designs down to cover just what you're developing. Since change is inevitable, planning for future functions is a waste of effort [30]. Customer gets to know regular and frequent status of the application and delivery is defined by fixed timescale. So, customer is assured of receiving some functionality by a fixed time period. Due to the short development life cycle through an iterative and incremental process, the agile methods have been used widely in business sectors where requirements are relatively unstable [26]. ix. Self organized team Agile teams are self organizing and roles and relationships evolve as necessary to meet objectives . Team composition in an agile project is usually cross-functional and self-organizing, without consideration for any existing corporate hierarchy or the corporate roles of team members [4]. Agile product development practices introduce changes in team culture in an attempt to bringing reciprocal effects of roalty and commitment to the team and projects (Sherehiy, Karwowski, & Layer, 2007). Team members normally take responsibility for tasks that deliver the functionality an iteration requires. They decide individually how to meet an iteration's requirements. Teams develop applications collaboratively and in cooperative environment. Agile alliance [5], claims that for a given problem size, "fewer people are needed if a lighter methodology is used, and more people are needed if a heavier methodology is used," and asserts that, "There is a limit to the size of problem that can be solved with a given number of people" [44].  According to (Boehm & Turner, 2005), agile approach design is simple which involves Designing for the battle, not the war. The motto is YAGNI (You Aren't Going to Need It). The anti-motto is BDUF (Big Design Up Front). Strip designs down to cover just what you're developing. Since change is inevitable, planning for future functions is a waste of effort [30]. In their research paper [46], (K Molokken & Ostvold, 2005), define agile method(s) as a flexible software development model(s), basis on evolutionary and incremental models; and also claim that, among the benefits of using these models are reduced software project overruns.

xii. Improves Software Quality Boehm, B., & Turner, R. (2004, May), Agile development methodologies (such as XP, Scrum, and ASD) promise higher customer satisfaction, lower defect rates, faster development times and a solution to rapidly changing requirements. Plan-driven approaches such as Cleanroom, the Personal Software Process, or methods based on the Capability Maturity Model promise predictability, stability, and high assurance [38].

The regular and continuous interaction between the customer and the developers have as their primary objective assuring that the product as built does what the customer needs for it to do and assures the usability of the product as well. The strong technical focus results in much better testing on an Agile project than in most other methods [9]. According to Charvat, (2003), agile practices: iterative and adaptive life cycles have the advantage of a continual testing throughout the project, which has a positive impact on quality [43]. Agile developers take responsibility for the quality of the code they write. In addition to producing cleaner code, it means that if there are testing specialists on the project, they will start their testing with better software, which always results in more effective testing and a better resulting product. In addition to, developers value the technical focus on testing and refactoring of agile methods increasing their motivation. There is also a perception of increased quality in software products and higher productivity when using some agile teams use practices like coding standards, peer reviews, and pair programming to assure that the code they produce is technically solid [73].

xiii. Increase business value, visibility, adaptability and reduce cost Agile software development accelerates the delivery of initial business value, and through a process of continuous planning and feedback, ensures that value continues to be maximized throughout the development process. ASD provides customer satisfaction through collaboration and frequent delivery of implemented features. By delivering working, tested, deployable software on an incremental basis, agile development delivers increased value, visibility and adaptability much earlier in the life cycle, significantly reducing project risk.  In a study by Boehm and Papaccio [72] discovered that a typical project experiences a 25% change in requirements, while yet another [Johnson] showed that 45% of features were never used. Agile approach aims to reduce waste and over-production by determining which parts are actually needed by the customer at each stage. In Agile approaches, delivering software on an incremental basis, customers give continuous feedback and agile team will always deliver products on time and on budget. As traditional project management isn't succeeding, more and more companies are turning to Agile development. According to the Standish Group's, [11] famous CHAOS Report of 2000, 25% of all projects fail outright through eventual cancellation, with no useful software deployed. Sadly, this represents a big improvement over CHAOS reports from past years. Recently, they conduct a survey for Agile implementation success rate, see figure 19.  


# Agile Adoption

Agile methods are highly being adopted because of expectations that these methods can bring development success (Esfahani, Yu, & Annosi, 2010). One of the main reasons for success with agile methods is that they are highly adaptive , [38]. Figure 1 reveals the current levels of agile adoption. In this case, 71% of respondents indicated that they work in organizations that have succeeded at agile and an additional 15% work in organizations that have tried agile but have not yet succeed at it. According to (West & Grant, 2010), "in the past few years, Agile processes have not only gained increasing adoption levels; they have also rapidly joined the mainstream of development approaches" [28]. Mary large companies including HP, IBM, Oracle, and Microsoft use Agile methodologies [76] -and more and more smaller organisations turn Agile each year. In their study (West & Grant, 2010), conducted by Forrester Research in 2009, agile software development processes were in use in 35% of organizations, and another 16% of organizations used an iterative development approach, while only 13% of organization use a Waterfall approach. However, nearly 31% did not use a formal development methodology [28]. The main reasons behind for adopting Agile approaches rather than plan-driven approaches relate to: rapid changes; need for rapid results; emergent requirements , [38]. According to Charvat, (2003), , & Perrin, (2008), Agile methodologies have numerous advantages including that they: adapt very well to change and dynamism; are people-oriented and value-driven, rather than process-oriented and plan-driven; mitigate risks by demonstrating values and functionalities up front in the development process; provide a faster time to market; improve productivity (by reducing the amount of documentation) and will fail early/quickly and painlessly, if a project is not doable [34], [33], [32].

A state of Agile survey 2011, conducted by versionone Inc. result shows: the top three reasons for adopting Agile to -accelerate time to market, increase productivity, and to more easily manage changing priorities. Prior to adoption, respondents said productivity and time to market ranked as their top reasons to adopt agile. But experienced agile users said actual benefits were primarily project visibility (77%) and the ability to manage changing priorities (84%). 5. Conclusion Agile software development methodologies are evolutionary and incremental models have become increasingly popular in software development industry. Through, in many organizations, agile system development methods at adoption stage, agile methods might start to become well-established processes of these small, mid-level, even large organizations. There is increasing need to have a deeper understanding of agile methods in use in software development industry; as well as, have a better understanding -the benefits of agile approach as for accepting agile methods into their development style and for cope-up with their dynamic business needs. In this paper, we present main issues of agile numerous benefits in comparison to the traditional approach which significantly improves software development process in many ways. We also provide with this paper, the current adoption state of Agile software development with different current survey results with graphs. The purpose of this paper is to provide an in-depth understandingthe benefits of agile development approach into the software development industry, as well as provide a comparison study report of ASDM over TSDM. 
![and "opportunistic development processes" [86]. Most of agile development methods promote development, teamwork, collaboration and process adaptability throughout the life-cycle of the project [4].](image-2.png "")
1![Figure 1 : An example of agile software development methodology: Scrum (Source: [53])](image-3.png "Figure 1 :")
2![Figure 2 : State of Agile Survey Results 2011 by Version One Inc.](image-4.png "Figure 2 :")
![i. Evolutionary Approach Agile software development is a highly collaborative and evolutionary approach [101]. Agile methods become more popular in the software development industry. In their different research papers, (Boehm, & Turner, 2005; Larman & Basili, 2003; Greer, & Ruhe, 2004; Dybå, & Dingsøyr, 2008; Paetsch, Eberlein, 2003; Abrahamsson, Warsta, 2003;](image-5.png "")
3![Figure 3 : Iterative and incremental agile development process (source: agile-development-tools.com) ii. Lightweight Methods Boehm, B., & Turner, R. (2005), generalize agile methods are lightweight processes that employ short iterative cycles, actively involve users to establish, prioritize, and verify requirements, and rely on a team's tacit knowledge as opposed to documentation[30]. G Perera, & MSD Fernando (2007), also describe Agile practice is a customer oriented, light-weight software development paradigm, best suited for small size development teams in projects under vague and changing requirements[65]. A number of agile software development methods such as extreme programming (XP), feature-driven development, crystal clear method, scrum, dynamic systems development, and adaptive software development, fall into this category[22]. Traditional Software Development Methods (TSDMs) including waterfall and spiral models are often called heavyweight development methods[26]. These methods involves extensive planning, predefine process phases, heavy documentation and long term design process. Lightweight methodologies put extreme emphasis on delivering working code or product while downplayning the importance of formal process and comprehensive documentation[23].](image-6.png "Figure 3 :")
4![Figure 4 : Iterative process and incremental delivery software products (source: [4]) iv. Highly tolerant of change requirementsThe main difference between heavyweight and agile methodologies is the acceptance of change. It is the ability to respond to change that often determines the success or failure of a software project[18]. Heavyweight methods freeze product functionality and disallow change. Agile systems development methods](image-7.png "Figure 4 :")
![. Agile software development promotes adaptive planning, evolutionary development and delivery, and encourages rapid and flexible response to change [4].](image-8.png "")
5![Figure 5 : Agile vs. traditional requirements change management (Source: www.versionone.com)](image-9.png "Figure 5 :")
6![Figure 6 : Agile vs. traditional requirements change management (source: [57])](image-10.png "Figure 6 :")
7![Figure 7 : Cost of change for agile and conventional development process](image-11.png "Figure 7 :C")
8![Figure 8 : Agile approach prioritized requirements (Source: www.agilemodeling.com [6]) vi. Active customer involvement & feedback](image-12.png "Figure 8 :")
10![Figure 10 : Cost for agile development process and conventional development (Source: http://www.thoughtworks.com) viii. Short design phase involves early feedback from clients In traditional, lifecycle based developments usually follow Big Design Up Front and Big Requirements Up Front development techniques. With these approaches, comprehensive requirements document and design document are developed early in the project lifecycle which is used to guide the design and implementation efforts. It is typically months, if not years, before stakeholders are shown working software which implements their requirements and design. In terms of the traditional project phases (requirements,](image-13.png "Figure 10 :")
12![Figure 12 : Problem size; number of people needed (Source: Cockburn, 2007) x. Documentation Agile development improvement in productivity, reduction development cost and reduction in time-tomarket (Reifer, 2002), [40]. Agile approaches, emphasis](image-14.png "Figure 12 :C")
13![Figure 13 : Agile vs. Traditional development documentation through the SDLC (Source: www.agilemodeling.com [6]) xi. Design Simplicity](image-15.png "Figure 13 :")
14![Figure 14 : Comparison of feedback cycles with traditional approaches (Source: http://www.ambysoft.com)](image-16.png "Figure 14 :")
15![Figure 15 : Agile development value proposition (Source: [10])](image-17.png "Figure 15 :")
17![Figure 17 : Agile development degree of success](image-18.png "Figure 17 :")
1921![Figure 19 : Agile implementation success rate by The Standish group (Source: http://bolg.standishgroup.com/) [11]Survey result shows: most of the clients are asking for Agile implementation due to unprecedented benefits of Agile, over the other methodology, such as time to market, quality, defect rate, customer satisfaction, continuous end user feedback. This requires vendors to quickly turnaround and respond, to market demands, which eventually forces the organization to reevaluate the present onshore-offshore model.](image-19.png "Figure 19 :Figure 21 :")
22![Figure 22 : Forrester Research Agile Adoption rate rises (Source: http://www.forrester.com [13]) Another survey conducted by Scott Ambler has consistently (2008, 2010 & 2011) shown that Agile and Iterative Projects have been more successful. Apart from the fact that Agile has been consistently been more successful compared to traditional approach.IV.](image-20.png "Figure 22 :")
2023![Figure 20 : Agile projects success rate by Scott Ambler (Source: www.ambysoft.com/surveys/)](image-21.png "Figure 20 :Figure 23 :")
24![Figure 24 : Reasons for adopting Agile from "A state of Agile survey 2011" (Source: www.versionone.com)](image-22.png "Figure 24 :")
			© 2013 Global Journals Inc. (US) Global Journal of Computer Science and Technology
			© 2013 Global Journals Inc. (US)
		
		
			

				


* 
	
		Empirical findings in agile methods
		
			MLindvall
		
		
			VBasili
		
		
			BBoehm
		
		
			PCosta
		
		
			KDangle
		
		
			FShull
		
		
			..Zelkowitz
		
		
			M
		
		
			2002. 2002
			
		
	




* 
	
		
			PMeso
		
		
			RJain
		
		Agile software development: adaptive systems principles and best
				
			2006
		
	




* 
	
		Get ready for agile methods, with care
		
			BBoehm
		
	
	
		Computer
		
			35
			1
			
			2002
		
	




* 
	
		
	
	
		Information Systems Management
		
			23
			3
			
		
	




* 
	
		New directions on agile methods: a comparative analysis
		
			PAbrahamsson
		
		
			JWarsta
		
		
			MTSiponen
		
		
			JRonkainen
		
	
	
		Proceedings. 25th International Conference on
				25th International Conference on
		
			Ieee
			2003. May. 2003
			
		
	
	Software Engineering




* 
	
		Agile software development: The business of innovation
		
			JHighsmith
		
		
			ACockburn
		
	
	
		Computer
		
			34
			9
			
			2001
		
	




* 
	
		Issues and Challenges of Agile Software Development with Scrum
		
			JCho
		
	
	
		Issues in Information Systems
		
			9
			2
			
			2008
		
	




* 
	
		Factors that significantly impact the implementation of an agile software development methodology
		
			JALivermore
		
	
	
		Journal of Software
		
			3
			4
			
			2008
		
	




* 
	
		Agile development: Mainstream adoption has changed agility
		
			DWest
		
		
			TGrant
		
		
			MGerush
		
		
			DSilva
		
		
			2010
			Forrester Research
		
	




* 
	
		Software release planning: an evolutionary and iterative approach
		
			DGreer
		
		
			GRuhe
		
	
	
		Information and Software Technology
		
			46
			4
			
			2004
		
	




* 
	
		Management challenges to implementing agile processes in traditional development organizations. Software
		
			BBoehm
		
		
			RTurner
		
		
			2005
			IEEE
			22
			
		
	




* 
	
		Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum
		
			OSalo
		
		
			PAbrahamsson
		
	
	
		Software
		
			2
			1
			
			2008
		
	
	IET




* 
	
		identifying the critical factors in software development methodology FIT
		
			JLemétayer
		
		
			2010
		
	




* 
	
		Agile software requirements: Lean requirements practices for teams, programs, and the enterprise
		
			DLeffingwell
		
		
			2007
			Addison-Wesley Professional
		
	




* 
	
		Agile Software Development: It's about Feedback and Change
		
			LWilliams
		
		
			ACockburn
		
	
	
		IEEE Computer
		
			
			June 2003
		
	




* 
	
		Using risk to balance agile and plan-driven methods
		
			BBoehm
		
		
			RTurner
		
	
	
		Computer
		
			36
			6
			
			2003
		
	




* 
	
		
			TDybå
		
		
			TDingsøyr
		
		Empirical studies of agile software development: A systematic review. Information and software technology
				
			2008
			50
			
		
	




* 
	
		Agile software development, the people factor
		
			ACockburn
		
		
			JHighsmith
		
	
	
		Computer
		
			34
			11
			
			2001
		
	




* 
	
		Challenges of migrating to agile methodologies
		
			SNerur
		
		
			RMahapatra
		
		
			GMangalaraj
		
	
	
		Project management methodologies. Selecting, implementig, and supporting
				
			2005. 2003
			48
			
		
	
	Charvat, J.




* 
	
		Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum
		
			OSalo
		
		
			PAbrahamsson
		
	
	
		Software
		
			2
			1
			
			2008
		
	
	IET




* 
	
		Agile software development: The business of innovation
		
			JHighsmith
		
		
			ACockburn
		
	
	
		Computer
		
			34
			9
			
			2001
		
	




* 
	
		Agile Software Development Methods
		
			PAbrahamsson
		
		
			OSolo
		
		
			JRonkainen
		
		
			JWarsta
		
		
			2002
		
		
			VTT technical Research Centre of Finland
		
	




* 
	
		Using risk to balance agile and plan-driven methods
		
			BBoehm
		
		
			RTurner
		
	
	
		Computer
		
			36
			6
			
			2003
		
	




* 
	
		Balancing agility and discipline: Evaluating and integrating agile and plan-driven methods
		
			BBoehm
		
		
			RTurner
		
	
	
		Proceedings. 26th International Conference on
				26th International Conference on
		
			IEEE
			2004. May. 2004. 2004
			
		
	
	Software Engineering




* 
	
		How good are agile methods
		
			DJReifer
		
	
	
		Software
				
			IEEE
			2002
			19
			
		
	




* 
	
		A review of enterprise agility: Concepts, frameworks, and attributes
		
			BSherehiy
		
		
			WKarwowski
		
		
			JKLayer
		
	
	
		International Journal of Industrial Ergonomics
		
			37
			5
			
			2007
		
	




* 
	
		An iterative improvement process for agile software development
		
			OSalo
		
		
			PAbrahamsson
		
	
	
		Software Process: Improvement and Practice
				
			2007
			12
			
		
	




* 
	
		Project management methodologies. Selecting, implementig, and supporting
		
			JCharvat
		
		
			2003
		
	




* 
	
		
		
			ACockburn
		
		
	
	
		The Methodology Space?
		
	




* 
	
		Agile process improvement
		
			KSouthwell
		
	
	
		TickIT International Journal
		
			
			2002
		
	




* 
	
		A comparison of software project overruns-flexible versus sequential development models. Software Engineering
		
			KMolokken-Ostvold
		
		
			MJorgensen
		
	
	
		IEEE Transactions on
		
			31
			9
			
			2005
		
	




* 
	
		The impact of agile methods on software project management
		
			MCoram
		
		
			SBohner
		
	
	
		ECBS'05. 12th IEEE International Conference and Workshops on the
				
			IEEE
			2005. April. 2005
			
		
		
			In Engineering of Computer-Based Systems
		
	




* 
	
		Levels of Agile Planning: From Enterprise Product Vision to Team Stand-up
		
			HSmits
		
		
			2006
		
	
	Rally Software Development Corporation Whitepaper




* 
	
		The impact of agile practices on communication in software development
		
			MPikkarainen
		
		
			JHaikara
		
		
			OSalo
		
		
			PAbrahamsson
		
		
			JStill
		
	
	
		Empirical Software Engineering
		
			13
			3
			
			2008
		
	




* 
	
		Effective project management: traditional, agile, extreme
		
			RKWysocki
		
		
			2011
			Wiley
		
	




* 
	
		Agile software development: evaluating the methods for your organization
		
			ASKoch
		
		
			2005
		
	
	Artech house




* 
	
		DSDM, dynamic systems development method: the method in practice
		
			JStapleton
		
		
			1997
			Addison-Wesley Professional
		
	




* 
	
		Adaptive software development
		
			JAHighsmith
		
		
			2000
			Dorset House
		
	




* 
	
		Crystal clear: a humanpowered methodology for small teams
		
			ACockburn
		
		
			2005
			Addison-Wesley Professional
		
	




* 
	
		A Practical Guide to Feature Driven Development
		
			SPalmer
		
		
			Felsing
		
		
			2002
			Prentice Hall
		
	




* 
	
		Manifesto for agile software development. The Agile Alliance
		
			KBeck
		
		
			MBeedle
		
		
			AVan Bennekum
		
		
			ACockburn
		
		
			WCunningham
		
		
			MFowler
		
		
			..Thomas
		
		
			D
		
		
			2001
			
		
	




* 
	
		Assumptions underlying agile software-development processes
		
			DTurk
		
		
			FRobert
		
		
			BRumpe
		
	
	
		Journal of Database Management (JDM)
		
			16
			4
			
			2005
		
	




* 
	
		Agility through discipline: A debate
		
			KBeck
		
		
			BBoehm
		
	
	
		Computer
		
			36
			6
			
			2003
		
	




* 
	
		Enhanced agile software developmenthybrid paradigm with LEAN practice. In Industrial and Information Systems
		
			GI U SPerera
		
		
			MS DFernando
		
	
	
		ICIIS 2007. International Conference on
				
			IEEE
			2007. August. 2007
			
		
	




* 
	
		Agile Software Development
		
			AGarg
		
		
			2009
		
	




* 
	
		Agile methodologists agree on something
		
			MFowler
		
		
			JHighsmith
		
	
	
		Software Development
		
			9
			
			2001
		
	




* 
	
		The Great Methodologies Debate: Part 1
		
			JHighsmith
		
		
			AVTraditional
		
		
			MLove
		
		
			NWar
		
	
	
		The Journal
		
			12
			14
			2001
		
	




* 
	
		The Great Methodologies Debate: Part 2
		
			JHighsmith
		
		
			AVTraditional
		
		
			MLove
		
		
			NWar
		
	
	
		The Journal
		
			12
			14
			2001
		
	




* 
	
		Scaling software agility: best practices for large enterprises
		
			DLeffingwell
		
		
			2007
			Addison-Wesley Professional
		
	




* 
	
		Can agile and traditional systems development approaches coexist? An ambidextrous view
		
			VVinekar
		
		
			CWSlinkman
		
		
			SNerur
		
	
	
		Information systems management
		
			23
			3
			
			2006
		
	




* 
	
		Scaling software agility: best practices for large enterprises
		
			DLeffingwell
		
		
			2007
			Addison-Wesley Professional
		
	




* 
	
		
			KSchwaber
		
		
			MBeedle
		
		Agile software development with Scrum
				
			Prentice Hall
			2002
			18
		
	
	PTR Upper Saddle River^ eNJ NJ




* 
	
		Agile and iterative development: a manager's guide
		
			CLarman
		
		
			2004
			Addison-Wesley Professional
		
	




* 
	
		Agile software development ecosystems
		
			JAHighsmith
		
		
			2002
			Addison-Wesley Professional
		
	




* 
	
		Agile software development: it's about feedback and change
		
			LWilliams
		
		
			ACockburn
		
	
	
		IEEE Computer
		
			36
			6
			
			2003
		
	




* 
	
		Balancing plan-driven and agile methods in software engineering project courses
		
			BBoehm
		
		
			DPort
		
		
			AWBrown
		
	
	
		Computer Science Education
		
			12
			3
			
			2002
		
	




* 
	
		Understanding and controlling software costs. Software Engineering
		
			BWBoehm
		
		
			PNPapaccio
		
	
	
		IEEE Transactions on
		
			14
			10
			
			1988
		
	




* 
	
		A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case
		
			KPetersen
		
		
			CWohlin
		
	
	
		Journal of Systems and Software
		
			82
			9
			
			2009
		
	




* 
	
		What do we know about agile software development? Software
		
			TDyba
		
		
			TDingsoyr
		
		
			2009
			IEEE
			26
			
		
	




* 
	
		Breaking the Addiction to Process: An Introduction to Agile Project Management
		
			EScanlon-Thomas
		
		
			2011
		
	
	Itgp




* 
	
		The role of knowledge creation in adopting extreme programming model: an empirical study
		
			BBahli
		
		
			EAZeid
		
	
	
		Information and Communications Technology, 2005. Enabling Technologies for the New Knowledge Society: ITI 3rd International Conference on
				
			IEEE
			2005. December
			
		
	




* 
	
		Agile Versus Traditional: Make Love, Not War
		
			RGlass
		
	
	
		Cutter IT Journal
		
			
			Dec. 2001
		
	




* 
	
		Iterative and incremental developments. a brief history
		
			CLarman
		
		
			VRBasili
		
	
	
		Computer
		
			36
			6
			
			2003
		
	




* 
	
		Requirements engineering and agile software development
		
			FPaetsch
		
		
			AEberlein
		
		
			FMaurer
		
	
	
		Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003. WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on
				
			IEEE
			2003. June
			
		
	




* 
	
		An evolutionary lifecycle model with Agile practices for software development at ABB. In Engineering of Complex Computer Systems
		
			ADagnino
		
	
	
		Eighth IEEE International Conference on
				
			IEEE
			2002. December. 2002
			
		
	




* 
	
		Embracing change with extreme programming
		
			KBeck
		
	
	
		Computer
		
			32
			10
			
			1999
		
	




* 
	
		Agile and Iterative Development: A Manager's Guide
		
			CLarman
		
		
			2004
			Addison Wesley
			Boston
		
	




* 
	
		A History of Iterative and Incremental Development
		
			CLarman
		
		
			VBasili
		
	
	
		IEEE Computer
		
			36
			6
			
			June 2003
		
	




* 
	
		Iterative Enhancement: A Practical Technique for Software Development
		
			VRBasili
		
		
			AJTurner
		
	
	
		IEEE Transactions on Software Engineering
		
			1
			4
			
			1975
		
	




* 
	
		
			BCurtis
		
		Three Problems Overcome with Behavioral Models of the Software Development Process (Panel)," International Conference on Software Engineering
				Pittsburgh, PA
		
			1989