Open Access Articles- Top Results for Agile software development

Agile software development

Software development process
Core activities
Supporting disciplines

Agile software development is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement, and encourages rapid and flexible response to change.[1]

The Manifesto for Agile Software Development,[2] also known as the Agile Manifesto, first introduced the term agile in the context of software development in 2001.



Incremental software development methods trace back to 1957.[3] In 1974, E. A. Edmonds wrote a paper that introduced an adaptive software development process.[4][5] Concurrently and independently, the same methods were developed and deployed by the New York Telephone Company's Systems Development Center under the direction of Dan Gielan. In the early 1970s, Tom Gilb started publishing the concepts of evolutionary project management (EVO), which has evolved into competitive engineering.[6] During the mid- to late 1970s, Gielan lectured extensively throughout the U.S. on this methodology, its practices, and its benefits.

A collection of lightweight software development methods evolved in the mid-1990s in reaction to the perceived heavyweight waterfall-oriented methods, which critics called heavily regulated, regimented, and micro-managed; although some proponents of these lightweight methods contended that they were simply returning to earlier software practices.[3] These lightweight methods included: from 1994, unified process and dynamic systems development method (DSDM); from 1995, scrum; from 1996, crystal clear and extreme programming (aka "XP"); and from 1997, adaptive software development and feature-driven development. Although these originated before the publication of the Agile Manifesto in 2001, they are now collectively referred to as agile methods;[7] and often abbreviated loosely as Agile, with a capital A, although this is progressively becoming deprecated.[8]

The Agile Manifesto

In February 2001, 17 software developers (see below) met at the Snowbird resort in Utah to discuss lightweight development methods. They published the Manifesto for Agile Software Development:[2]

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.[2]
Kent Beck James Grenning Robert C. Martin
Mike Beedle Jim Highsmith Steve Mellor
Arie van Bennekum Andrew Hunt Ken Schwaber
Alistair Cockburn Ron Jeffries Jeff Sutherland
Ward Cunningham Jon Kern Dave Thomas
Martin Fowler Brian Marick

© 2001, the above authors. This declaration may be freely copied in any form, but only in its entirety through this notice.

The meanings of the manifesto items on the left are:

  • Individuals and interactions: self-organization and motivation are important, as are interactions like co-location and pair programming.
  • Working software: working software is more useful and welcome than just presenting documents to clients in meetings.
  • Customer collaboration: requirements cannot be fully collected at the beginning of the software development cycle, therefore continuous customer or stakeholder involvement is very important.
  • Responding to change: agile methods are focused on quick responses to change and continuous development.[9]

Some of the authors formed the Agile Alliance, a non-profit organization that promotes software development according to the manifesto's values and principles. Introducing the manifesto on behalf of the Agile Alliance, Jim Highsmith said,

The Agile movement is not anti-methodology, in fact many of us want to restore credibility to the word methodology. We want to restore a balance. We embrace modeling, but not in order to file some diagram in a dusty corporate repository. We embrace documentation, but not hundreds of pages of never-maintained and rarely-used tomes. We plan, but recognize the limits of planning in a turbulent environment. Those who would brand proponents of XP or SCRUM or any of the other Agile Methodologies as "hackers" are ignorant of both the methodologies and the original definition of the term hacker.
—Jim Highsmith, History: The Agile Manifesto[10]

Agile principles

The Agile Manifesto is based on 12 principles:[11]

  1. Customer satisfaction by rapid delivery of useful software
  2. Welcome changing requirements, even late in development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the principal measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
  10. Simplicity—the art of maximizing the amount of work not done—is essential
  11. Self-organizing teams
  12. Regular adaptation to changing circumstance


Later, Ken Schwaber with others founded the Scrum Alliance and created the Certified Scrum Master programs and its derivatives. Schwaber left the Scrum Alliance in the fall of 2009, and founded

In 2005, a group headed by Alistair Cockburn and Jim Highsmith wrote an addendum of project management principles, the Declaration of Interdependence,[12] to guide software project management according to agile software development methods.

In 2009, a movement spearheaded by Robert C Martin wrote an extension of software development principles, the Software Craftsmanship Manifesto, to guide agile software development according to professional conduct and mastery.

In 2011 the original Agile Alliance[13] created the Guide to Agile Practices, an evolving open-source compendium of the working definitions of agile practices, terms, and elements, along with interpretations and experience guidelines from the world-wide community of agile practitioners.

The PRINCE2 project management methodology, used on many British Government projects, is being enhanced to manage projects that use Agile techniques.[14]


File:Pair programming 1.jpg
Pair programming, an agile development technique used by XP. Note information radiators in the background.

There are many specific agile development methods. Most promote development, teamwork, collaboration, and process adaptability throughout the life-cycle of the project.

Iterative, incremental and evolutionary

Most agile development methods break the tasks into small increments with minimal planning and do not directly involve long-term planning. Iterations are short time frames (timeboxes) that typically last from one to four weeks. Each iteration involves a cross-functional team working in all functions: planning, requirements analysis, design, coding, unit testing, and acceptance testing. At the end of the iteration a working product is demonstrated to stakeholders. This minimizes overall risk and allows the project to adapt to changes quickly. An iteration might not add enough functionality to warrant a market release, but the goal is to have an available release (with minimal bugs) at the end of each iteration.[15] Multiple iterations might be required to release a product or new features.

Efficient and face-to-face communication

No matter what development disciplines are required, each agile team should include a customer representative (product owner in scrum). This person is appointed by stakeholders to act on their behalf[16] and makes a personal commitment to being available for developers to answer mid-iteration questions. At the end of each iteration, stakeholders and the customer representative review progress and re-evaluate priorities with a view to optimizing the return on investment (ROI) and ensuring alignment with customer needs and company goals.

In agile software development, an information radiator is a (normally large) physical display located prominently in an office, where passers-by can see it. It presents an up-to-date summary of the status of a software project or other product.[17][18] The name was coined by Alistair Cockburn, and described in his 2002 book Agile Software Development.[18] A build light indicator may be used to inform a team about the current status of their project.

Very short feedback loop and adaptation cycle

A common characteristic in agile development is the daily "stand-up", also known as the daily scrum. In a brief session, team members report to each other what they did the previous day toward their team's sprint goal, what they intend to do today toward their team's sprint goal, and any roadblocks or impediments they can see to their team's sprint goal.[19]

Quality focus

Specific tools and techniques, such as continuous integration, automated unit testing, pair programming, test-driven development, design patterns, domain-driven design, code refactoring and other techniques are often used to improve quality and enhance project agility.


Compared to traditional software engineering, agile software development mainly targets complex systems and projects with dynamic, undeterministic and non-linear characteristics, where accurate estimates, stable plans, and predictions are often hard to get in early stages—and big up-front designs and arrangements would probably cause a lot of waste, i.e., are not economically sound. These basic arguments and previous industry experiences, learned from years of successes and failures, have helped shape agile development's favor of adaptive, iterative and evolutionary development.[20]

Adaptive vs. predictive

Development methods exist on a continuum from adaptive to predictive.[21] Agile methods lie on the adaptive side of this continuum. One key of adaptive development methods is a "Rolling Wave" approach to schedule planning, which identifies milestones but leaves flexibility in the path to reach them, and also allows for the milestones themselves to change.[22] 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 has difficulty describing exactly what will happen in the future. The further away a date is, the more vague an adaptive method is about what will happen on that date. An adaptive team cannot report exactly what tasks they will do next week, but only which features they plan for next month. When asked about a release six months from now, an adaptive team might be able to report only the mission statement for the release, or a statement of expected value vs. cost.

Predictive method, in contrast, focus on analysing and planning the future in detail and cater for known risks. In the extremes, a predictive team can report exactly what features and tasks are planned for the entire length of the development process. Predictive methods rely on effective early phase analysis and if this goes very wrong, the project may have difficulty changing direction. Predictive teams often institute a change control board to ensure they consider only the most valuable changes.

Risk analysis can be used to choose between adaptive (agile or value-driven) and predictive (plan-driven) methods.[23] Barry Boehm and Richard Turner suggest that each side of the continuum has its own home ground, as follows:[24]

Home grounds of different development methods
Agile methods Plan-driven methods Formal methods
Low criticality High criticality Extreme criticality
Senior developers Junior developers(?) Senior developers
Requirements change often Requirements do not change often Limited requirements, limited features see Wirth's law
Small number of developers Large number of developers Requirements that can be modeled
Culture that responds to change Culture that demands order Extreme quality

Iterative vs. waterfall

One of the differences between agile and waterfall is the approach to quality and testing. In the waterfall model, there is always a separate testing phase after a build phase; however, in agile development testing is usually done concurrently with, or at least in the same iteration as, programming.

Because testing is done in every iteration—which develops a small piece of the software—users can frequently use those new pieces of software and validate the value.

After the users know the real value of the updated piece of software, they can make better decisions about the software's future. Having a value retrospective and software re-planning session in each iteration—scrum typically has iterations of just two weeks—helps the team continuously adapt its plans so as to maximize the value it delivers.

This iterative practice also introduces a product mindset rather than the waterfall model's project mindset. Software can be seen as a living organism, which actively changes due to environmental change. As long as the software is being used, especially when it has competition, iterations in agile software development drive the change.

Because of the short iteration style of agile software development, it also has strong connections with the lean startup concept.

Code vs. documentation

In a letter to IEEE Computer, Steven Rakitin expressed cynicism about agile development, calling it "yet another attempt to undermine the discipline of software engineering" and translating "Working software over comprehensive documentation" as "We want to spend all our time coding. Remember, real programmers don't write documentation."[25]

This is disputed by proponents of agile software development, who state that developers should write documentation if that's the best way to achieve the relevant goals, but that there are often better ways to achieve those goals than writing static documentation.[26] Scott Ambler states that documentation should be "Just Barely Good Enough" (JBGE),[27] that too much or comprehensive documentation would usually cause waste, and developers rarely trust detailed documentation because it's usually out of sync with code,[26] while too little documentation may also cause problems for maintenance, communication, learning and knowledge sharing. Alistair Cockburn wrote of the Crystal Clear method:

Crystal considers development a series of co-operative games, and intends that the documentation is enough to help the next win at the next game. The work products for Crystal include use cases, risk list, iteration plan, core domain models, and design notes to inform on choices...however there are no templates for these documents and descriptions are necessarily vague, but the objective is clear, just enough documentation for the next game. I always tend to characterize this to my team as: what would you want to know if you joined the team tomorrow.[28]
—Alistair Cockburn[attribution verification needed]

Agile methods

Well-known agile software development methods and/or process frameworks include:

Software development life-cycle support[29]

Agile methods are focused on different aspects of the software development life cycle. Some focus on the practices (e.g. XP, pragmatic programming, agile modeling), while others focus on managing the software projects (e.g. scrum). Yet, there are approaches providing full coverage over the development life cycle (e.g. DSDM, RUP), while most of them are suitable from the requirements specification phase on (FDD, for example). Thus, there is a clear difference between the various agile methods in this regard.[29]

Agile practices

Agile development is supported by a bundle of concrete practices, covering areas like requirements, design, modelling, coding, testing, project management, process, quality, etc. Some notable agile practices include:

The Agile Alliance has provided a comprehensive online collection with a map guide to the applying agile practices.[30]

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 determine a system development approach for a specific project situation through responsive changes in, and dynamic interplays between contexts, intentions, and method fragments.[31]

Potentially, almost all agile methods are suitable for method tailoring. Even the DSDM method is being used for this purpose and has been successfully tailored in a CMM context.[32] Situation-appropriateness can be considered 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 of principles, could be adapted (Aydin, 2004).[31]

Extreme programming (XP) makes the need for method adaptation explicit. One of the fundamental ideas of XP is that no 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 by Beck, has been reported on several occasions.[29] Mehdi Mirakhorli proposes a tailoring practice that provides a sufficient road-map and guidelines for adapting all the practices. RDP Practice is designed for customizing XP. This practice, first proposed as a long research paper in the APSO workshop at the ICSE 2008 conference, is currently 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.[33]

Comparison with other methods


Agile methods have much in common with the Rapid Application Development techniques from the 1980/90s as espoused by James Martin and others.[citation needed] In addition to technology-focused methods, customer-and-design-centered methods, such as Visualization-Driven Rapid Prototyping developed by Brian Willison, work to engage customers and end users to facilitate agile software development.[citation needed]


In 2008 the Software Engineering Institute (SEI) published the technical report "CMMI or Agile: Why Not Embrace Both"[34] to make clear that the Capability Maturity Model Integration and Agile can co-exist. Modern CMMI-compatible development processes are also iterative. The CMMI Version 1.3 includes tips for implementing CMMI and agile process improvement together.[35]

Large-scale and distributed agile development

Agile development has been widely seen as highly suited to certain types of environments, including small teams of experts working on greenfield projects,[24][36]:157 and the challenges and limitations encountered in the adoption of agile methods in a large organization with legacy infrastructure are well-documented and understood.[37]

In response, a range of strategies and patterns has evolved for overcoming challenges with large-scale development efforts (>20 developers)[38][39] or distributed (non-colocated) development teams,[40][41] amongst other challenges; and there are now several recognised frameworks that seek to mitigate or avoid these challenges, including:

There are many conflicting viewpoints on whether all of these are effective or indeed fit the definition of agile development, and this remains an active and ongoing area of research.[38][42]

When agile software development is applied in a distributed setting (with teams dispersed across multiple business locations), it is commonly referred to as Distributed Agile Development. The goal is to leverage the unique benefits offered by each approach. Distributed development allow organizations to build software by strategically setting up teams in different parts of the globe, virtually building software round-the-clock (more commonly referred to as follow-the-sun model). On the other hand, agile development provides increased transparency, continuous feedback and more flexibility when responding to changes.

Experience and adoption

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)[43] score projects against a number of agility factors to achieve a total. The similarly named Agility Measurement Index,[44] scores developments against five dimensions of a software project (duration, risk, novelty, effort, and interaction). Other techniques are based on measurable goals.[45] Another study using fuzzy mathematics[46] 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 (Nokia test,[47] Karlskrona test,[48] 42 points test[49]).

While such approaches have been proposed to measure agility, the practical application of such metrics is still debated. There is agile software development ROI data available from the CSIAC ROI Dashboard.[50]


One of the early studies reporting gains in quality, productivity, and business satisfaction by using Agile methods was a survey conducted by Shine Technologies from November 2002 to January 2003.[51] A similar survey, the State of Agile, is conducted every year starting in 2006 with thousands of participants from around the software development community. The State of Agile survey tracks trends on the benefits of agile, trends, lessons learned, preferred practices and agile methodologies. From the 2013 results released in January 2014, the survey concludes that 73% of respondents say agile software helps them complete software projects faster; 92% say agile improves their ability to manage changing customer priorities; and 87% say agile improves their development team's productivity.[52] Yet another survey conducted in 2006 by Scott Ambler, the Practice Leader for Agile Development with IBM Rational's Methods Group reported similar benefits.[53] Others claim that agile development methods are still too young to require extensive academic proof of their success.[54]

Common agile pitfalls

Organizations and teams implementing agile development often face difficulties transitioning from more traditional methods such as waterfall development, such as teams having an agile process forced on them.[55] These are often termed agile anti-patterns or more commonly agile smells. Below are some common examples:

Lack of overall project design

This can lead to lack of scalability and design flaws—like building a house with no blueprint and hoping it remains standing.

Adding stories to a sprint in progress

Adding stories to a sprint in progress is detrimental to the flow established by Agile. From Ilan Goldstein's Sprint issues – when sprints turn into crawls, "'Isn't the ability to change course on the fly what Scrum is all about?' Well not quite. Scrum certainly provides provision to change product backlog priorities mid-project however this needs to occur between sprints and not during them."[56]

If an issue arises that requires additions to a sprint, Ilan recommends an abnormal sprint termination.[56] This does not mean that a user story cannot expand. Teams must deal with new information, which may produce additional tasks for a user story. If the new information prevents the user story from being production-ready during the sprint, then it should carry over to the next sprint. However, during the next sprint planning, the user story should be prioritized over all remaining user stories. The information that requires new tasks may have altered the user story priority.

Lack of sponsor support

Agile is often implemented as a grassroots efforts in organizations by software development teams trying to optimize their development processes. By not having sponsor support, teams may face difficulties and resistance from business partners, other development teams and management. "Carrying on without an effective sponsor raises the probability of project failure..."[57]

Additionally, the project sponsor is responsible for ensuring the team has appropriate funding and resources.[58]

Insufficient training

A survey performed by Version One found respondents cited insufficient training as the most significant cause for failed agile projects[59] Teams have fallen into the trap of assuming the reduced processes of agile development compared to other methodologies such as waterfall mean there are no actual rules for agile development. Agile development is a set of prescribed methodologies, and training/practice is a requirement.

Product owner role is not properly filled

The product owner is responsible for representing the business in the development activity. In The Elements of Scrum the product owner "... is usually the most demanding role on a scrum team."[60]

A common mistake is to have the product owner role filled by someone from the development team. According to Johanna Rothman this is a mistake, "When the business is unaccountable, the agile ecosystem breaks down."[61] Having the development team fill this role results in the team making its own decisions on prioritization without real feedback from the business. Additionally, the team either tries to solve business issues internally or delay as they reach outside the core group for input. This can cause finger-pointing and divert from the collaborative process directed.

Teams are not focused

The agile process requires teams who focus on the project to meet project commitments. During a sprint, a resource who has the capacity is expected to take up tasks potentially outside their area of greatest expertise or comfort.

If team members have multiple projects, it is difficult to make spare capacity available to help complete the sprint. "While having information developers working on multiple scrum teams is not ideal, it can be done with some proper planning and judicious evaluation of which meetings you should attend."[62]

Excessive preparation/planning

Teams may fall into the trap of spending too much time preparing or planning. This is a common trap for teams less familiar with the agile process where the teams feel obligated to have a complete understanding of all user stories or a detailed design. Teams should leverage the ability for Sprints to act as a method discovery and moving forward with the information they do know. As more information is gained it should be applied to the next Sprint.

Problem-solving in the daily standup

A daily standup should be a focused, timely meeting where all team members disseminate information. If problem-solving occurs, it often can only involve certain team members and potentially is not the best use of the entire team's time. If during the daily standup the team starts diving into problem-solving, it should be tabled until a sub-team can discuss, usually immediately after the daily scrum completes.[63]

Assigning Tasks

One of the intended benefits of agile development is to empower the team to make choices, as they are closest to the problem. Additionally, they should make choices as close to implementation as possible—compared to a waterfall approach—to use more timely information in the decision. If team members are assigned tasks by others or too early in the process, the benefits of localized and timely decision making can be lost.[64]

Another tendency is for assigners to box team members into certain roles (for example, team member A must always do the database work), which hinders cross-training.[64] Team members themselves can choose to take on tasks that stretch their abilities and provide cross-training opportunities.

Scrum master as a contributor

Another common pitfall is for a scrum master to act as a contributor. While not prohibited by the Scrum methodology, the scrum master needs to ensure they have the capacity to act in the role of scrum master first and not working on tasks for the project. A scrum master's role is to facilitate the Scrum process. "Facilitating meetings such as a daily scrum, sprint planning, sprint reviews and sprint retrospectives is part of this. A technical contributor's role is to work with the other team members to figure out how to get the work done and to do it."[65]

Having the scrum master also multitasking may result in too many context switches to be productive. Additionally, as a scrum master is responsible for ensuring roadblocks are removed so that the team can make forward progress, the benefit gained by individual tasks moving forward may not outweigh roadblocks that are deferred due to lack of capacity.[65]

Lacking test automation

Due to the iterative nature of agile development, multiple rounds of testing for a project are often needed. "Having an automated testing framework, which takes care of both system and integration tests, adds a lot of firepower to such a team. It not only acts as a safety net against regressions caused by new development, but more importantly frees up a lot of precious developer and tester time - allowing them to focus on the things they do best."[66]

Test automation also supports continued refactoring required by iterative software development. Allowing a developer to quickly run tests to confirm refactoring has not modified the functionality of the application may reduce the workload and increase confidence that cleanup efforts have not introduced new defects.

Allowing technical debt to build up

Focusing on delivering new functionality may result in increased technical debt. The team must allow themselves time for defect remediation and refactoring. Technical debt hinders planning abilities by increasing the amount of unscheduled work as production defects distract the team from further project progress.[67]

As the system evolves it is important to refactor as entropy of the system naturally increases.[68] Over time the lack of constant maintenance causes increasing defects and development costs.[67]

Attempting to take on too much in a sprint

This is not applicable to Kanban, which does not have sprints.

A common misconception is that agile development allows continuous change, however a sprint backlog is an agreement of what work can be completed during the sprint.[69] Additionally having too much work-in-progress(WIP) can result in inefficiencies due "to avoid the penalties of wasted time, effort and resources."[70]

A possible issue is the team being pressured into taking on additional work. "An important point to reiterate here is that it's the team that selects how much work they can do in the coming sprint. The product owner does not get to say, 'We have four sprints left so you need to do one-fourth of everything I need.' We can hope the team does that much (or more), but it's up to the team to determine how much they can do in the sprint."[71]

Fixed time, resources, scope, and quality

Agile development fixes time (sprint duration), quality, and ideally resources in advance (though maintaining fixed resources may be difficult if developers are often pulled away from tasks to handle production incidents), while the scope remains variable. The customer or product owner often pushes for a fixed scope for a sprint. However, teams should be reluctant to commit to locked time, resources and scope (commonly known as the project management triangle). Efforts to add scope to the fixed time and resources of agile development may result in decreased quality.[72]


Agile methodologies can be very difficult for large organizations such as governments and multinational banks to faithfully adopt, for reasons ranging for lack of sponsor buy-in to agile, to refusal to heed agile consultants' advice on co-located teams - and particularly in the case of governments, outdated procurement and project management policies that assume non-agile methodologies.[citation needed]

Agile methodologies can be inefficient in large organizations and certain types of projects.[citation needed] Agile methods seem best for developmental and non-sequential projects. Many organizations believe that agile methodologies are too extreme and adopt a hybrid approach that mixes elements of agile and plan-driven approaches.[73] However, DSDM is an agile methodology that in fact mixes elements of agile and plan-driven approaches in a disciplined way, without sacrificing the fundamental principles that make agile work.

The term "agile" has also been criticized as being a management fad that simply describes existing good practices under new jargon, promotes a "one size fits all" mindset towards development strategies, and wrongly emphasizes method over results.[74]

Alistair Cockburn organized a celebration of the 10th anniversary of the Agile Manifesto in Snowbird, Utah on February 12, 2011, gathering some 30+ people who had been involved at the original meeting and since. A list of about 20 elephants in the room ("undiscussable" agile topics/issues) were collected, including aspects: the alliances, failures and limitations of agile practices and context (possible causes: commercial interests, decontextualization, no obvious way to make progress based on failure, limited objective evidence, cognitive biases and reasoning fallacies), politics and culture.[75] As Philippe Kruchten wrote:

The agile movement is in some ways a bit like a teenager: very self-conscious, checking constantly its appearance in a mirror, accepting few criticisms, only interested in being with its peers, rejecting en bloc all wisdom from the past, just because it is from the past, adopting fads and new jargon, at times cocky and arrogant. But I have no doubts that it will mature further, become more open to the outside world, more reflective, and also therefore more effective.

Application outside software development

Agile methods have been extensively used for development of software products and some of them use certain characteristics of software, such as object technologies.[76] However, these techniques can be applied to the development of non-software products, such as computers, motor vehicles, medical devices, food, clothing, and music;[77] see Flexible product development.

Agile development paradigms can be used in other areas of life such as raising children. Its success in child development might be founded on some basic management principles; communication, adaptation and awareness. Bruce Feiler has claimed that the basic Agile Development paradigms can be applied to household management and raising children. In his TED Talk, "Agile programming -- for your family", these paradigms brought significant changes to his household environment, such as the kids doing dishes, taking out the trash, and decreasing his children's emotional outbreaks, which inadvertently increased their emotional stability. In some ways, agile development is more than a bunch of software development rules: it can be something more simple and broad, like a problem solving guide.


  1. ^ "What is Agile Software Development?". Agile Alliance. 8 June 2013. Retrieved 4 April 2015. 
  2. ^ a b c Beck, Kent et al. (2001). "Manifesto for Agile Software Development". Agile Alliance. Retrieved 14 June 2010. 
  3. ^ a b Gerald M. Weinberg, as quoted in Larman, Craig; Basili, Victor R. (June 2003). "Iterative and Incremental Development: A Brief History". Computer 36 (6): 47–56. ISSN 0018-9162. doi:10.1109/MC.2003.1204375. We were doing incremental development as early as 1957, in Los Angeles, under the direction of Bernie Dimsdale at IBM's Service Bureau Corporation. He was a colleague 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.' 
  4. ^ Edmonds, E. A. (1974). "A Process for the Development of Software for Nontechnical Users as an Adaptive System". General Systems 19: 215–18. 
  5. ^ Note by Edmonds: I presented these ideas in London in 1970 and first submitted the paper to the Journal Computer Aided Design. It was rejected with the comment "If you don't know what you are going to do before you start you shouldn't start"! Only then did I submit it to General Systems.
  6. ^ "Evolutionary Project Management". Gilb. 
  7. ^ Larman, Craig (2004). Agile and Iterative Development: A Manager's Guide. Addison-Wesley. p. 27. ISBN 978-0-13-111155-4. 
  8. ^ "a"-vs-agile-lowercase-"a" "Agile With a Capital "A" Vs. agile With a Lowercase "a"". Rally. 2010. Retrieved 31 March 2015. 
  9. ^ Ambler, S.W. "Examining the Agile Manifesto". Retrieved 6 April 2011.
  10. ^ Jim Highsmith (2001). "History: The Agile Manifesto". 
  11. ^ Beck, Kent et al. (2001). "Principles behind the Agile Manifesto". Agile Alliance. Archived from the original on 14 June 2010. Retrieved 6 June 2010. 
  12. ^ Anderson, David (2005). "Declaration of Interdependence". 
  13. ^
  14. ^ "PRINCE2® Agile". Axelos Ltd. Retrieved 6 March 2015. 
  15. ^ Beck, Kent (1999). "Embracing Change with Extreme Programming". Computer 32 (10): 70–77. doi:10.1109/2.796139. 
  16. ^ Gauthier, Alexandre (17 August 2011). "What is scrum". Planbox. 
  17. ^ Cockburn, Alistair. "Information radiator". 
  18. ^ a b Ambler, Scott (12 April 2002). Agile Modeling: Effective Practices for EXtreme Programming and the Unified Process. John Wiley & Sons. pp. 12, 164, 363. ISBN 978-0-471-20282-0. 
  19. ^ Vasiliauskas, Vidas (2014). "Developing agile project task and team management practices". Eylean. 
  20. ^ Larman, Craig (2004). Agile and Iterative Development: A Manager's Guide. Addison-Wesley. p. 27. ISBN 978-0-13-111155-4. 
  21. ^ 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
  22. ^ Larman, Craig (2004). "Chapter 11: Practice Tips". Agile and Iterative Development: A Manager's Guide. p. 253. ISBN 9780131111554. Retrieved October 14, 2013. 
  23. ^ Sliger, Michele; Broderick, Stacia (2008). The Software Project Manager's Bridge to Agility. Addison-Wesley. p. 46. ISBN 0-321-50275-2. 
  24. ^ a b Boehm, B.; R. Turner (2004). Balancing Agility and Discipline: A Guide for the Perplexed. Boston, MA: Addison-Wesley. pp. 55–57. ISBN 0-321-18612-5. 
  25. ^ Rakitin, Steven R. (2001). "Manifesto Elicits Cynicism: Reader's letter to the editor by Steven R. Rakitin". IEEE Computer 34: 4. The article titled 'Agile Software Development: The Business of Innovation' . . . is yet another attempt to undermine the discipline of software engineering . . . We want to spend all our time coding. Remember, real programmers don’t write documentation. 
  26. ^ a b Scott Ambler. "Agile/Lean Documentation: Strategies for Agile Software Development". 
  27. ^ Scott Ambler. "Just Barely Good Enough Models and Documents: An Agile Best Practice". 
  28. ^ Geoffrey Wiseman (July 18, 2007). "Do Agile Methods Require Documentation?". InfoQ. 
  29. ^ a b c Abrahamson P, Salo O, Ronkainen J, Warsta J (2002). Agile software development methods: Review and analysis (PDF) (Technical report). VTT. 478. 
  30. ^ "Guide to Agile Practices". the Agile Alliance. 
  31. ^ a b Aydin, 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
  32. ^ Abrahamsson, P., Warsta, J., Siponen, M.T., & Ronkainen, J. (2003). New Directions on Agile Methods: A Comparative Analysis. Proceedings of ICSE'03, 244-254
  33. ^ Aydin, M.N., Harmsen, F., Slooten van K., & Stegwee, R.A. (2005). On the Adaptation of An Agile Information(Suren) Systems Development Method. Journal of Database Management Special issue on Agile Analysis, Design, and Implementation, 16(4), 20-24
  34. ^ "TECHNICAL NOTE CMU/SEI-2008-TN-003 CMMI or Agile: Why Not Embrace Both". 
  35. ^ CMMI Product Team, ; CMMI for Development, Version 1.3 (CMU/SEI-2010-TR-033). Software Engineering Institute, Carnegie Mellon University, 2010.
  36. ^ Beck, K. (1999). Extreme Programming Explained: Embrace Change. Boston, MA: Addison-Wesley. ISBN 0-321-27865-8. 
  37. ^ Evans, Ian. "Agile Delivery at British Telecom". Retrieved 21 February 2011. 
  38. ^ a b W. Scott Ambler (2006) Supersize Me in Dr. Dobb's Journal, 15 February 2006.
  39. ^ Schaaf, R.J. (2007). Agility XL Systems and Software Technology Conference 2007, Tampa, FL
  40. ^ "Bridging the Distance". Retrieved 1 February 2011. 
  41. ^ Martin Fowler. "Using an Agile Software Process with Offshore Development". Retrieved 6 June 2010. 
  42. ^ Agile Processes Workshop II Managing Multiple Concurrent Agile Projects. Washington: OOPSLA 2002
  43. ^ "David Bock's Weblog : Weblog". Retrieved 2 April 2010. 
  44. ^ "Agility measurement index". Retrieved 2 April 2010. 
  45. ^ Peter Lappo; Henry C.T. Andrew. "Assessing Agility" (PDF). Retrieved 6 June 2010. 
  46. ^ Kurian, Tisni (2006). Agility Metrics: A Quantitative Fuzzy Based Approach for Measuring Agility of a Software Process, ISAM-Proceedings of International Conference on Agile Manufacturing'06(ICAM-2006), Norfolk, U.S.
  47. ^ Joe Little (2 December 2007). "Nokia test, A scrum-specific test". Retrieved 6 June 2010. 
  48. ^ Mark Seuffert, Mayberg, Sweden. "Karlskrona test, A generic agile adoption test". Retrieved 5 Apr 2014. 
  49. ^ "How Agile Are You? (Take This 42 Point Test)". Retrieved 3 April 2014. 
  50. ^ CSIAC ROI Dashboard Retrieved 11 November 2011.
  51. ^ "Agile Methodologies Survey Results" (PDF). Shine Technologies. January 2003. Retrieved 3 June 2010. 95% stated that there was either no effect or a cost reduction ... 93% stated that productivity was better or significantly better ... 88% stated that quality was better or significantly better ... 83% stated that business satisfaction was better or significantly better 
  52. ^ "2013 State of Agile report: Why Agile?". 27 January 2014. Retrieved 13 August 2014. 
  53. ^ Ambler, Scott (3 August 2006). "Survey Says: Agile Works in Practice". Dr. Dobb's. Retrieved 3 June 2010. Only 6% indicated that their productivity was lowered ... No change in productivity was reported by 34% of respondents and 60% reported increased productivity ... 66% [responded] that the quality is higher ... 58% of organizations report improved satisfaction, whereas only 3% report reduced satisfaction. 
  54. ^ "Answering the "Where is the Proof That Agile Methods Work" Question". 19 January 2007. Retrieved 2 April 2010. 
  55. ^ Shore, James; Warden, Shane. Art of Agile Development. p. 47. 
  56. ^ a b Goldstein, Ilan. "Sprint issues – when sprints turn into crawls". Retrieved 2014-06-08. 
  57. ^ Bourne, Lynda. "What Does a Project Sponsor Really Do?". Retrieved 2014-06-08. 
  58. ^ "Project Roles and Responsibility Distribution". Retrieved 2014-06-15. 
  59. ^ "State of Agile Development Survey Results". Version One. Retrieved 2014-06-08. 
  60. ^ Sims, Chris; Johnson, Hillary Louise (2011-02-15). The Elements of Scrum (Kindle Edition ed.). Dymaxicon. p. 73. 
  61. ^ Rothman, Johanna Rothman. "When You Have No Product Owner At All". Retrieved 2014-06-08. 
  62. ^ Fox, Alyssa. "Working on Multiple Agile Teams". Retrieved 2014-06-14. 
  63. ^ "Daily Scrum Meeting". Retrieved 2014-06-14. 
  64. ^ a b May, Robert. "Effective Sprint Planning". Retrieved 2014-06-14. 
  65. ^ a b Berczuk, Steve. "Mission Possible: ScrumMaster and Technical Contributor". Retrieved 2014-06-14. 
  66. ^ Namta, Rajneesh. "Thoughts on Test Automation in Agile". Retrieved 2014-06-14. 
  67. ^ a b Band, Zvi. "Technical Debt + Red October". Retrieved 8 June 2014. 
  68. ^ Shore, James. "The Art of Agile Development: Refactoring". Retrieved 2014-06-14. 
  69. ^ "Step 4: Sprint Planning (Tasks)". Retrieved 2014-06-14. 
  70. ^ George, Claire. "Why Limiting Your Work-in-Progress Matters". Retrieved 2014-06-14. 
  71. ^ "Sprint Planning Meeting". Retrieved 2014-06-14. 
  72. ^ McMillan, Keith. "Time, Resources, Scope… and Quality.". Retrieved 2014-06-15. 
  73. ^ Barlow, Jordan B.; Justin Scott Giboney; Mark Jeffery Keith; David W. Wilson; Ryan M. Schuetzler; Paul Benjamin Lowry; Anthony Vance (2011). "Overview and Guidance on Agile Development in Large Organizations". Communications of the Association for Information Systems 29 (1): 25–44. 
  74. ^ Kupersmith, Kupe. "Agile is a Fad". 
  75. ^ Kruchten, Philippe (2011-06-20). "Agile's Teenage Crisis?". InfoQ. 
  76. ^ Smith, Preston G (2007). Flexible Product Development. Jossey-Bass. p. 25. ISBN 978-0-7879-9584-3. 
  77. ^ Newton Lee (2014). "Getting on the Billboard Charts: Music Production as Agile Software Development," Digital Da Vinci: Computers in Music<span />. Springer Science+Business Media. ISBN 978-1-4939-0535-5. 

Further reading

External links

Lua error in Module:Authority_control at line 346: attempt to index field 'wikibase' (a nil value).