agile sdlc (wiki)

7/30/2019 Agile SDLC (Wiki)

1/12

Agile software development Page 1

Agile software development

From Wikipedia, the free encyclopedia

Agile software development refers to a group ofsoftware development methodologiesbased on iterative

development, where requirements and solutions evolve through collaboration between self-organizing cross-

functional teams. The term was coined in the year 2001 when theAgile Manifestowas formulated.

Agile methods generally promote a disciplined project management process that encourages frequent

inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and

accountability, a set of engineering best practices that allow for rapid delivery of high-quality software, and a

business approach that aligns development with customer needs and company goals. Conceptual foundations

of this framework are found in modern approaches tooperations managementand analysis, such aslean

manufacturing,soft systems methodology,speech acttheory (network of conversations approach), andSix

Sigma.

Introduction

There are many specific agile development methods. Most promote developmentiterations, teamwork,

collaboration, and process adaptability throughout the life-cycle of the project.

Agile methods break tasks into small increments with minimal planning, and don't directly involve long-term

planning. Iterations are short time frames ("timeboxes") that typically last from one to four weeks. Each

iteration is worked on by a team through a full software development cycle including planning,requirements

analysis, design, coding,unit testing, andacceptance testingwhen a working product is demonstrated to

stakeholders. This helps minimize overall risk, and lets the project adapt to changes quickly. Stakeholders

produce documentation as required. An iteration may not add enough functionality to warrant a market

release, but the goal is to have an available release (with minimalbugs) at the end of each iteration. Multipleiterations may be required to release a product or new features.

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. Team members normally take

responsibility for tasks that deliver the functionality an iteration requires. They decide individually how to

meet an iteration's requirements.

Agile methods emphasize face-to-face communication over written documents when the team is all in the

same location. When a team works in different locations, they maintain daily contact through

videoconferencing, voice, e-mail, etc.

Most agile teams work in a single open office (called bullpen), which facilitates such communication. Team

size is typically small (5-9 people) to help make team communication and team collaboration easier. Larger

development efforts may be delivered by multiple teams working toward a common goal or different parts of

an effort. This may also require a coordination of priorities across teams.
http://en.wikipedia.org/wiki/Software_development_methodologieshttp://en.wikipedia.org/wiki/Software_development_methodologieshttp://en.wikipedia.org/wiki/Software_development_methodologieshttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Operations_managementhttp://en.wikipedia.org/wiki/Operations_managementhttp://en.wikipedia.org/wiki/Operations_managementhttp://en.wikipedia.org/wiki/Lean_manufacturinghttp://en.wikipedia.org/wiki/Lean_manufacturinghttp://en.wikipedia.org/wiki/Lean_manufacturinghttp://en.wikipedia.org/wiki/Lean_manufacturinghttp://en.wikipedia.org/wiki/Soft_systems_methodologyhttp://en.wikipedia.org/wiki/Soft_systems_methodologyhttp://en.wikipedia.org/wiki/Soft_systems_methodologyhttp://en.wikipedia.org/wiki/Speech_acthttp://en.wikipedia.org/wiki/Speech_acthttp://en.wikipedia.org/wiki/Speech_acthttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Iterations#Project_managementhttp://en.wikipedia.org/wiki/Iterations#Project_managementhttp://en.wikipedia.org/wiki/Iterations#Project_managementhttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Requirements_analysishttp://en.wikipedia.org/wiki/Requirements_analysishttp://en.wikipedia.org/wiki/Requirements_analysishttp://en.wikipedia.org/wiki/Requirements_analysishttp://en.wikipedia.org/wiki/Unit_testhttp://en.wikipedia.org/wiki/Unit_testhttp://en.wikipedia.org/wiki/Unit_testhttp://en.wikipedia.org/wiki/Acceptance_testhttp://en.wikipedia.org/wiki/Acceptance_testhttp://en.wikipedia.org/wiki/Acceptance_testhttp://en.wikipedia.org/wiki/Software_bughttp://en.wikipedia.org/wiki/Software_bughttp://en.wikipedia.org/wiki/Software_bughttp://en.wikipedia.org/wiki/Software_bughttp://en.wikipedia.org/wiki/Acceptance_testhttp://en.wikipedia.org/wiki/Unit_testhttp://en.wikipedia.org/wiki/Requirements_analysishttp://en.wikipedia.org/wiki/Requirements_analysishttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Iterations#Project_managementhttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Speech_acthttp://en.wikipedia.org/wiki/Soft_systems_methodologyhttp://en.wikipedia.org/wiki/Lean_manufacturinghttp://en.wikipedia.org/wiki/Lean_manufacturinghttp://en.wikipedia.org/wiki/Operations_managementhttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Software_development_methodologies


2/12


No matter what development disciplines are required, each agile team will contain a customer representative.

This person is appointed by stakeholders to act on their behalf and makes a personal commitment to being

available for developers to answer mid-iteration problem-domain questions. At the end of each iteration,

stakeholders and the customer representative review progress and re-evaluate priorities with a view to

optimizing thereturn on investmentand ensuring alignment with customer needs and company goals.

Most agile implementations use a routine and formal daily face-to-face communication among team

members. This specifically includes the customer representative and any interested stakeholders as observers.

In a brief session, team members report to each other what they did yesterday, what they intend to do today,

and what their roadblocks are. This standing face-to-face communication prevents problems being hidden.

Agile emphasizes working software as the primary measure of progress. This, combined with the preference

for face-to-face communication, produces less written documentation than other methodsthough, in an

agile project, documentation and other artifacts rank equally with working product. The agile method

encourages stakeholders to prioritize them with other iteration outcomes based exclusively on business value

perceived at the beginning of the iteration.

Specific tools and techniques such ascontinuous integration, automated orxUnit test,pair programming,test

driven development,design patterns,domain-driven design,code refactoringand other techniques are oftenused to improve quality and enhance project agility.

History

The modern definition of agile software development evolved in the mid-1990s as part of a reaction against

"heavyweight" methods, perceived to be typified by a heavily regulated, regimented, micro-managed use of

thewaterfall modelof development. The processes originating from this use of the waterfall model were seen

as bureaucratic, slow, demeaning, and inconsistent with the ways that software developers actually perform

effective work. A case can be made that agile and iterative development methods mark a return to

development practice from early in the history of software development.[1]

Initially, agile methods were called"lightweight methods." In 2001, prominent members of the community met atSnowbird,Utah, and adopted

the name "agile methods." Later, some of these people formed The Agile Alliance,[2]

a non-profit organization

that promotes agile development.

An adaptive software development process was introduced in a paper by Edmonds (1974).[3]

Notable early

Agile methods includeScrum(1995),Crystal Clear,Extreme Programming(1996),Adaptive Software

Development,Feature Driven Development, andDynamic Systems Development Method(DSDM) (1995).

These typically are referred to as Agile Methodologies since theAgile Manifestowas published in 2001.

Principles behind agile methodsSee also:Agile Manifesto

Agile methods are a family of development processes, not a single approach to software development. In

2001, 17 prominent figures[4]

in the field of agile development (then called "light-weight methods") came

together at theSnowbird ski resortinUtahto discuss ways of creating software in a lighter, faster, more

people-centric way. They coined the termAgile Software Developmentand created theAgile Manifesto,
http://en.wikipedia.org/wiki/Return_on_investmenthttp://en.wikipedia.org/wiki/Return_on_investmenthttp://en.wikipedia.org/wiki/Return_on_investmenthttp://en.wikipedia.org/wiki/Continuous_integrationhttp://en.wikipedia.org/wiki/Continuous_integrationhttp://en.wikipedia.org/wiki/Continuous_integrationhttp://en.wikipedia.org/wiki/XUnithttp://en.wikipedia.org/wiki/XUnithttp://en.wikipedia.org/wiki/XUnithttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/Test_driven_developmenthttp://en.wikipedia.org/wiki/Test_driven_developmenthttp://en.wikipedia.org/wiki/Test_driven_developmenthttp://en.wikipedia.org/wiki/Test_driven_developmenthttp://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29http://en.wikipedia.org/wiki/Domain-driven_designhttp://en.wikipedia.org/wiki/Domain-driven_designhttp://en.wikipedia.org/wiki/Domain-driven_designhttp://en.wikipedia.org/wiki/Refactoringhttp://en.wikipedia.org/wiki/Refactoringhttp://en.wikipedia.org/wiki/Refactoringhttp://en.wikipedia.org/wiki/Waterfall_modelhttp://en.wikipedia.org/wiki/Waterfall_modelhttp://en.wikipedia.org/wiki/Waterfall_modelhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-0http://en.wikipedia.org/wiki/Agile_software_development#cite_note-0http://en.wikipedia.org/wiki/Agile_software_development#cite_note-0http://en.wikipedia.org/wiki/Snowbird,_Utahhttp://en.wikipedia.org/wiki/Snowbird,_Utahhttp://en.wikipedia.org/wiki/Snowbird,_Utahhttp://en.wikipedia.org/wiki/Utahhttp://en.wikipedia.org/wiki/Utahhttp://en.wikipedia.org/wiki/Utahhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-1http://en.wikipedia.org/wiki/Agile_software_development#cite_note-1http://en.wikipedia.org/wiki/Agile_software_development#cite_note-1http://en.wikipedia.org/wiki/Agile_software_development#cite_note-edmonds1974-2http://en.wikipedia.org/wiki/Agile_software_development#cite_note-edmonds1974-2http://en.wikipedia.org/wiki/Agile_software_development#cite_note-edmonds1974-2http://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Crystal_Clear_%28software_development%29http://en.wikipedia.org/wiki/Crystal_Clear_%28software_development%29http://en.wikipedia.org/wiki/Crystal_Clear_%28software_development%29http://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Adaptive_Software_Developmenthttp://en.wikipedia.org/wiki/Adaptive_Software_Developmenthttp://en.wikipedia.org/wiki/Adaptive_Software_Developmenthttp://en.wikipedia.org/wiki/Adaptive_Software_Developmenthttp://en.wikipedia.org/wiki/Feature_Driven_Developmenthttp://en.wikipedia.org/wiki/Feature_Driven_Developmenthttp://en.wikipedia.org/wiki/Feature_Driven_Developmenthttp://en.wikipedia.org/wiki/Dynamic_Systems_Development_Methodhttp://en.wikipedia.org/wiki/Dynamic_Systems_Development_Methodhttp://en.wikipedia.org/wiki/Dynamic_Systems_Development_Methodhttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-3http://en.wikipedia.org/wiki/Agile_software_development#cite_note-3http://en.wikipedia.org/wiki/Agile_software_development#cite_note-3http://en.wikipedia.org/wiki/Snowbird_ski_resorthttp://en.wikipedia.org/wiki/Snowbird_ski_resorthttp://en.wikipedia.org/wiki/Snowbird_ski_resorthttp://en.wikipedia.org/wiki/Utahhttp://en.wikipedia.org/wiki/Utahhttp://en.wikipedia.org/wiki/Utahhttp://en.wikipedia.org/wiki/Agile_Software_Developmenthttp://en.wikipedia.org/wiki/Agile_Software_Developmenthttp://en.wikipedia.org/wiki/Agile_Software_Developmenthttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Software_Developmenthttp://en.wikipedia.org/wiki/Utahhttp://en.wikipedia.org/wiki/Snowbird_ski_resorthttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-3http://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Agile_Manifestohttp://en.wikipedia.org/wiki/Dynamic_Systems_Development_Methodhttp://en.wikipedia.org/wiki/Feature_Driven_Developmenthttp://en.wikipedia.org/wiki/Adaptive_Software_Developmenthttp://en.wikipedia.org/wiki/Adaptive_Software_Developmenthttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Crystal_Clear_%28software_development%29http://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Agile_software_development#cite_note-edmonds1974-2http://en.wikipedia.org/wiki/Agile_software_development#cite_note-1http://en.wikipedia.org/wiki/Utahhttp://en.wikipedia.org/wiki/Snowbird,_Utahhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-0http://en.wikipedia.org/wiki/Waterfall_modelhttp://en.wikipedia.org/wiki/Refactoringhttp://en.wikipedia.org/wiki/Domain-driven_designhttp://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29http://en.wikipedia.org/wiki/Test_driven_developmenthttp://en.wikipedia.org/wiki/Test_driven_developmenthttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/XUnithttp://en.wikipedia.org/wiki/Continuous_integrationhttp://en.wikipedia.org/wiki/Return_on_investment


3/12


widely regarded as the canonical definition of agile development and accompanying agile principles. The Agile

Manifesto states:

We are uncovering better ways of developing software by doing it and helping others do it. Through this work

we have come to value:

Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Some of the principles behind the Agile Manifesto[5]

are:

Customer satisfaction by rapid, continuous delivery of useful software Working software is delivered frequently (weeks rather than months) Working software is the principal measure of progress Even late changes in requirements are welcomed (this does not mean code & run. Instead removing an

existing feature or moving a deadline forward to accommodate late/unplanned feature requests)

Close, daily cooperation between business people and developers Face-to-face conversation is the best form of communication (Co-location) Projects are built around motivated individuals, who should be trusted Continuous attention to technical excellence and good design Simplicity Self-organizing teams Regular adaptation to changing circumstances

The manifesto spawned a movement in the software industry known as agile software development.

In 2005,Alistair CockburnandJim Highsmithgathered another group of peoplemanagement experts, this

timeand wrote an addendum, known as thePM Declaration of Interdependence.

The functioning principles of Agile can be found inlean manufacturingandsix sigma. These concepts include

error proofing, eliminating waste, creating flow, adding customer value, and empowering workers. The

concepts were first formally espoused in the 14 principles of theToyota Way, the two pillars of the Toyota

Production System (Just-in-timeandsmart automation), the5S methodology, and Demings14 points. These

have been summarized in the seven points oflean software development..

Comparison with other methods

Agile methods are sometimes characterized as being at the opposite end of the spectrum from "plan-driven"

or "disciplined" methods. This distinction is misleading, as it implies that agile methods are "unplanned" or

"undisciplined". A more accurate distinction is that methods exist on a continuum from "adaptive" to

"predictive".[6]

Agile methods lie on the "adaptive" side of this continuum.
http://en.wikipedia.org/wiki/Agile_software_development#cite_note-manifestoprinciples-4http://en.wikipedia.org/wiki/Agile_software_development#cite_note-manifestoprinciples-4http://en.wikipedia.org/wiki/Alistair_Cockburnhttp://en.wikipedia.org/wiki/Alistair_Cockburnhttp://en.wikipedia.org/wiki/Alistair_Cockburnhttp://en.wikipedia.org/wiki/Jim_Highsmithhttp://en.wikipedia.org/wiki/Jim_Highsmithhttp://en.wikipedia.org/wiki/Jim_Highsmithhttp://en.wikipedia.org/wiki/PM_Declaration_of_Interdependencehttp://en.wikipedia.org/wiki/PM_Declaration_of_Interdependencehttp://en.wikipedia.org/wiki/PM_Declaration_of_Interdependencehttp://en.wikipedia.org/wiki/Lean_manufacturinghttp://en.wikipedia.org/wiki/Lean_manufacturinghttp://en.wikipedia.org/wiki/Lean_manufacturinghttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/The_Toyota_Wayhttp://en.wikipedia.org/wiki/The_Toyota_Wayhttp://en.wikipedia.org/wiki/The_Toyota_Wayhttp://en.wikipedia.org/wiki/Just-in-time_%28business%29http://en.wikipedia.org/wiki/Just-in-time_%28business%29http://en.wikipedia.org/wiki/Just-in-time_%28business%29http://en.wikipedia.org/wiki/Autonomationhttp://en.wikipedia.org/wiki/Autonomationhttp://en.wikipedia.org/wiki/Autonomationhttp://en.wikipedia.org/wiki/5S_%28methodology%29http://en.wikipedia.org/wiki/5S_%28methodology%29http://en.wikipedia.org/wiki/5S_%28methodology%29http://en.wikipedia.org/wiki/W._Edwards_Deminghttp://en.wikipedia.org/wiki/W._Edwards_Deminghttp://en.wikipedia.org/wiki/W._Edwards_Deminghttp://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004App-5http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004App-5http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004App-5http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004App-5http://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/W._Edwards_Deminghttp://en.wikipedia.org/wiki/5S_%28methodology%29http://en.wikipedia.org/wiki/Autonomationhttp://en.wikipedia.org/wiki/Just-in-time_%28business%29http://en.wikipedia.org/wiki/The_Toyota_Wayhttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Lean_manufacturinghttp://en.wikipedia.org/wiki/PM_Declaration_of_Interdependencehttp://en.wikipedia.org/wiki/Jim_Highsmithhttp://en.wikipedia.org/wiki/Alistair_Cockburnhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-manifestoprinciples-4


4/12


Adaptive methods focus on adapting quickly to changing realities. When the needs of a project change, an

adaptive team changes as well. An adaptive team will have difficulty describing exactly what will happen in the

future. The further away a date is, the more vague an adaptive method will be about what will happen on that

date. An adaptive team can report exactly what tasks are being done next week, but only which features are

planned for next month. When asked about a release six months from now, an adaptive team may only be

able to report the mission statement for the release, or a statement of expected value vs. cost.

Predictive methods, in contrast, focus on planning the future in detail. A predictive team can report exactly

what features and tasks are planned for the entire length of the development process. Predictive teams have

difficulty changing direction. The plan is typically optimized for the original destination and changing direction

can cause completed work to be thrown away and done over differently. Predictive teams will often institute a

change control boardto ensure that only the most valuable changes are considered.

Agile methods have much in common with the "Rapid Application Development" techniques from the

1980/90s as espoused by James Martin and others.

Contrasted with other iterative development methods

Most agile methods share otheriterative and incremental developmentmethods' emphasis on buildingreleasable software in short time periods. Agile development differs from other development models: in this

model time periods are measured in weeks rather than months and work is performed in a highly

collaborative manner. Most agile methods also differ by treating their time period as a stricttimebox.

Contrasted with the waterfall model

Agile development has little in common with thewaterfall model. As of 2004, the waterfall model is still in

common use.[7]

The waterfall model is the most structured of the methods, stepping through requirements-

capture, analysis, design, coding, and testing in a strict, pre-planned sequence. Progress is generally measured

in terms of deliverable artifacts: requirement specifications, design documents, test plans, code reviews andthe like.

The main problem with the waterfall model is the inflexible division of a project into separate stages, so that

commitments are made early on, and it is difficult to react to changes in requirements. Iterations are

expensive. This means that the waterfall model is likely to be unsuitable if requirements are not well

understood or are likely to change in the course of the project.[8]

Agile methods, in contrast, produce completely developed and tested features (but a very small subset of the

whole) every few weeks. The emphasis is on obtaining the smallest workable piece of functionality to deliver

business value early, and continually improving it and adding further functionality throughout the life of the

project. If a project being delivered under the waterfall method is cancelled at any point up to the end, thereis nothing to show for it beyond a huge resources bill. With the agile method, being cancelled at any point will

still leave the customer with some worthwhile code, that has likely already been put into live operation.

In this respect, agile critics[who?]

may assert that these features are not placed in context of the overall project,

concluding that, if the sponsors of the project are concerned about completing certain goals with a defined

timeline or budget, agile may not be appropriate. Proponents of agile development counter that adaptations

ofScrum[9]

show how agile methods are augmented to produce and continuously improve a strategic plan.
http://en.wikipedia.org/wiki/Change_control_boardhttp://en.wikipedia.org/wiki/Change_control_boardhttp://en.wikipedia.org/wiki/Rapid_Application_Developmenthttp://en.wikipedia.org/wiki/Rapid_Application_Developmenthttp://en.wikipedia.org/wiki/Rapid_Application_Developmenthttp://en.wikipedia.org/wiki/Iterative_and_incremental_developmenthttp://en.wikipedia.org/wiki/Iterative_and_incremental_developmenthttp://en.wikipedia.org/wiki/Iterative_and_incremental_developmenthttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Waterfall_modelhttp://en.wikipedia.org/wiki/Waterfall_modelhttp://en.wikipedia.org/wiki/Waterfall_modelhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-Laplante2004-6http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Laplante2004-6http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Laplante2004-6http://en.wikipedia.org/wiki/Agile_software_development#cite_note-7http://en.wikipedia.org/wiki/Agile_software_development#cite_note-7http://en.wikipedia.org/wiki/Agile_software_development#cite_note-7http://en.wikipedia.org/wiki/Wikipedia:Avoid_weasel_wordshttp://en.wikipedia.org/wiki/Wikipedia:Avoid_weasel_wordshttp://en.wikipedia.org/wiki/Wikipedia:Avoid_weasel_wordshttp://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Wikipedia:Avoid_weasel_wordshttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-7http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Laplante2004-6http://en.wikipedia.org/wiki/Waterfall_modelhttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Iterative_and_incremental_developmenthttp://en.wikipedia.org/wiki/Rapid_Application_Developmenthttp://en.wikipedia.org/wiki/Change_control_board


5/12


Some agile teams use the waterfall model on a small scale, repeating the entire waterfall cycle in every

iteration.[10]

Other teams, most notablyExtreme Programmingteams, work on activities simultaneously.

Contrasted with "cowboy coding"

Cowboy codingis the absence of a defined method: team members do whatever they feel is right. Agile

development's frequent re-evaluation of plans, emphasis on face-to-face communication, and relatively

sparse use of documents sometimes causes people to confuse it with cowboy coding. Agile teams, however,

do follow defined (and often very disciplined and rigorous) processes.[clarification needed]

As with all development methods, the skill and experience of the users determine the degree of success

and/or abuse of such activity. The more rigid controls systematically embedded within a process offer stronger

levels of accountability of the users. The degradation of well-intended procedures can lead to activities often

categorized as cowboy coding.

Suitability of agile methods

There is little if any consensus on what types of software projects are best suited for the agile approach. Many

large organizations have difficulty bridging the gap between the traditional waterfall method and an agile one.

Large scale agile software development remains an active research area.[11][12]

Agile development has been widely documented (seeExperience Reports, below, as well as Beck[13]

pg. 157,

and Boehm and Turner[14]

pg. 55-57) as working well for small (20 developers), though scaling strategies[15]and evidence to thecontrary

[16]

have been described. Distributed development efforts (non-co-located teams). Strategies have been described in Bridging

the Distance[17]

and Using an Agile Software Process with Offshore Development[18]

Command-and-control company cultures Forcing an agile process on a development team

Several successful large scale agile projects have been documented.[where?]

BThas had several hundred

developers situated in the UK, Ireland and India working collaboratively on projects and using Agile methods.

While questions undoubtedly still arise about the suitability of some Agile methods to certain project types, it

would appear that scale or geography, by themselves, are not necessarily barriers to success.

Barry BoehmandRichard Turnersuggest thatrisk analysisbe used to choose between adaptive ("agile") and

predictive ("plan-driven") methods.[14]

The authors suggest that each side of the continuum has its own home

groundas follows:

Agile home ground:

Low criticality
http://en.wikipedia.org/wiki/Agile_software_development#cite_note-9http://en.wikipedia.org/wiki/Agile_software_development#cite_note-9http://en.wikipedia.org/wiki/Agile_software_development#cite_note-9http://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Cowboy_codinghttp://en.wikipedia.org/wiki/Cowboy_codinghttp://en.wikipedia.org/wiki/Wikipedia:Please_clarifyhttp://en.wikipedia.org/wiki/Wikipedia:Please_clarifyhttp://en.wikipedia.org/wiki/Wikipedia:Please_clarifyhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-oopsla2002-10http://en.wikipedia.org/wiki/Agile_software_development#cite_note-oopsla2002-10http://en.wikipedia.org/wiki/Agile_software_development#cite_note-oopsla2002-10http://en.wikipedia.org/wiki/Agile_software_development#Experience_Reportshttp://en.wikipedia.org/wiki/Agile_software_development#Experience_Reportshttp://en.wikipedia.org/wiki/Agile_software_development#Experience_Reportshttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-beck1999-12http://en.wikipedia.org/wiki/Agile_software_development#cite_note-beck1999-12http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Agile_software_development#cite_note-supersizeme-14http://en.wikipedia.org/wiki/Agile_software_development#cite_note-supersizeme-14http://en.wikipedia.org/wiki/Agile_software_development#cite_note-supersizeme-14http://en.wikipedia.org/wiki/Agile_software_development#cite_note-sstc2007-15http://en.wikipedia.org/wiki/Agile_software_development#cite_note-sstc2007-15http://en.wikipedia.org/wiki/Agile_software_development#cite_note-BridgingTheDistance-16http://en.wikipedia.org/wiki/Agile_software_development#cite_note-BridgingTheDistance-16http://en.wikipedia.org/wiki/Agile_software_development#cite_note-AgileOffshore-17http://en.wikipedia.org/wiki/Agile_software_development#cite_note-AgileOffshore-17http://en.wikipedia.org/wiki/Agile_software_development#cite_note-AgileOffshore-17http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Countering_systemic_biashttp://en.wikipedia.org/wiki/Wikipedia:WikiProject_Countering_systemic_biashttp://en.wikipedia.org/wiki/Wikipedia:WikiProject_Countering_systemic_biashttp://en.wikipedia.org/wiki/British_Telecomhttp://en.wikipedia.org/wiki/British_Telecomhttp://en.wikipedia.org/wiki/British_Telecomhttp://en.wikipedia.org/wiki/Barry_Boehmhttp://en.wikipedia.org/wiki/Barry_Boehmhttp://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Risk_analysishttp://en.wikipedia.org/wiki/Risk_analysishttp://en.wikipedia.org/wiki/Risk_analysishttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Risk_analysishttp://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Barry_Boehmhttp://en.wikipedia.org/wiki/British_Telecomhttp://en.wikipedia.org/wiki/Wikipedia:WikiProject_Countering_systemic_biashttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-AgileOffshore-17http://en.wikipedia.org/wiki/Agile_software_development#cite_note-BridgingTheDistance-16http://en.wikipedia.org/wiki/Agile_software_development#cite_note-sstc2007-15http://en.wikipedia.org/wiki/Agile_software_development#cite_note-supersizeme-14http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Agile_software_development#cite_note-beck1999-12http://en.wikipedia.org/wiki/Agile_software_development#Experience_Reportshttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-oopsla2002-10http://en.wikipedia.org/wiki/Agile_software_development#cite_note-oopsla2002-10http://en.wikipedia.org/wiki/Wikipedia:Please_clarifyhttp://en.wikipedia.org/wiki/Cowboy_codinghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-9


6/12


Senior developers Requirements change very often Small number of developers Culture that thrives on chaos

Plan-driven home ground:

High criticality Junior developers Requirements don't change too often Large number of developers Culture that demands order

Agile methods apply to only the development of software products because they exploit certain

characteristics of software, such as object technologies and the ability to automate testing. For developing

non-software products, such as machinery, electronic hardware, and food, a related set of techniques, known

asflexible product development, are available.

Agile methods and method tailoring

In the literature, different terms refer to the notion of method adaptation, including method tailoring,

method fragment adaptation and situational method engineering. Method tailoring is defined as:

A process or capability in which human agents through responsive changes in, and dynamic interplays

between contexts, intentions, and method fragments determine a system development approach for a

specific project situation.[19]

Potentially, almost all agile methods are suitable for method tailoring. Even theDSDMmethod is being used

for this purpose and has been successfully tailored in aCMMcontext.[20]

Situation-appropriateness can beconsidered as a distinguishing characteristic between agile methods and traditional software development

methods, with the latter being relatively much more rigid and prescriptive. The practical implication is that

agile methods allow project teams to adapt working practices according to the needs of individual projects.

Practices are concrete activities and products that are part of a method framework. At a more extreme level,

the philosophy behind the method, consisting of a number ofprinciples, could be adapted (Aydin, 2004).[19]

Extreme Programming(XP) makes the need for method adaptation explicit. One of the fundamental ideas of

XP is that not one process fits every project, but rather that practices should be tailored to the needs of

individual projects. Partial adoption of XP practices, as suggested byBeck, has been reported on several

occasions.[21]

A tailoring practice is proposed byMehdi Mirakhorliwhich provides sufficient roadmap and

guideline for adapting all the practices.RDP Practiceis designed for customizing XP. This practice first time

proposed as a long research paper in APSO workshop at ICSE 2008 conference and yet it is the only proposed

and applicable method for customizing XP. Although it is specifically a solution for XP, this practice has the

capability of extending to other methodologies. At first glance, this practice seems to be in the category of

static method adaptation but experiences with RDP Practice says that it can be treated like dynamic method

adaptation. The distinction between static method adaptation and dynamic method adaptation is subtle.[22]

The key assumption behind static method adaptation is that the project context is given at the start of a
http://en.wikipedia.org/wiki/Flexible_product_developmenthttp://en.wikipedia.org/wiki/Flexible_product_developmenthttp://en.wikipedia.org/wiki/Flexible_product_developmenthttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2004-18http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2004-18http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2004-18http://en.wikipedia.org/wiki/DSDMhttp://en.wikipedia.org/wiki/DSDMhttp://en.wikipedia.org/wiki/DSDMhttp://en.wikipedia.org/wiki/Capability_Maturity_Modelhttp://en.wikipedia.org/wiki/Capability_Maturity_Modelhttp://en.wikipedia.org/wiki/Capability_Maturity_Modelhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2003-19http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2003-19http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2003-19http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2004-18http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2004-18http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2004-18http://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2002-20http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2002-20http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2002-20http://portal.acm.org/citation.cfm?id=1370143.1370149&coll=ACM&dl=ACM&CFID=69442744&CFTOKEN=96226775,http://portal.acm.org/citation.cfm?id=1370143.1370149&coll=ACM&dl=ACM&CFID=69442744&CFTOKEN=96226775,http://portal.acm.org/citation.cfm?id=1370143.1370149&coll=ACM&dl=ACM&CFID=69442744&CFTOKEN=96226775,http://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2005-21http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2005-21http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2005-21http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2005-21http://en.wikipedia.org/wiki/Extreme_Programminghttp://portal.acm.org/citation.cfm?id=1370143.1370149&coll=ACM&dl=ACM&CFID=69442744&CFTOKEN=96226775,http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2002-20http://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2004-18http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2003-19http://en.wikipedia.org/wiki/Capability_Maturity_Modelhttp://en.wikipedia.org/wiki/DSDMhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2004-18http://en.wikipedia.org/wiki/Flexible_product_development


7/12


project and remains fixed during project execution. The result is a static definition of the project context.

Given such a definition, route maps can be used in order to determine which structured method fragments

should be used for that particular project, based on predefined sets of criteria. Dynamic method adaptation, in

contrast, assumes that projects are situated in an emergent context. An emergent context implies that a

project has to deal with emergent factors that affect relevant conditions but are not predictable. This also

means that a project context is not fixed, but changing during project execution. In such a case prescriptive

route maps are not appropriate. The practical implication of dynamic method adaptation is that project

managers often have to modify structured fragments or even innovate new fragments, during the execution of

a project (Aydin et al., 2005).[22]

Agile methods and project management

Agile methods differ to a large degree in the way they cover project management. Some methods are

supplemented with guidelines on project management, but there is generally no comprehensive support.[20]

PMPhas been suggested as a suitable, complementary project management system.

PRINCE2has been suggested as a suitable, complementary project management system.[23]

Agile methods

Some of the well-known agile software development methods:

Agile Modeling Agile Unified Process(AUP) Agile Data Method DSDM Essential Unified Process(EssUP) Extreme programming(XP) Feature Driven Development(FDD) Getting Real Open Unified Process(OpenUP) Scrum Lean software development

Agile practices

Test Driven Development(TDD) Behavior Driven Development(BDD) Continuous Integration Pair Programming Planning poker

Note: Although these are often considered methodologies in and of themselves, they are simply practices

used in different methodologies.
http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2005-21http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2005-21http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2005-21http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2003-19http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2003-19http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2003-19http://en.wikipedia.org/wiki/PMPhttp://en.wikipedia.org/wiki/PMPhttp://en.wikipedia.org/wiki/PRINCE2http://en.wikipedia.org/wiki/PRINCE2http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Prince2DSDM-22http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Prince2DSDM-22http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Prince2DSDM-22http://en.wikipedia.org/wiki/Agile_Modelinghttp://en.wikipedia.org/wiki/Agile_Modelinghttp://en.wikipedia.org/wiki/Agile_Unified_Processhttp://en.wikipedia.org/wiki/Agile_Unified_Processhttp://en.wikipedia.org/wiki/Agile_Data_Methodhttp://en.wikipedia.org/wiki/Agile_Data_Methodhttp://en.wikipedia.org/wiki/DSDMhttp://en.wikipedia.org/wiki/DSDMhttp://en.wikipedia.org/wiki/Essential_Unified_Processhttp://en.wikipedia.org/wiki/Essential_Unified_Processhttp://en.wikipedia.org/wiki/Extreme_programminghttp://en.wikipedia.org/wiki/Extreme_programminghttp://en.wikipedia.org/wiki/Feature_Driven_Developmenthttp://en.wikipedia.org/wiki/Feature_Driven_Developmenthttp://en.wikipedia.org/wiki/37signals#.22Getting_Real.22_philosophyhttp://en.wikipedia.org/wiki/37signals#.22Getting_Real.22_philosophyhttp://en.wikipedia.org/wiki/Open_Unified_Processhttp://en.wikipedia.org/wiki/Open_Unified_Processhttp://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Test_Driven_Developmenthttp://en.wikipedia.org/wiki/Test_Driven_Developmenthttp://en.wikipedia.org/wiki/Behavior_Driven_Developmenthttp://en.wikipedia.org/wiki/Behavior_Driven_Developmenthttp://en.wikipedia.org/wiki/Continuous_Integrationhttp://en.wikipedia.org/wiki/Continuous_Integrationhttp://en.wikipedia.org/wiki/Pair_Programminghttp://en.wikipedia.org/wiki/Pair_Programminghttp://en.wikipedia.org/wiki/Planning_pokerhttp://en.wikipedia.org/wiki/Planning_pokerhttp://en.wikipedia.org/wiki/Planning_pokerhttp://en.wikipedia.org/wiki/Pair_Programminghttp://en.wikipedia.org/wiki/Continuous_Integrationhttp://en.wikipedia.org/wiki/Behavior_Driven_Developmenthttp://en.wikipedia.org/wiki/Test_Driven_Developmenthttp://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Open_Unified_Processhttp://en.wikipedia.org/wiki/37signals#.22Getting_Real.22_philosophyhttp://en.wikipedia.org/wiki/Feature_Driven_Developmenthttp://en.wikipedia.org/wiki/Extreme_programminghttp://en.wikipedia.org/wiki/Essential_Unified_Processhttp://en.wikipedia.org/wiki/DSDMhttp://en.wikipedia.org/wiki/Agile_Data_Methodhttp://en.wikipedia.org/wiki/Agile_Unified_Processhttp://en.wikipedia.org/wiki/Agile_Modelinghttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-Prince2DSDM-22http://en.wikipedia.org/wiki/PRINCE2http://en.wikipedia.org/wiki/PMPhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-Abrahamsson2003-19http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Aydin2005-21


8/12


Agile beyond software development

Agile software development depends on some special characteristics possessed only by software, such as

object technologies and the ability to automate testing. However, related techniques have been created for

developing non-software products, such as semiconductors, motor vehicles, or chemicals. For more on them,

seeFlexible product development.

Measuring agility

While agility can be seen as a means to an end, a number of approaches have been proposed to quantify

agility. Agility Index Measurements (AIM)[1]score projects against a number of agility factors to achieve a

total. The similarly-named Agility Measurement Index[2], scores developments against five dimensions of a

software project (duration, risk, novelty, effort, and interaction). Other techniques are based on measurable

goals[3]. Another study using fuzzy mathematics[24]

has suggested that project velocity can be used as a

metric of agility. There are agile self assessments to determine whether a team is using agile practices.[25][26]

While such approaches have been proposed to measure agility, the practical application of such metrics has

yet to be seen.

Criticism

Extreme Programming's initial buzz and controversial tenets, such aspair programmingandcontinuous

design, have attracted particular criticism, such as McBreen[27]

and Boehm and Turner.[14]

Many of the

criticisms, however, are believed by Agile practitioners to be misunderstandings of agile development.[28]

In particular,Extreme Programmingis reviewed and critiqued by Matt Stephens's and Doug Rosenberg's

Extreme Programming Refactored.[29]

Criticisms include:

Often used as a means to bleed money from customers through lack of defining a deliverable Lack of structure and necessary documentation Only works with senior-level developers Incorporates insufficient software design Requires meetings at frequent intervals at enormous expense to customers Requires too much cultural change to adopt Can lead to more difficult contractual negotiations Can be very inefficientif the requirements for one area of code change through various iterations,

the same programming may need to be done several times over. Whereas if a plan were there to be

followed, a single area of code is expected to be written once.

Impossible to develop realistic estimates of work effort needed to provide a quote, because at thebeginning of the project no one knows the entire scope/requirements

Can increase the risk ofscope creepdue to the lack of detailed requirements documentation Agile is feature driven, non-functional quality attributes are hard to be placed as user stories
http://en.wikipedia.org/wiki/Flexible_product_developmenthttp://en.wikipedia.org/wiki/Flexible_product_developmenthttp://en.wikipedia.org/wiki/Flexible_product_developmenthttp://jroller.com/page/bokmann?entry=improving_your_processes_aim_highhttp://jroller.com/page/bokmann?entry=improving_your_processes_aim_highhttp://jroller.com/page/bokmann?entry=improving_your_processes_aim_highhttp://doi.acm.org/10.1145/1185448.1185509http://doi.acm.org/10.1145/1185448.1185509http://doi.acm.org/10.1145/1185448.1185509http://www.smr.co.uk/presentations/measure.pdfhttp://www.smr.co.uk/presentations/measure.pdfhttp://www.smr.co.uk/presentations/measure.pdfhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-Kurian_2006-23http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Kurian_2006-23http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Kurian_2006-23http://en.wikipedia.org/wiki/Agile_software_development#cite_note-24http://en.wikipedia.org/wiki/Agile_software_development#cite_note-24http://en.wikipedia.org/wiki/Agile_software_development#cite_note-24http://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/Continuous_designhttp://en.wikipedia.org/wiki/Continuous_designhttp://en.wikipedia.org/wiki/Continuous_designhttp://en.wikipedia.org/wiki/Continuous_designhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-mcbreen-26http://en.wikipedia.org/wiki/Agile_software_development#cite_note-mcbreen-26http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Agile_software_development#cite_note-sdmagazine1811-27http://en.wikipedia.org/wiki/Agile_software_development#cite_note-sdmagazine1811-27http://en.wikipedia.org/wiki/Agile_software_development#cite_note-sdmagazine1811-27http://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-ExtremeProgrammingRefactored-28http://en.wikipedia.org/wiki/Agile_software_development#cite_note-ExtremeProgrammingRefactored-28http://en.wikipedia.org/wiki/Agile_software_development#cite_note-ExtremeProgrammingRefactored-28http://en.wikipedia.org/wiki/Scope_creephttp://en.wikipedia.org/wiki/Scope_creephttp://en.wikipedia.org/wiki/Scope_creephttp://en.wikipedia.org/wiki/User_storyhttp://en.wikipedia.org/wiki/User_storyhttp://en.wikipedia.org/wiki/User_storyhttp://en.wikipedia.org/wiki/Scope_creephttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-ExtremeProgrammingRefactored-28http://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-sdmagazine1811-27http://en.wikipedia.org/wiki/Agile_software_development#cite_note-boehm2004-13http://en.wikipedia.org/wiki/Agile_software_development#cite_note-mcbreen-26http://en.wikipedia.org/wiki/Continuous_designhttp://en.wikipedia.org/wiki/Continuous_designhttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-24http://en.wikipedia.org/wiki/Agile_software_development#cite_note-24http://en.wikipedia.org/wiki/Agile_software_development#cite_note-Kurian_2006-23http://www.smr.co.uk/presentations/measure.pdfhttp://doi.acm.org/10.1145/1185448.1185509http://jroller.com/page/bokmann?entry=improving_your_processes_aim_highhttp://en.wikipedia.org/wiki/Flexible_product_development


9/12


The criticisms regarding insufficient software design and lack of documentation are addressed by the Agile

Modeling method, which can easily be tailored into agile processes.

Agile software development has been criticized because it may not bring about all of the claimed benefits

when programmers of average ability use this method.[30]

Post-Agilism

Insoftware engineering, post-Agilism is an informal movement of practitioners who prefer to avoid being

constrained by what they consider to be "Agile Dogma" (or "Agile with a capital 'A'")

Some have argued that the meaning ofAgileis ambiguous and has been applied inappropriately to a very wide

range of approaches likeSix SigmaandCMMi(though proponents of some agile methods, such as Scrum,

show that the methods can exist comfortably within a CMMi environment.)[31]

Some have argued also that

"Agile", "evolutionary", and "lean" (as inLean software development) do not mean the same thing in practice,

even though they are all lumped under the banner of "Agile" and are often used interchangeably by

practitioners.

Proponents also argue that process-oriented methods, especially methods that rely on repeatable results and

that incrementally reduce waste and process variation likeSix Sigma, have a tendency to limit an

organisation's adaptive capacity (their "slack"), making them less able to respond todiscontinuous change-

i.e., less agile. It is proposed that "agile", "lean" and "evolutionary" are strategies that need to be properly

understood and appropriately applied to any specific context. That is, there is a time to be "agile", a time to be

"lean" and a time to be "evolutionary." Some agilists agree with this position, promoting the concept of agile

methods as one set of tools that should be available to managers for use in appropriate situations, not as one-

size-fits-all methods that should be forced onto all organizations.[32]

Much of post-Agile thinking centers aroundNonlinear Management, a superset of management techniques

that include manyAgilepractices.

Some commentators propose a model of post-Agilism that is effectively constructiveanarchy, in that teams

should be self-organizing to the point where even the core values of theAgilemovement are considered too

prescriptive, and that teams should simply "do whatever works for them." This position is controversial in the

agile community and breaks from the trend of later agile methods being more structured (fitting better within

CMMi environments) than earlier agile methods.

Experience reports

Agile development has been the subject of several conferences. Some of these conferences have hadacademic backing and included peer-reviewed papers, including a peer-reviewed experience report track. The

experience reports share industry experiences with agile software development.

As of 2006, experience reports have been or will be presented at the following conferences:

XP (2000[33], 2001, 2002, 2003, 2004, 2005, 2006[34]) XP Universe (2001[35])
http://en.wikipedia.org/wiki/Agile_software_development#cite_note-TheGreatPyramidOfAgile-29http://en.wikipedia.org/wiki/Agile_software_development#cite_note-TheGreatPyramidOfAgile-29http://en.wikipedia.org/wiki/Agile_software_development#cite_note-TheGreatPyramidOfAgile-29http://en.wikipedia.org/wiki/Software_engineeringhttp://en.wikipedia.org/wiki/Software_engineeringhttp://en.wikipedia.org/wiki/Software_engineeringhttp://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/CMMihttp://en.wikipedia.org/wiki/CMMihttp://en.wikipedia.org/wiki/CMMihttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-30http://en.wikipedia.org/wiki/Agile_software_development#cite_note-30http://en.wikipedia.org/wiki/Agile_software_development#cite_note-30http://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/w/index.php?title=Discontinuous_change&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Discontinuous_change&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Discontinuous_change&action=edit&redlink=1http://en.wikipedia.org/wiki/Agile_software_development#cite_note-31http://en.wikipedia.org/wiki/Agile_software_development#cite_note-31http://en.wikipedia.org/wiki/Agile_software_development#cite_note-31http://en.wikipedia.org/wiki/Nonlinear_Managementhttp://en.wikipedia.org/wiki/Nonlinear_Managementhttp://en.wikipedia.org/wiki/Nonlinear_Managementhttp://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Anarchyhttp://en.wikipedia.org/wiki/Anarchyhttp://en.wikipedia.org/wiki/Anarchyhttp://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-32http://en.wikipedia.org/wiki/Agile_software_development#cite_note-32http://en.wikipedia.org/wiki/Agile_software_development#cite_note-32http://en.wikipedia.org/wiki/Agile_software_development#cite_note-33http://en.wikipedia.org/wiki/Agile_software_development#cite_note-33http://en.wikipedia.org/wiki/Agile_software_development#cite_note-34http://en.wikipedia.org/wiki/Agile_software_development#cite_note-34http://en.wikipedia.org/wiki/Agile_software_development#cite_note-34http://en.wikipedia.org/wiki/Agile_software_development#cite_note-33http://en.wikipedia.org/wiki/Agile_software_development#cite_note-32http://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Anarchyhttp://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Nonlinear_Managementhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-31http://en.wikipedia.org/w/index.php?title=Discontinuous_change&action=edit&redlink=1http://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-30http://en.wikipedia.org/wiki/CMMihttp://en.wikipedia.org/wiki/Six_Sigmahttp://en.wikipedia.org/wiki/Agilehttp://en.wikipedia.org/wiki/Software_engineeringhttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-TheGreatPyramidOfAgile-29


10/12


XP/Agile Universe (2002,[36]2003,[37]2004[38]) Agile Development Conference[39]starting from 2003 to present (peer-reviewed; proceedings

published by IEEE)

See also

Agile web development Code refactoring Collaborative software development model Continuous integration Extreme Programming(XP) Scrum (development) Lean software development List of software development philosophies Multi-stage continuous integration Systems Development Life Cycle Software Engineering CAP (Client Accelerated Programming) Software Craftsmanship

References

1. ^Gerald M. Weinberg:We were doing incremental development as early as 1957, in Los Angeles, underthe direction of Bernie Dimsdale [at IBMs ServiceBureau Corporation]. He was a c olleague of John von

Neumann, so perhaps he learned it there, or assumed it as totally natural. I do remember Herb Jacobs

(primarily, though we all participated) developing a large simulation for Motorola, where the technique

used was, as far as I can tell, [. . .] All of us, as far as I can remember, thought waterfalling of a huge

project was rather stupid, or at least ignorant of the realities. I think what the waterfall description did

for us was make us realize that we were doing something else, something unnamed except for

software development. quoted in Larman, Craig; Victor R. Basili (June 2003). "Iterative and

Incremental Development: A Brief History" (pdf). Computer36 (No. 6): pp 4756.

doi:10.1109/MC.2003.1204375.http://www2.umassd.edu/SWPI/xp/articles/r6047.pdf. Retrieved on

2007-02-22. (Permission note)

2. Âgile Alliance3. Êdmonds, E. A. (1974), "A process for the development of software for non-technical users as an

adaptive system", General SystemsXIX: 215218

4. ^Kent Beck,Mike Beedle,Arie van Bennekum,Alistair Cockburn,Ward Cunningham,Martin Fowler,James Grenning,Jim Highsmith,Andrew Hunt,Ron Jeffries,Jon Kern,Brian Marick,Robert C. Martin,

Steve Mellor,Ken Schwaber,Jeff SutherlandandDave Thomas5. Âgile Manifesto principles6. ^Boehm, B.;R. Turner(2004). Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA:

Addison-Wesley.ISBN 0-321-18612-5. Appendix A, pages 165-194

7. ^Laplante, P.A.; C.J. Neill (February 2004). ""The Demise of the Waterfall Model Is Imminent" andOther Urban Myths".ACMQueue1 (10): 10.doi:10.1145/971564.971573.

http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=110. Retrieved on

2006-05-13.
http://en.wikipedia.org/wiki/Agile_software_development#cite_note-35http://en.wikipedia.org/wiki/Agile_software_development#cite_note-35http://en.wikipedia.org/wiki/Agile_software_development#cite_note-35http://en.wikipedia.org/wiki/Agile_software_development#cite_note-36http://en.wikipedia.org/wiki/Agile_software_development#cite_note-36http://en.wikipedia.org/wiki/Agile_software_development#cite_note-36http://en.wikipedia.org/wiki/Agile_software_development#cite_note-37http://en.wikipedia.org/wiki/Agile_software_development#cite_note-37http://en.wikipedia.org/wiki/Agile_software_development#cite_note-38http://en.wikipedia.org/wiki/Agile_software_development#cite_note-38http://en.wikipedia.org/wiki/Agile_web_developmenthttp://en.wikipedia.org/wiki/Agile_web_developmenthttp://en.wikipedia.org/wiki/Code_refactoringhttp://en.wikipedia.org/wiki/Code_refactoringhttp://en.wikipedia.org/wiki/Collaborative_software_development_modelhttp://en.wikipedia.org/wiki/Collaborative_software_development_modelhttp://en.wikipedia.org/wiki/Continuous_integrationhttp://en.wikipedia.org/wiki/Continuous_integrationhttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/List_of_software_development_philosophieshttp://en.wikipedia.org/wiki/List_of_software_development_philosophieshttp://en.wikipedia.org/wiki/Multi-stage_continuous_integrationhttp://en.wikipedia.org/wiki/Multi-stage_continuous_integrationhttp://en.wikipedia.org/wiki/Systems_Development_Life_Cyclehttp://en.wikipedia.org/wiki/Systems_Development_Life_Cyclehttp://en.wikipedia.org/wiki/Software_Engineeringhttp://en.wikipedia.org/wiki/Software_Engineeringhttp://en.wikipedia.org/w/index.php?title=CAP_%28Client_Accelerated_Programming%29&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=CAP_%28Client_Accelerated_Programming%29&action=edit&redlink=1http://en.wikipedia.org/wiki/Software_Craftsmanshiphttp://en.wikipedia.org/wiki/Software_Craftsmanshiphttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-0http://en.wikipedia.org/wiki/Gerald_M._Weinberghttp://en.wikipedia.org/wiki/Gerald_M._Weinberghttp://en.wikipedia.org/wiki/Gerald_M._Weinberghttp://www2.umassd.edu/SWPI/xp/articles/r6047.pdfhttp://www2.umassd.edu/SWPI/xp/articles/r6047.pdfhttp://www2.umassd.edu/SWPI/xp/articles/r6047.pdfhttp://www2.umassd.edu/SWPI/xp/articles/r6047.pdfhttp://en.wikipedia.org/wiki/Digital_object_identifierhttp://dx.doi.org/10.1109%2FMC.2003.1204375http://dx.doi.org/10.1109%2FMC.2003.1204375http://dx.doi.org/10.1109%2FMC.2003.1204375http://www2.umassd.edu/SWPI/xp/articles/r6047.pdfhttp://www2.umassd.edu/SWPI/xp/articles/r6047.pdfhttp://www2.umassd.edu/SWPI/xp/articles/r6047.pdfhttp://www.agilealliance.org/show/1404http://www.agilealliance.org/show/1404http://www.agilealliance.org/show/1404http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-1http://www.agilealliance.com/http://www.agilealliance.com/http://www.agilealliance.com/http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-edmonds1974_2-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-edmonds1974_2-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-3http://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/w/index.php?title=Mike_Beedle&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Mike_Beedle&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Mike_Beedle&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Arie_van_Bennekum&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Arie_van_Bennekum&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Arie_van_Bennekum&action=edit&redlink=1http://en.wikipedia.org/wiki/Alistair_Cockburnhttp://en.wikipedia.org/wiki/Alistair_Cockburnhttp://en.wikipedia.org/wiki/Alistair_Cockburnhttp://en.wikipedia.org/wiki/Ward_Cunninghamhttp://en.wikipedia.org/wiki/Ward_Cunninghamhttp://en.wikipedia.org/wiki/Ward_Cunninghamhttp://en.wikipedia.org/wiki/Martin_Fowlerhttp://en.wikipedia.org/wiki/Martin_Fowlerhttp://en.wikipedia.org/wiki/Martin_Fowlerhttp://en.wikipedia.org/w/index.php?title=James_Grenning&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=James_Grenning&action=edit&redlink=1http://en.wikipedia.org/wiki/Jim_Highsmithhttp://en.wikipedia.org/wiki/Jim_Highsmithhttp://en.wikipedia.org/wiki/Jim_Highsmithhttp://en.wikipedia.org/wiki/Andy_Hunt_%28author%29http://en.wikipedia.org/wiki/Andy_Hunt_%28author%29http://en.wikipedia.org/wiki/Andy_Hunt_%28author%29http://en.wikipedia.org/wiki/Ron_Jeffrieshttp://en.wikipedia.org/wiki/Ron_Jeffrieshttp://en.wikipedia.org/wiki/Ron_Jeffrieshttp://en.wikipedia.org/w/index.php?title=Jon_Kern&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Jon_Kern&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Jon_Kern&action=edit&redlink=1http://en.wikipedia.org/wiki/Brian_Marickhttp://en.wikipedia.org/wiki/Brian_Marickhttp://en.wikipedia.org/wiki/Brian_Marickhttp://en.wikipedia.org/wiki/Robert_C._Martinhttp://en.wikipedia.org/wiki/Robert_C._Martinhttp://en.wikipedia.org/wiki/Robert_C._Martinhttp://en.wikipedia.org/wiki/Steve_Mellorhttp://en.wikipedia.org/wiki/Steve_Mellorhttp://en.wikipedia.org/wiki/Ken_Schwaberhttp://en.wikipedia.org/wiki/Ken_Schwaberhttp://en.wikipedia.org/wiki/Ken_Schwaberhttp://en.wikipedia.org/wiki/Jeff_Sutherlandhttp://en.wikipedia.org/wiki/Jeff_Sutherlandhttp://en.wikipedia.org/wiki/Jeff_Sutherlandhttp://en.wikipedia.org/wiki/Dave_Thomas_%28programmer%29http://en.wikipedia.org/wiki/Dave_Thomas_%28programmer%29http://en.wikipedia.org/wiki/Dave_Thomas_%28programmer%29http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-manifestoprinciples_4-0http://www.agilemanifesto.org/principles.htmlhttp://www.agilemanifesto.org/principles.htmlhttp://www.agilemanifesto.org/principles.htmlhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-boehm2004App_5-0http://en.wikipedia.org/wiki/Barry_Boehmhttp://en.wikipedia.org/wiki/Barry_Boehmhttp://en.wikipedia.org/wiki/Barry_Boehmhttp://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Special:BookSources/0321186125http://en.wikipedia.org/wiki/Special:BookSources/0321186125http://en.wikipedia.org/wiki/Special:BookSources/0321186125http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Laplante2004_6-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Laplante2004_6-0http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=110http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=110http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=110http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=110http://en.wikipedia.org/wiki/Association_for_Computing_Machineryhttp://en.wikipedia.org/wiki/Association_for_Computing_Machineryhttp://en.wikipedia.org/wiki/Association_for_Computing_Machineryhttp://en.wikipedia.org/wiki/Digital_object_identifierhttp://en.wikipedia.org/wiki/Digital_object_identifierhttp://dx.doi.org/10.1145%2F971564.971573http://dx.doi.org/10.1145%2F971564.971573http://dx.doi.org/10.1145%2F971564.971573http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=110http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=110http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=110http://dx.doi.org/10.1145%2F971564.971573http://en.wikipedia.org/wiki/Digital_object_identifierhttp://en.wikipedia.org/wiki/Association_for_Computing_Machineryhttp://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=110http://www.acmqueue.com/modules.php?name=Content&pa=showpage&pid=110http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Laplante2004_6-0http://en.wikipedia.org/wiki/Special:BookSources/0321186125http://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Barry_Boehmhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-boehm2004App_5-0http://www.agilemanifesto.org/principles.htmlhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-manifestoprinciples_4-0http://en.wikipedia.org/wiki/Dave_Thomas_%28programmer%29http://en.wikipedia.org/wiki/Jeff_Sutherlandhttp://en.wikipedia.org/wiki/Ken_Schwaberhttp://en.wikipedia.org/wiki/Steve_Mellorhttp://en.wikipedia.org/wiki/Robert_C._Martinhttp://en.wikipedia.org/wiki/Brian_Marickhttp://en.wikipedia.org/w/index.php?title=Jon_Kern&action=edit&redlink=1http://en.wikipedia.org/wiki/Ron_Jeffrieshttp://en.wikipedia.org/wiki/Andy_Hunt_%28author%29http://en.wikipedia.org/wiki/Jim_Highsmithhttp://en.wikipedia.org/w/index.php?title=James_Grenning&action=edit&redlink=1http://en.wikipedia.org/wiki/Martin_Fowlerhttp://en.wikipedia.org/wiki/Ward_Cunninghamhttp://en.wikipedia.org/wiki/Alistair_Cockburnhttp://en.wikipedia.org/w/index.php?title=Arie_van_Bennekum&action=edit&redlink=1http://en.wikipedia.org/w/index.php?title=Mike_Beedle&action=edit&redlink=1http://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-3http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-edmonds1974_2-0http://www.agilealliance.com/http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-1http://www.agilealliance.org/show/1404http://www2.umassd.edu/SWPI/xp/articles/r6047.pdfhttp://dx.doi.org/10.1109%2FMC.2003.1204375http://en.wikipedia.org/wiki/Digital_object_identifierhttp://www2.umassd.edu/SWPI/xp/articles/r6047.pdfhttp://www2.umassd.edu/SWPI/xp/articles/r6047.pdfhttp://en.wikipedia.org/wiki/Gerald_M._Weinberghttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-0http://en.wikipedia.org/wiki/Software_Craftsmanshiphttp://en.wikipedia.org/w/index.php?title=CAP_%28Client_Accelerated_Programming%29&action=edit&redlink=1http://en.wikipedia.org/wiki/Software_Engineeringhttp://en.wikipedia.org/wiki/Systems_Development_Life_Cyclehttp://en.wikipedia.org/wiki/Multi-stage_continuous_integrationhttp://en.wikipedia.org/wiki/List_of_software_development_philosophieshttp://en.wikipedia.org/wiki/Lean_software_developmenthttp://en.wikipedia.org/wiki/Scrum_%28development%29http://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Continuous_integrationhttp://en.wikipedia.org/wiki/Collaborative_software_development_modelhttp://en.wikipedia.org/wiki/Code_refactoringhttp://en.wikipedia.org/wiki/Agile_web_developmenthttp://en.wikipedia.org/wiki/Agile_software_development#cite_note-38http://en.wikipedia.org/wiki/Agile_software_development#cite_note-37http://en.wikipedia.org/wiki/Agile_software_development#cite_note-36http://en.wikipedia.org/wiki/Agile_software_development#cite_note-35


11/12


8. ^Sommerville, Ian(2007) [1982]. "4.1.1. The waterfall model". Software engineering (8th edition ed.).Harlow:Addison Wesley. pp. 66f.ISBN 0-321-31379-8.

9. ^Ambler, S. (April 2008). ""Scaling Scrum - Meeting Real World Development Needs". Dr. Dobbs.http://www.drdobbsonline.net/architect/207100381. Retrieved on 2008-04-23.

10. AsreportedbyHeavyLogic11. Agile Processes Workshop II Managing Multiple Concurrent Agile Projects. Washington: OOPSLA 200212. "Supersize Me" in Dr. Dobb's Journal, February 15, 2006.13. Beck, K.(1999). Extreme Programming Explained: Embrace Change. Boston, MA: Addison-Wesley.

ISBN 0-321-27865-8.

14. abcBoehm, B.;R. Turner(2004). Balancing Agility and Discipline: A Guide for the Perplexed. Boston,MA: Addison-Wesley.ISBN 0-321-18612-5.

15. Supersize Me16. Schaaf, R.J. (2007). "Agility XL",Systems and Software Technology Conference 2007, Tampa, FL17. Bridging the Distance18. Using an Agile Software Process with Offshore Development19. abAydin, M.N., Harmsen, F., Slooten, K. v., & Stagwee, R. A. (2004). An Agile Information Systems

Development Method in use. Turk J Elec Engin, 12(2), 127-138

20. abAbrahamsson, P., Warsta, J., Siponen, M.T., & Ronkainen, J. (2003). New Directions on AgileMethods: A Comparative Analysis. Proceedings of ICSE'03, 244-254

21. Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2002). Agile Software Development Methods:Review and Analysis. VTT Publications 478

22. abAydin, M.N., Harmsen, F., Slooten van K., & Stegwee, R.A. (2005). On the Adaptation of An AgileInformation Systems Development Method.Journal of Database Management Special issue on Agile

Analysis, Design, and Implementation, 16(4), 20-24

23. Agile Alliance athttp://agilealliance.org/system/article/file/904/file.pdf:PRINCE2 (Projects in Controlled Environments) . . . is a project management method that was

specifically designed to be generic and independent of any particular project type or development

method. As with DSDM, its use is dramatically on the increase in both the public and private sectors. Asa development method and a project management method, the two should be complementary. Some

have perceived the dynamic emphasis of DSDM and the control emphasis of PRINCE2 to be in conflict.

However, this is not the case. When DSDM was being developed, those involved had PRINCE firmly in

mind. This is reflected in a number of the DSDM principles and techniques for example, product-based

planning, the involved partnership of users and developers, and the strong emphasis on the underlying

business case.

24. Kurian, Tisni (2006). "Agility Metrics: A Quantitative Fuzzy Based Approach for Measuring Agility of aSoftware Process" ISAM-Proceedings of International Conference on Agile Manufacturing'06(ICAM-

2006), Norfolk, U.S.

25. Nokia test, Scrum specific26. Karlskrona test, generic agile adoption27. McBreen, P. (2003). Questioning Extreme Programming. Boston, MA: Addison-Wesley.ISBN 0-201-

84457-5.

28. sdmagazine29. Extreme Programming Refactored, Matt Stephens and Doug Rosenberg, Publisher: Apress L.P.30. The Great Pyramid of Agile
http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-7http://en.wikipedia.org/wiki/Ian_Sommerville_%28academic%29http://en.wikipedia.org/wiki/Ian_Sommerville_%28academic%29http://en.wikipedia.org/wiki/Ian_Sommerville_%28academic%29http://en.wikipedia.org/wiki/Addison_Wesleyhttp://en.wikipedia.org/wiki/Addison_Wesleyhttp://en.wikipedia.org/wiki/Addison_Wesleyhttp://en.wikipedia.org/wiki/Special:BookSources/0321313798http://en.wikipedia.org/wiki/Special:BookSources/0321313798http://en.wikipedia.org/wiki/Special:BookSources/0321313798http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Ambler2008_8-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Ambler2008_8-0http://www.drdobbsonline.net/architect/207100381http://www.drdobbsonline.net/architect/207100381http://www.drdobbsonline.net/architect/207100381http://www.drdobbsonline.net/architect/207100381http://www.drdobbsonline.net/architect/207100381http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-9http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-9http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-9http://heavylogic.com/agile.phphttp://heavylogic.com/agile.phphttp://heavylogic.com/agile.phphttp://heavylogic.com/http://heavylogic.com/http://heavylogic.com/http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-oopsla2002_10-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-oopsla2002_10-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-oopsla2002_10-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-ambler2006_11-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-ambler2006_11-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-ambler2006_11-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-beck1999_12-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-beck1999_12-0http://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/wiki/Special:BookSources/0321278658http://en.wikipedia.org/wiki/Special:BookSources/0321278658http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-boehm2004_13-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-boehm2004_13-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-boehm2004_13-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-boehm2004_13-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-boehm2004_13-2http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-boehm2004_13-2http://en.wikipedia.org/wiki/Barry_Boehmhttp://en.wikipedia.org/wiki/Barry_Boehmhttp://en.wikipedia.org/wiki/Barry_Boehmhttp://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Special:BookSources/0321186125http://en.wikipedia.org/wiki/Special:BookSources/0321186125http://en.wikipedia.org/wiki/Special:BookSources/0321186125http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-supersizeme_14-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-supersizeme_14-0http://www.sdmagazine.com/documents/s=10020/sdm0603g/0603g.htmlhttp://www.sdmagazine.com/documents/s=10020/sdm0603g/0603g.htmlhttp://www.sdmagazine.com/documents/s=10020/sdm0603g/0603g.htmlhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-sstc2007_15-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-sstc2007_15-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-sstc2007_15-0http://www.sstc-online.org/Proceedings/2007/pdfs/RJS1722.pdfhttp://www.sstc-online.org/Proceedings/2007/pdfs/RJS1722.pdfhttp://www.sstc-online.org/Proceedings/2007/pdfs/RJS1722.pdfhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-BridgingTheDistance_16-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-BridgingTheDistance_16-0http://www.sdmagazine.com/documents/s=7556/sdm0209i/sdm0209i.htmhttp://www.sdmagazine.com/documents/s=7556/sdm0209i/sdm0209i.htmhttp://www.sdmagazine.com/documents/s=7556/sdm0209i/sdm0209i.htmhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-AgileOffshore_17-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-AgileOffshore_17-0http://www.martinfowler.com/articles/agileOffshore.htmlhttp://www.martinfowler.com/articles/agileOffshore.htmlhttp://www.martinfowler.com/articles/agileOffshore.htmlhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2004_18-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2004_18-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2004_18-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2004_18-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2004_18-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Abrahamsson2003_19-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Abrahamsson2003_19-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Abrahamsson2003_19-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Abrahamsson2003_19-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Abrahamsson2003_19-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Abrahamsson2002_20-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Abrahamsson2002_20-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Abrahamsson2002_20-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2005_21-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2005_21-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2005_21-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2005_21-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2005_21-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Prince2DSDM_22-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Prince2DSDM_22-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Prince2DSDM_22-0http://agilealliance.org/system/article/file/904/file.pdfhttp://agilealliance.org/system/article/file/904/file.pdfhttp://agilealliance.org/system/article/file/904/file.pdfhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Kurian_2006_23-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Kurian_2006_23-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Kurian_2006_23-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-24http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-24http://agileconsortium.blogspot.com/2007/12/nokia-test.htmlhttp://agileconsortium.blogspot.com/2007/12/nokia-test.htmlhttp://agileconsortium.blogspot.com/2007/12/nokia-test.htmlhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-25http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-25http://www.piratson.se/archive/Agile_Karlskrona_Test.pdfhttp://www.piratson.se/archive/Agile_Karlskrona_Test.pdfhttp://www.piratson.se/archive/Agile_Karlskrona_Test.pdfhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-mcbreen_26-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-mcbreen_26-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-mcbreen_26-0http://en.wikipedia.org/wiki/Special:BookSources/0201844575http://en.wikipedia.org/wiki/Special:BookSources/0201844575http://en.wikipedia.org/wiki/Special:BookSources/0201844575http://en.wikipedia.org/wiki/Special:BookSources/0201844575http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-sdmagazine1811_27-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-sdmagazine1811_27-0http://www.sdmagazine.com/documents/s=1811/sdm0112h/0112h.htmhttp://www.sdmagazine.com/documents/s=1811/sdm0112h/0112h.htmhttp://www.sdmagazine.com/documents/s=1811/sdm0112h/0112h.htmhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-ExtremeProgrammingRefactored_28-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-ExtremeProgrammingRefactored_28-0http://www.softwarereality.com/ExtremeProgrammingRefactored.jsphttp://www.softwarereality.com/ExtremeProgrammingRefactored.jsphttp://www.softwarereality.com/ExtremeProgrammingRefactored.jsphttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-TheGreatPyramidOfAgile_29-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-TheGreatPyramidOfAgile_29-0http://worsethanfailure.com/Articles/The-Great-Pyramid-of-Agile.aspxhttp://worsethanfailure.com/Articles/The-Great-Pyramid-of-Agile.aspxhttp://worsethanfailure.com/Articles/The-Great-Pyramid-of-Agile.aspxhttp://worsethanfailure.com/Articles/The-Great-Pyramid-of-Agile.aspxhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-TheGreatPyramidOfAgile_29-0http://www.softwarereality.com/ExtremeProgrammingRefactored.jsphttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-ExtremeProgrammingRefactored_28-0http://www.sdmagazine.com/documents/s=1811/sdm0112h/0112h.htmhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-sdmagazine1811_27-0http://en.wikipedia.org/wiki/Special:BookSources/0201844575http://en.wikipedia.org/wiki/Special:BookSources/0201844575http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-mcbreen_26-0http://www.piratson.se/archive/Agile_Karlskrona_Test.pdfhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-25http://agileconsortium.blogspot.com/2007/12/nokia-test.htmlhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-24http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Kurian_2006_23-0http://agilealliance.org/system/article/file/904/file.pdfhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Prince2DSDM_22-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2005_21-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2005_21-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Abrahamsson2002_20-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Abrahamsson2003_19-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Abrahamsson2003_19-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2004_18-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Aydin2004_18-0http://www.martinfowler.com/articles/agileOffshore.htmlhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-AgileOffshore_17-0http://www.sdmagazine.com/documents/s=7556/sdm0209i/sdm0209i.htmhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-BridgingTheDistance_16-0http://www.sstc-online.org/Proceedings/2007/pdfs/RJS1722.pdfhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-sstc2007_15-0http://www.sdmagazine.com/documents/s=10020/sdm0603g/0603g.htmlhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-supersizeme_14-0http://en.wikipedia.org/wiki/Special:BookSources/0321186125http://en.wikipedia.org/wiki/Richard_Turner_%28software%29http://en.wikipedia.org/wiki/Barry_Boehmhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-boehm2004_13-2http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-boehm2004_13-1http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-boehm2004_13-0http://en.wikipedia.org/wiki/Special:BookSources/0321278658http://en.wikipedia.org/wiki/Kent_Beckhttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-beck1999_12-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-ambler2006_11-0http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-oopsla2002_10-0http://heavylogic.com/http://heavylogic.com/agile.phphttp://en.wikipedia.org/wiki/Agile_software_development#cite_ref-9http://www.drdobbsonline.net/architect/207100381http://www.drdobbsonline.net/architect/207100381http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-Ambler2008_8-0http://en.wikipedia.org/wiki/Special:BookSources/0321313798http://en.wikipedia.org/wiki/Addison_Wesleyhttp://en.wikipedia.org/wiki/Ian_Sommerville_%28academic%29http://en.wikipedia.org/wiki/Agile_software_development#cite_ref-7


12/12


31. Sutherland, Jeff. "Scrum and CMMI Level

agile sdlc (wiki)

Documents