Agile
Agile is the family of iterative delivery approaches — Scrum, Kanban, XP — built on the 2001 Agile Manifesto: deliver working software in short cycles, welcome changing requirements, and measure progress by running product rather than documents.
Agile is not a process
The Manifesto is four value pairs and twelve principles — it prescribes no ceremonies, roles, or sprints. Those come from frameworks: Scrum adds roles and fixed iterations, Kanban adds flow limits, XP adds engineering practices like pair programming and TDD. “Doing Scrum” is not the same as “being agile”; the test is whether the team can change direction cheaply when learning arrives.
Agile shines where requirements are discovered by shipping — new products, evolving integrations. Where requirements are fixed and change is expensive (regulated deliverables, hardware-coupled systems), a staged or hybrid waterfall approach can be the honest choice. Our agile-vs-waterfall guide covers the trade-off with real selection criteria.
Frequently Asked Questions
What is agile methodology in simple terms?
Agile means building software in short iterations — typically two-week cycles — shipping a working slice each time and adjusting plans based on feedback, instead of defining everything upfront and delivering once at the end. It is a set of values implemented by frameworks like Scrum and Kanban.
Is Scrum the same as agile?
No — Scrum is one framework that implements agile values (sprints, roles, ceremonies). Agile is the broader philosophy from the 2001 Manifesto; Kanban, XP, and Lean are other agile approaches. All Scrum is agile, but not all agile is Scrum.
Related Standards
- •Agile Manifesto (2001) — values and principles
- •ISO/IEC/IEEE 12207 — software lifecycle processes (framework-agnostic)
Further Reading
Products & Services
Need help with this?
We consult and build across all of these domains — tell us what you are working on.
