Skip to content

Instantly share code, notes, and snippets.

@ojas
Last active June 30, 2023 12:35
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ojas/9675c0a62c0234a5156dedab86c7a52e to your computer and use it in GitHub Desktop.
Save ojas/9675c0a62c0234a5156dedab86c7a52e to your computer and use it in GitHub Desktop.

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

Principles behind the Agile Manifesto

We follow these principles:

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhances agility.
  10. Simplicity--the art of maximizing the amount of work not done--is essential.
  11. The best architectures, requirements, and designs emerge from self-organizing teams.
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Signatories

  • 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 Sutherland
  • Dave Thomas

~ https://agilemanifesto.org/

Bonus: As Javascript

`Individuals and interactions > processes and tools
----------------------------

Working software > comprehensive documentation
----------------

Customer collaboration > contract negotiation
----------------------

Responding to change > following a plan
--------------------
`
    .split('\n')
    .filter(l => l.length && l[0] !== '-')
    .map(l => l.replace(' > ', ' over '))
    .forEach(l => {
  const parts = l.split(' over ');
  console.log(parts[0].toUpperCase());
  console.log(' '.repeat(parts[0].length-2) + 'over');
  console.log(' '.repeat(parts[0].length) + '"' + parts[1] + '"');
});

INDIVIDUALS AND INTERACTIONS
                          over
                            "processes and tools"
WORKING SOFTWARE
              over
                "comprehensive documentation"
CUSTOMER COLLABORATION
                    over
                      "contract negotiation"
RESPONDING TO CHANGE
                  over
                    "following a plan"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment