TITLE

History: The Agile Manifesto

PUB. DATE
January 2005
SOURCE
Software World;Jan2005, Vol. 36 Issue 1, p14
SOURCE TYPE
Periodical
DOC. TYPE
Article
ABSTRACT
The article focuses on the principles behind the "Agile Software Development Manifesto" which was developed in February 11-13, 2001 in Utah, by representatives from some software development companies and others sympathetic to the need for an alternative to documentation driven, heavyweight software development. The signatories aim to satisfy the customer through early and continuous delivery of valuable software. The proponents commit to welcome changing requirements, to deliver working software frequently, to build projects around motivated individuals, and to pay continuous attention to technical excellence and good design to enhance agility. They believe that agile processes promote sustainable development and that the best architectures, requirements, and designs emerge from self-organizing teams. INSET: Principles behind the Agile Manifesto..
ACCESSION #
16455529

 

Related Articles

  • An Agile Software Roadmap.  // Software World;Jan2005, Vol. 36 Issue 1, p16 

    The article provides a background on the "Manisfeto for Agile Software Development," which was created by various originators and practitioners of agile methodologies in early 2001 in Utah. The manifesto values individuals and interactions over processes and tools, working software over...

  • When Software Isn't a Product. Downes, Larry // CIO Insight;Jul2008, Issue 95, p20 

    The author reflects on the software development which started from a product to a packaged software and then to a service. It states that as software architectures become standard and the purchase of the said product is governed by the law of sales, encapsulated in the Uniform Commercial Code....

  • Is Internet-Speed Software Development Different? Baskerville, Richard; Ramesh, Balasubramaniam; Levina, Linda; Pries-Heje, Jan; Slaughter, Sandra // IEEE Software;Nov/Dec2003, Vol. 20 Issue 6, p70 

    Focuses on the development of software at Internet-speed to cope with fast changing requirements and increasing demands of the market. Comparison of Internet-speed software development with traditional software development; Impact of customer involvement in traditional software development on...

  • A Script in Time Saves 9. Otey, Michael // SQL Server Magazine;Mar2007, Vol. 9 Issue 3, p3 

    The article presents the author's views about the software development process. According to the author, one of the mistakes made by the software-development companies in software-development projects is rushing the next release out the door. The author says that in this case end users and...

  • Understanding the Role of Core Developers in Open Source Software Development. Ju Long // Journal of Information, Information Technology & Organizations;2006, Vol. 1, p75 

    Most Open Source Software projects fail, while only very few succeed. In this study, we examine the factors that may influence the success or failure of OSS projects. We particularly focus on OSS core developer roles. We separate core developers from other developers in the community and...

  • VMWorld: Virtualization benefits have 'only just begun' for data center industry. Taylor, Colleen // Electronic News;9/17/2007, Vol. 53 Issue 38, p25 

    The article discusses the highlights of the VMWorld Conference. During the conference, Mendel Rosenblum, the chief scientist of virtualization software developer VMWare Inc., stated that the data center industry has only just begun to witness the benefits of virtualization technology. It was...

  • Eliminating those excuses. Coffe, Peter // eWeek;4/17/2006, Vol. 23 Issue 16, pD6 

    The article evaluates Microsoft Corp.'s Visual Studio Team System for managing software development.

  • Improving Software Development through Three Stages. Motoyama, Tetsuro // IEEE Software;Sep/Oct2006, Vol. 23 Issue 5, p81 

    The article discusses the author's experiences in a software development process. He talked about the three stages defined in the process of improving software development. He recalls that the first stage is the major factor of software development process improvement. This first stage is the...

  • Building the LabVIEW Ecosystem.  // Instrumentation Newsletter;2007 3rd Quarter, Vol. 19 Issue 3, p30 

    The article reports on the impact of the growth of National Instruments' LabVIEW software on the ecosystem of third-party product developers. As the LabVIEW applications have grown, the ecosystem also expanded. Many developers create add-on tools and products for LabVIEW that include...

Share

Read the Article

Courtesy of THE LIBRARY OF VIRGINIA

Sorry, but this item is not currently available from your library.

Try another library?
Sign out of this library

Other Topics