Skip to content
BENIBIX Learn

The Agile Manifesto

Level 1 Β· What agile is

What the Agile Manifesto says, who wrote it and when. Its four values and twelve rules. What the line about the right side really means.

Course contentsLesson 1 of 19

After this lesson you can

  • Name the four agile values
  • Explain what the right-hand side means
  • Say what agile is and is not

10 mincovers 2 glossary entries

What the Agile Manifesto says

Agile is a way of working that builds a result in small pieces. It learns from each one. Its start was the Agile Manifesto, a one-page text from February 2001. Seventeen software makers wrote it in three days at a ski lodge in Utah. It holds four values and twelve principles.

Each of the four values puts one thing first. People and how they work together beat steps and tools. Working software beats long papers. Working with the customer beats a fight over the contract. Responding to change beats sticking to a plan.

The line under them matters most. It says the things on the right still have value, but the things on the left have more. So agile does not mean no plan and no papers. It means a plan that can change, and papers that serve the work rather than replace it.

The twelve principles turn the values into habits. Hand over working software often, every few weeks or every few months, and pick the shorter. Welcome changes, even late ones. Let business people and builders work side by side each day. Keep a pace the team can hold for good.

Two more principles are easy to miss. One says working software is the main measure of progress, not reports about it. Another says simplicity, the art of not doing work that does not need doing, is essential. A feature nobody uses is cost with no value.

Agile is not one method. It is the set of values that several methods share. Each method turns them into its own rules, roles and meetings. This course covers the two most used, and a few others. Choosing agile or a fixed plan for a whole project is a separate subject.

The common mistake is treating agile as a set of meetings. A team can hold every meeting and still hand over nothing for six months. The test is the values: does the team ship small pieces, listen and change course?

Each value puts the left side first. The right side is not thrown away.

Worked example

Emma's team stops writing a 90-page spec

Emma's team in Dublin spends 3 months on a 90-page plan for a booking app. When the first screen ships, users say half of it is wrong.

On the next app they build one small part every 2 weeks and show it to 5 users each time. By week 12 they have shipped 6 small pieces, and users asked for 4 changes on the way.

The words for this lesson2

Check yourself

Does agile say a plan has no value at all?

Finished this lesson?

Marking it complete also marks its 2 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.