"Agile and Scrum" is one of the most searched phrases in project management — and one of the most misunderstood. People use the terms interchangeably when they should not. Here is the clear distinction and why it matters for how you work.
The One-Line Answer
Agile is a mindset. Scrum is a framework. Agile describes a set of values and principles for delivering complex work iteratively. Scrum is a specific framework that implements Agile principles through defined roles, events, and artefacts. You can be Agile without using Scrum. Every team using Scrum should be Agile — but many aren't, because they follow Scrum's ceremonies without the underlying values.
The Agile Manifesto (The Foundation)
Agile was defined in February 2001 by 17 software practitioners who signed the Agile Manifesto. It contains four values and twelve principles — no roles, no ceremonies, no tools. It is a philosophy, not a process. Key values:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
Scrum: One Way to Be Agile
Scrum is a framework for implementing Agile values in practice. It defines three roles (Scrum Master, Product Owner, Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), and three artefacts (Product Backlog, Sprint Backlog, Increment). Scrum was developed by Ken Schwaber and Jeff Sutherland and first described in 1995.
Agile vs Scrum vs Kanban: The Comparison
| Factor | Agile | Scrum | Kanban |
|---|---|---|---|
| What it is | Mindset / philosophy | Framework (subset of Agile) | Method (subset of Agile) |
| Fixed cadence | No | Yes — sprints | No — continuous flow |
| Defined roles | No | Yes — SM, PO, Dev | No |
| Prescribed events | No | Yes — 5 events | No |
| Best for | Guiding any delivery approach | Product development, software delivery | Operations, support, continuous work |
Can You Be Agile Without Scrum?
Absolutely. Kanban teams are Agile. XP teams are Agile. Teams running continuous deployment without sprint ceremonies can be deeply Agile. What matters is whether the team is living the Agile values — inspecting and adapting, delivering working value, responding to change, collaborating with customers — not whether they hold a specific ceremony on a specific day.
Which Should Your Team Use?
- Use Scrum if your work is creative and complex (software, product), you benefit from regular cadenced delivery, and your stakeholders can attend sprint reviews for feedback
- Use Kanban if your work is continuous and unpredictable (support, operations, maintenance), or if Scrum's sprint boundaries don't fit your delivery model
- Use SAFe or LeSS if you need to coordinate multiple Scrum teams on related products
What to Certify In
There is no "Agile certification" as such — because Agile is a mindset, not a framework. Certifications test framework knowledge: Scrum (CREA-SM, CSM, PSM I), Kanban (PKI, KMP), SAFe (SSM, RTE), Lean (various). CREA-SM is the broadest entry-level certification — covering Scrum as the foundation plus all major scaling frameworks, enterprise tooling, and Agile coaching models.