Página
Topic 1.2 - Agile Manifesto
The Agile manifesto emerged on February 17, 2001, when seventeen critics of software development met and coined the term "Agile Methodology" to define the methods that were emerging as an alternative to formal methodologies.
The Agile manifesto consists of 12 principles associated to 4 aspects or pillars.
Aspects or Pillars of the Manifesto
● Individuals and their interaction, over processes and tools
● Working software, over the detailed documentation
● Customer collaboration, over contract negotiation
● Responding to change, over following a plan
Principles Behind the Agile Manifesto
The highest priority is to satisfy the customer through early and continuous delivery of useful software. Welcome changing to requirements,
including late ones.
Frequently release a running software, from a couple of weeks to a couple of months, with preference for shorter periods.
Business leaders and developers should work together daily during the project.
Build projects around motivated individuals. Provide the environment and support they need, and trust that they will get the job done.
Direct conversation is the most efficient and effective method of transmitting information, both to and within the team.
Principles
A working software is the primary measure of progress. Agile processes promote sustainable development.
Continuous attention to technical excellence and good design enhances agility.
Simplicity--the art of maximizing the amount of work not done--is essential.
The best architectures requirements and designs emerge from self-organizing teams.
At regular intervals the team reflects about how to become more effective, then tunes and adjusts its behavior accordingly.
Última modificación: viernes, 20 de agosto de 2021, 05:51