Handbook
Agile (umbrella)
**Agile** is a set of **values and principles** for software development, not a single process. The [**Manifesto for Agile Software Development**](https://agilemanifesto.org/) (2001) prioritizes:
Agile (umbrella)
What it is
Agile is a set of values and principles for software development, not a single process. The Manifesto for Agile Software Development (2001) prioritizes:
- 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 Twelve Principles behind the manifesto expand on delivery, sustainability, and technical excellence.
Scrum, Kanban, and XP are compatible frameworks/practices that operationalize Agile ideas in different ways. Teams often blend them (e.g. Scrum cadence + XP engineering practices + Kanban flow metrics).
Process diagram (handbook)
Values and principles span concrete frameworks — methodologies-agile.html shows this alongside deeper prose.
Authoritative sources (external)
| Resource | Executive summary (why it’s linked here) |
|---|---|
| Agile Manifesto | Original four values (2001)—defines “Agile” before you choose Scrum, Kanban, or phased delivery. |
| Agile Alliance | Nonprofit hub for articles, glossary, community—neutral background for vocabulary shared with this blueprint. |
| Scrum.org — What is Scrum? | One framework often used under Agile values—helps readers who picked Scrum as their cadence. |
How this blueprint relates
Software development lifecycle (SDLC) is methodology-neutral at the phase level: you can run Phases A–F with Scrum Sprints, Kanban flow, or phased gates. The blueprint does not require Agile certification or a specific tool.
Choosing a primary rhythm:
| If you need… | Often start with… |
|---|---|
| Fixed iterations, stakeholder demos every few weeks | Scrum |
| Continuous flow, variable intake | Kanban |
| Strong engineering discipline | XP practices + either cadence |
| Formal gates and baselines | Phased / hybrid |
Roles: blending frameworks still means naming who holds each archetype—see Roles, archetypes & methodology titles (per-archetype detail + Methodology roll-up).
Ceremonies: pick intent types from Ceremony foundation (methodology-neutral), use Methodology bridge — foundation intents ↔ named ceremonies to align vocabulary across frameworks, then map your blend with the forks in Ceremonies — blueprint package.
Agentic SDLC
See Agentic SDLC for how AI-assisted development intersects Agile values (feedback, working software, sustainable pace) without replacing human judgment.
Further reading
- Agile Alliance — Subway map to Agile practices — Visual map of practices; orientation only, not a workflow mandate.
- Deep dives: Scrum, Kanban, XP, Phased delivery
Canonical source
Edit https://github.com/autowww/blueprints/blob/main/sdlc/methodologies/agile.md first; regenerate with docs/build-handbook.py.