Scrum vs. Agile: what's the actual difference?
Agile and Scrum are often mentioned in the same breath, but they are not the same thing. Agile is a mindset and philosophy about working adaptively. Scrum is a concrete framework that helps you put that mindset into practice. In this guide we explain the difference clearly, with practical examples and advice on which training fits your situation.
What is Agile?
Agile is a way of thinking and working that originated with the Agile Manifesto (2001). The core idea: deliver value to customers in short cycles, learn continuously and adapt based on new insights. Agile is not a tool or a step-by-step plan, but a set of values and principles.
Those values prioritise individuals over processes, working solutions over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.
- Mindset and philosophy, not a method
- 12 principles from the Agile Manifesto
- Applicable to software, HR, marketing, product and beyond
What is Scrum?
Scrum is the most widely used framework for putting Agile into practice. It defines three roles (Product Owner, Scrum Master, Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective) and three artefacts (Product Backlog, Sprint Backlog, Increment).
Scrum is intentionally lightweight: it describes the rules of the game, but leaves most of the 'how' to your team. That makes it flexible, but also easy to misapply — which is where good training comes in.
- Concrete framework with roles, events and artefacts
- Documented in the Scrum Guide
- Best known from software, but broadly applicable
The difference at a glance
The simplest way to remember it: Agile is the 'why' and 'what', Scrum is one of the ways to fill in the 'how'. You can work Agile without Scrum (e.g. with Kanban or SAFe), but you can't meaningfully do Scrum without the Agile mindset.
Which training fits me?
Want to understand what working Agile means for your team or organisation? Start with our basic Agile training. Already working Agile and looking to step into a Scrum Master or Product Owner role? Choose a targeted certification training. Working in a scaled environment with multiple teams? Our SAFe trainings are built for that.
Agile vs. Scrum compared
| Agile | Scrum | |
|---|---|---|
| Type | Mindset and philosophy | Concrete framework |
| Defined in | Agile Manifesto | Scrum Guide |
| Roles | No prescribed roles | Product Owner, Scrum Master, Developers |
| Cycle | Short iterations (flexible) | Sprints of 1–4 weeks |
| Where used | Across sectors and domains | Product teams, mainly software |
| Combines with | Scrum, Kanban, SAFe, XP | SAFe, LeSS, Nexus |
Frequently asked questions
Is Scrum always Agile?
Yes, Scrum is built on the Agile values and principles. But 'doing' Scrum without the Agile mindset mostly produces rituals without the benefits — that's sometimes called 'mechanical Scrum'.
Is Agile always Scrum?
No. Agile is a mindset; Scrum is one way to live it. Other widely used Agile approaches are Kanban, SAFe, LeSS and XP.
Which certification fits a Scrum Master?
For a Scrum Master role you can choose a PSM or SAFe Scrum Master training. The right fit depends on whether you work in a single team or in a scaled SAFe environment.
Can I work Agile without Scrum?
Absolutely. Many HR, marketing and innovation teams work Agile using Kanban or their own mix. Our basic Agile training shows how.
Ready to take the next step?
Browse our open trainings or schedule a no-strings conversation. We're happy to help you pick the right training for your team.