Introduction to Agile

The underlying spirit of all these frameworks are contained in the agile manifesto and the 12 agile principles.

We are uncovering better ways of developing

software by doing it and helping others do it.

Through this work we have come to value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

That is, while there is value in the items on

the right, we value the items on the left more.

Reference – Agilemanifesto.org

12 Agile Principles

12 Agile Principles

Principle#1 – Satisfy the customer through early and continuous delivery

We follow these principles:

Our highest priority is to satisfy the customer

through early and continuous delivery

of valuable software.

Principle#2 – Welcome changing requirements even late in development

Welcome changing requirements, even late in

development. Agile processes harness change for

the customer’s competitive advantage.

Principle#3 – Deliver working software frequently

Deliver working software frequently, from a

couple of weeks to a couple of months, with a

preference to the shorter timescale.

Principle#4 – Business people and developers working together

Business people and developers must work

together daily throughout the project.

Principle#5 – Build projects around motivated individuals

Build projects around motivated individuals.

Give them the environment and support they need,

and trust them to get the job done.

Principle#6 – Face to face conversation

The most efficient and effective method of

conveying information to and within a development

team is face-to-face conversation.

Principle#7 – Working software

Working software is the primary measure of progress.

Principle#8 – Sustainable development

Agile processes promote sustainable development.

The sponsors, developers, and users should be able

to maintain a constant pace indefinitely.

Principle#9 – Good design

Continuous attention to technical excellence

and good design enhances agility.

Principle#10 – Simplicity

Simplicity–the art of maximizing the amount

of work not done–is essential.

Principle#11 – Self organizing teams

The best architectures, requirements, and designs

emerge from self-organizing teams.

Principle#12 – Team reflections (retrospectives)

At regular intervals, the team reflects on how

to become more effective, then tunes and adjusts

its behavior accordingly.