Skip to content
Tutorials Center
My learning

Topics

Lesson 25 of 50 ยท Agile and Teamwork

Agile Principles and Manifesto

Learn why agile arose, what the four values and twelve principles of the Agile Manifesto say, and which common myths about agile are wrong.

In the 1990s, many software projects followed heavy, plan-driven processes like the waterfall model: gather all requirements, design everything, build, then test at the end. For projects where requirements are well known and rarely change, that can work. But for many business and consumer products the requirements were not well known, and they changed during the long months before anyone saw working software. Projects delivered late, over budget, or perfectly matching a need that had since moved on.

In response, several lightweight approaches appeared, including Extreme Programming, Scrum, Crystal and others. In February 2001, seventeen practitioners met in Utah and wrote down what their methods had in common. The result was the Manifesto for Agile Software Development. "Agile" is not a process or a tool; it is a set of values and principles for working under uncertainty. Specific frameworks, such as Scrum and Kanban, are ways to put those values into practice. This lesson is text and diagrams; the two small JavaScript stand-ins at the end are teaching models, not measurements of real projects.

Why agile arose

The core observation is that software is hard to specify in advance. Customers often cannot say exactly what they want until they see something working, technology surprises you, and the market moves. Seen this way, a long plan is a bet that nothing will change, and the cost of being wrong rises with every month before feedback arrives. (See the cost of change by phase.)

Agile responds by shortening the feedback loop. Instead of one big delivery at the end, the team delivers small, working increments often, gathers feedback from real users, and adjusts the plan. The bet shrinks from "we know exactly what to build" to "we know what to try next."

flowchart LR
    P["Plan a small slice"] --> B["Build it"]
    B --> S["Show working software"]
    S --> F["Get feedback"]
    F --> P

The agile loop: small slices, frequent feedback, constant adjustment.

The four values

The manifesto states four value pairs. Each says "while there is value in the items on the right, we value the items on the left more."

The four values of the Agile Manifesto

Individuals and interactions over processes and tools.
Working software over comprehensive documentation.
Customer collaboration over contract negotiation.
Responding to change over following a plan.

The right-hand items still matter. The left-hand ones matter more.

1 / 2

Here is how to read each pair sensibly:

  • Individuals and interactions over processes and tools. Talented people communicating well beat a perfect process followed by people who do not talk. A tool cannot repair a team that will not communicate. It does not mean "no process."
  • Working software over comprehensive documentation. The measure of progress is software that works, not pages of specification. It does not mean "no documentation"; it means write what people will actually use, and no more.
  • Customer collaboration over contract negotiation. Treat the customer as a partner who learns alongside you, not as an opponent in a contract dispute. It does not mean "no contracts"; it means a contract should not stop you from adapting.
  • Responding to change over following a plan. A plan is useful for thinking, but when facts change, the plan must change. It does not mean "no planning."

The twelve principles

Behind the four values stand twelve principles. In paraphrase, grouped by theme:

Delivering value

  1. Satisfy the customer through early and continuous delivery of valuable software.
  2. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter time.
  3. Working software is the primary measure of progress.

Welcoming change

  1. Welcome changing requirements, even late in development; agile processes harness change for the customer's advantage.
  2. Business people and developers must work together daily throughout the project.

Sustainable teams

  1. Build projects around motivated individuals; give them the environment and support they need, and trust them to get the job done.
  2. The most efficient and effective way to convey information is face-to-face conversation (today that includes video calls).
  3. Agile processes promote sustainable development; sponsors, developers and users should be able to maintain a constant pace indefinitely.
  4. Continuous attention to technical excellence and good design enhances agility.

Simplicity and learning

  1. Simplicity, the art of maximizing the amount of work not done, is essential.
  2. The best architectures, requirements and designs emerge from self-organizing teams.
  3. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior.

Principle 9 is often forgotten. Agile does not mean sloppy code; quick delivery depends on code that stays easy to change, so practices from technical debt and refactoring and test-driven development are central to it. Principle 8 matters too: a team that burns out on constant crunch is not agile.

Common myths

Agile is widely used and widely misunderstood. Some myths worth correcting:

Myth Reality
"Agile means no planning." Agile teams plan continuously, in shorter horizons and with more revision.
"Agile means no documentation." It values documentation that is useful and kept current, over volume.
"Agile means moving fast and cutting corners." Principle 9 asks for technical excellence; sustainable pace beats bursts.
"Agile is just Scrum." Scrum is one framework; Kanban, XP and others are also agile.
"Agile works only for small software teams." Large organizations use it, though scaling takes extra coordination.
"Agile means the team does whatever the customer says." The team negotiates scope with the customer; it welcomes change but also says what it costs.
"Doing the ceremonies makes us agile." Daily meetings and boards without the values are "cargo cult" agile.
"Agile guarantees success." It reduces some risks (building the wrong thing); it does not remove hard problems.

It is also honest to say that agile is not always the right fit. Projects with fixed, well-understood requirements, strict regulatory documentation, or hardware that cannot change cheaply may need more upfront planning, and often use a hybrid. See choosing a process model.

Stand-in: the cost of late feedback

The central claim of agile is that earlier feedback is worth a lot. This stand-in is a small model, not a measurement: it assumes a project of 20 weeks whose customer will want some fraction of the features changed once they see working software, and that changing something already built costs extra the more is built on top. All the numbers are invented to illustrate the shape of the effect.

JS Model: when does feedback arrive?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The exact figures mean nothing; the shape is the lesson: the same share of change costs far more when it is discovered late, which is why agile teams keep the gap between building and learning short.

Stand-in: matching practices to principles

A common exercise is asking, for any practice a team uses, which principle it serves. Here a handful of practices are mapped to principle numbers, and the code reports which principles have no supporting practice. A real team would use this only as a prompt for discussion, not as a score.

JS Which principles does your team support?

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The output surfaces two gaps (welcoming change and sustainable pace), and that is where a real discussion would start: is our backlog really open to change, and do we work at a rate we could keep up for years?

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. What problem was the Agile Manifesto largely a response to?

    Heavy up-front planning with feedback only at the end meant requirements often changed before delivery, so teams sought shorter feedback loops.
  2. 2. How should the manifesto's 'working software over comprehensive documentation' be read?

    The right-hand items still have value; the manifesto says the left-hand ones matter more.
  3. 3. Which is true about agile and Scrum?

    Agile is a set of values and principles. Scrum, Kanban and XP are methods that put them into practice.
  4. 4. Principle 9 asks for continuous attention to what?

    Easy-to-change code is what makes frequent delivery and welcoming change sustainable.
  5. 5. Which statement is a myth?

    Ceremonies without the underlying values are a hollow imitation, sometimes called cargo-cult agile.

Summary

  • Agile arose because software requirements are hard to know up front and change during long projects.
  • The manifesto values individuals and interactions, working software, customer collaboration and responding to change, while still valuing the items on the right.
  • Twelve principles cover early and frequent delivery, welcoming change, sustainable pace, technical excellence, simplicity and regular reflection.
  • The key mechanism is a short feedback loop: build small, show it, learn, adjust.
  • Common myths include "no planning", "no documentation" and "agile equals Scrum".
  • Agile is a good fit for uncertain requirements but not a guarantee, and some projects need more up-front planning.

Next: Scrum in Practice.