In February 2001, 17 software developers gathered in Utah to discuss less cumbersome development methodologies. They published the first Agile Development Methodology manifesto, which told how they had found "better ways to develop software and help others do it." This manifesto includes 12 principles, which are a great contrast to the standards of the Project Management Institute (PMI).
PRINCIPLE 1: Our highest priority is to satisfy the customer through the early and continuous delivery of valuable software.
PRINCIPLE 2: We accept that requirements change, even in late stages of development. Agile processes leverage change to provide competitive advantage to the customer.
PRINCIPLE 3: We deliver functional software frequently, between two weeks and one month,
preferably for periods of time as short as possible.
PRINCIPLE 4: Business leaders and developers work together on a daily basis throughout the project.
PRINCIPLE 5: Projects are developed around motivated individuals. You have to give them the environment and the support they need, and entrust them with the execution of the work.
PRINCIPLE 6: The most efficient and effective method of communicating information to the development team and among its members is face-to-face.
PRINCIPLE 7: Software running is the main measure progress.
PRINCIPLE 8: Agile processes promote sustainable development. Promoters, developers and users must be able to maintain a constant pace indefinitely.
PRINCIPLE 9: Continued attention to technical excellence and good design improves agility.
PRINCIPLE 10: Simplicity, or the art of maximizing the amount of unfulfilled work, is essential.
PRINCIPLE 11: The best architectures, requirements and designs emerge from self-organized teams.
PRINCIPLE 12: At regular intervals the team reflects on how to be more effective then adjust and refine their behavior accordingly.