Table 1 Agile Principles as outlined from an article by Laurie Williams[5]

Principle 1

The highest priority is to satisfy the customer through early and continuous delivery of valuable software.

Principle 2

Changing requirements are welcome at the start of each iteration, even late in development; agile processes harness change for the customer's competitive advantage.

Principle 4

Business people and developers must work together daily throughout the project.

Principle 5

Projects should be built around empowered, motivated individuals with a shared vision of success; give them the environment and support their needs, clear their external obstacles, and trust them to get the job done.

Principle 6

The most efficient method for conveying information to and within a development team is through synchronous communication; important decisions are documented so that they are not forgotten.

Principle 7

Valuable, high-quality software is the primary measure of progress at the end of a short time boxed iteration.

Principle 8

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

Principle 9

Continuous attention to technical excellence and good design enhances agility and makes the product valuable through its usability and functionality.

Principle 10

Simplicity—the art of maximizing the amount of work not done—is essential.

Principle 11

The best architecture, requirements, and designs emerge from self-organizing teams guided by a vision for a product release.

Principle 12

For each iteration, the team should candidly reflect on the success of the project, its feedback, and how it could be more effective, then tune and adjust its plans and behavior accordingly.