Skip to content
BENIBIX Learn

Agile Manifesto

Business📋 Agile DeliveryAgile

Also known as Manifesto for Agile Software Development

A short list from 2001 with four values and twelve principles. Agile ways of working grow from it.

Think of it like

It is like the rules on a classroom wall. Four short lines say what the class cares about most.

Example

A team in Berlin argues about writing a 60-page spec first. They recall the second value, working software over documents. So they build a small test version instead.

Why it matters

Scrum, Kanban teams and Extreme Programming all point back to it. It is the shortest way to see what agile is for.

Definition

The Agile Manifesto is a short text about how to build software. Seventeen people wrote it in February 2001, at a ski lodge in Utah. It holds four values and twelve principles. Each value puts one thing over another, like working software over long documents. The things on the right still matter, just less than the things on the left.
The four values. The words on the left matter more, but the words on the right still count.

Common mistake

Reading over as instead of. The manifesto says plans and documents still have value, just less.

Key takeaways

  1. 1
    Four values. Each one puts people and results first.
  2. 2
    Twelve principles. Plain rules, like ship working software often.
  3. 3
    Left over right. The right side still has some value.

Learn it properly