Agile is the umbrella name for a family of methods built around a single bet: software is too unpredictable to plan in detail up front, so deliver in small slices, listen to what comes back, and adjust constantly.
This page covers the background. If you already know all of this, skim to How East Agile Tracker maps to agile.
The Agile Manifesto
Section titled “The Agile Manifesto”In February 2001, seventeen software practitioners — Kent Beck, Martin Fowler, Robert Martin, Ron Jeffries, and others — met at a ski lodge in Utah and wrote down what they had in common. They called it the Agile Manifesto. It is four lines:
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.
That’s it. A page of preamble, twelve supporting principles, and the four lines above. It is the most influential document in modern software practice.
The twelve principles
Section titled “The twelve principles”Behind the four values, the manifesto’s twelve principles spell out what “agile” actually looks like day to day:
- The highest priority is satisfying the customer through early and continuous delivery of valuable software.
- Welcome changing requirements, even late. Agile processes harness change for the customer’s competitive advantage.
- Deliver working software frequently — weeks rather than months.
- Business people and developers must work together daily.
- Build projects around motivated individuals. Give them what they need and trust them to get the job done.
- The most efficient way to convey information is face-to-face conversation.
- Working software is the primary measure of progress.
- Agile processes promote sustainable development — a constant pace, indefinitely.
- Continuous attention to technical excellence and good design enhances agility.
- Simplicity — the art of maximizing the amount of work not done — is essential.
- The best architectures, requirements, and designs emerge from self-organizing teams.
- The team regularly reflects on how to become more effective, then tunes and adjusts.
The family of methods
Section titled “The family of methods”“Agile” is an umbrella. Under it sit several distinct methodologies:
- eXtreme Programming (XP) — The most demanding of the family. Pair programming, TDD, continuous integration, on-site customer, small releases. See our XP page.
- Scrum — Time-boxed iterations called sprints, daily standups, named roles (Product Owner, Scrum Master). Lighter on engineering practices than XP.
- Kanban — Visualize the workflow, limit work-in-progress, optimize flow. No time boxes; pull instead of push.
- Lean — Borrowed from Toyota’s manufacturing system: eliminate waste, optimize the whole, deliver fast, build quality in.
These methods overlap and combine. Most working teams cherry-pick from all four. East Agile Tracker is opinionated toward XP — see eXtreme Programming — but most of what it offers works for any agile flavor.
What agile is not
Section titled “What agile is not”A few persistent misconceptions worth naming:
- Agile is not “no planning.” Plans are smaller and shorter, but planning is constant.
- Agile is not “no documentation.” Write what’s needed. The manifesto says working software is more valuable than comprehensive documentation — not that documentation is bad.
- Agile is not Scrum. Scrum is one agile method. There are several.
- Agile is not a tool. No tool makes you agile. Agile is a way of working. Tools (including this one) help; they don’t substitute.
How East Agile Tracker maps to agile
Section titled “How East Agile Tracker maps to agile”East Agile Tracker is designed around the principles above. Here’s the correspondence:
| Principle | How the tracker supports it |
|---|---|
| Continuous delivery | Iterations of 1–4 weeks; velocity-based auto-planning; releases as first-class story type. |
| Welcome change | Reorder the backlog any time; stories move across iterations freely; no “iteration lock.” |
| Working software as the measure | Velocity counts accepted points by default — only delivered, working work counts. |
| Sustainable pace | Velocity isn’t a target; it’s an observation. The system plans the next iteration with what you actually do. |
| Reflection | Per-iteration analytics: burndown, rejection rate, cycle time, projections. |
| Self-organizing teams | Roles are intentionally minimal: owner / member / viewer. The team decides. |
| Simplicity | The detail panel is one screen. The board fits on one page. We resist features that distract from shipping. |
Agile in 2026 — and agents
Section titled “Agile in 2026 — and agents”The manifesto was written in 2001. Since then, software development has gained a new kind of participant: AI agents.
We think agents belong on the agile team — as named participants, with their own roles, doing real work alongside humans. The principles still hold. Individuals and interactions now includes agent participants. Self-organizing teams now includes deciding which agents to bring in and what they’re allowed to do. Reflection now includes looking at agent contributions in the activity log and tuning what they’re working on.
East Agile Tracker is built to make this practical. Every story can be owned by a human or an agent. Every audit log entry attributes the real actor. Every action an agent takes is visible, reviewable, and revocable.
Further reading
Section titled “Further reading”- The Agile Manifesto — The original.
- eXtreme Programming — Our page on XP in practice.
- Operating Instructions — How to use the tracker.
Built by East Agile.