12 agile principles

Principle 6:Face to face contact

Face to face contact is the best way to communicate. It ties into collocation as well as open and honest communication across the team dynamic.

Principle 7 :Working Software.

Focus is on a usable increment that works, and not spending a lot of time on a software that doesn't work. The aim is a Working Software.

Principle 9 :Continues Attention.

In Agile, the entire team looks for ways to improve quality, the design, and the overall process on regular basis. The aim is Continues Attention.

At Principle 12 Regular Reflection.

In Agile, the team should have a constant focus on looking back to move foreword. The aims is have Regular Reflection.

Principle 8 sustainable pace

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

Principle 4 team work daily

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

Principle 9 continues attention

Continuous attention to technical excellence and good design enhances agility.

Principle 3 deliver working software

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

Principle 1: customer satisfaction

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

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 3 Frequent Delivery

The goal is to produce something usable early and often. Frequent Delivery is about producing a usable increment in a short time span that the customer finds valuable.

Principle 6 face to face

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Principle 11:Self-Organization.

The team decides for itself what it can and cannot do, and it works together on solutions. The aim here is to have Self-Organization.

Welcome Principle 2 to Welcome Change.

This allows for some flexibility in the design rather preplan and go through formal change control system every time there is an update to the scope of work. The aim is to Welcome Change.

Principle 2 welcome change

Welcome changing requirements, even late in development. Agile processes harness change for the customer's advantage.

Principle 7 working software

Working software is the primary measure of progress.

Principle 10 Simple,

You need to keep it Simple, no need to add extra features if they are not necessary.

o The 12 principles of the Agile Manifesto

are the guiding force for all agile methodologies.

Principle 5 motivated individuals

iteration if possible. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

Principle 1 customer satisfaction

o All Agile methodologies are looking for ways to bring value to the customer on regular basis by communication and adaption. Customer satisfaction is the aim!

Principle 4 :Collocate

o It is about having collocated teams, even you are managing remote or virtual teams, the best practice is to Collocate them for at least one iteration if possible.

Principle 8 Sustainable Pace.

o Try to achieve a 40-hour work week and no overtime is possible. The aim to have a Sustainable Pace.

Principle 12 regular reflection

the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.