Agile Manifesto Values and Principles

last edited by: Stelian ROMAN on Apr 5, 2019 7:31 AM login/register to edit this page
Keywords: Knowledge and Skills PMI-ACP

Contents
1 Contents
2 Overview
3 Manifesto for Agile Software Development
4 Values
5 Principles
6 Importance
7 PMI-ACP Exam Outline Reference
8 Body
9 History
10 Current practice
11 See also
12 Sources & Reference
13 External Links

Contents

1 Overview
2 Values

Overview

  1. overview

  2. Manifesto for Agile Software Development

    In February 2001, 17 software developers 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, Stephen J. Mellor, Ken Schwaber, Jeff Sutherland, and Dave Thomas met at the Snowbird, Utah resort, to discuss lightweight development methods. They published the Manifesto for Agile Software Developmentref name="Agile Manifesto"/ to define the approach now known as agile software development. Some of the manifesto's authors formed the Agile Alliance, a nonprofit organization that promotes software development according to the manifesto's principles. The Manifesto revolutioned the software development practices and marked a new direction in product delivery.

    Values

  3. values
  4. The Agile Manifesto reads, in its entirety, as follows:ref name="Agile Manifesto"/

    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.
    div align="left"That is, while there is value in the items on the right, we value the items on the left more./div

    Principles

    Twelve principles underline the Agile Manifesto include:

    • Customer satisfaction by rapid delivery of useful software
    • Welcome changing requirements, even late in development
    • Working software is delivered frequently (weeks rather than months)
    • Working software is the principal measure of progress
    • Sustainable development, able to maintain a constant pace
    • Close, daily co-operation 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

    Importance


    PMI-ACP Exam Outline Reference


    Body


    History


    Current practice


    See also


    Sources & Reference


    External Links

    Agile Manifesto for Software Development


last edited by: Stelian ROMAN on Apr 5, 2019 7:31 AM login/register to edit this page


ADVERTISEMENTS

"When one door closes another door opens; but we often look so long and so regretfully upon the closed door that we do not see the ones which open for us."

- Alexander Graham Bell

ADVERTISEMENT

Sponsors

Vendor Events

See all Vendor Events