El AGILE MANIFESTO (en español: Manifiesto para el desarrollo ágil de software) fue creado en 2001 y define una metodología de trabajo que puede mejorar los resultados en la construcción de software, principalmente el que se desarrolla en modo colaboracional.

Domino Internet ha firmado el manifiesto (número de validación: 218972865564478334) y a partir de ahora tendremos presente dicha metodología en los desarrollos web en los que usemos código abierto (open source).

Así mismo, nos comprometemos a animar a que otros profesionales lo conozcan y lo apoyen.

Estos son sus 4 puntos principales y sus 12 principios (mantenemos el idioma original para no alterar su significado):

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


The 12 Principles behind the Agile Manifesto

  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.

La Wikipedia tiene aquí una página en español con información muy interesante acerca de esta metodología.