Agile Manifesto

Manifesto: A written statement declaring publicly the intentions, motives, or views of its issue.

The 4 Agile Manifesto:

• Individuals and Interactions; No need to follow a standard process and tools
• Working Software; No need to wait for comprehensive documentation
• Customer Collaboration; No discussion over the pre-defined scope, contract negotiation.
• Responding to change; No need to wait for change by following a process or plan. The immediate change in place

12 Principles of Agile Manifesto

• Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
• Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
• Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.
• Business people and developers must work together daily throughout the project.
• Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
• The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
• Working software is the primary measure of progress.
• Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
• 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 on how to become more effective, then tunes and adjusts its behavior accordingly.

Reference: Scrum Alliance