The distinction between Agile and Scrum is one of the first questions many interviewers ask — and one that many candidates answer poorly, despite knowing the answer in theory. The difference isn't complicated, but explaining it with clarity and confidence under pressure requires more than just memorising a definition.
Agile is a mindset and a set of values for how to approach work: iteratively, collaboratively, with continuous feedback, and with a preference for working outcomes over exhaustive documentation. It was codified in the 2001 Agile Manifesto and its twelve principles, but it exists at the level of philosophy, not procedure. You cannot "do Agile" in the same way you might run a standup — you can only develop the Agile mindset and work to embody its principles.
Scrum is a specific framework for implementing Agile in practice. It provides a set of concrete structures — 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) — within which a team can deliver work iteratively. Scrum doesn't tell you exactly how to do everything; it creates a cadence and a set of accountabilities within which good Agile practice can emerge.
In an interview, the best way to answer this question is with a clear two-part structure: define Agile as the broader philosophy, then position Scrum as one specific framework for operationalising that philosophy. You can add that other frameworks like Kanban and SAFe also operate within the Agile philosophy, which demonstrates broader awareness. The key is clarity and confidence — not length.
Put this into practice with expert coaching
Reading builds awareness. Live coaching builds performance. If you're preparing for Scrum Master interviews, the fastest path to confidence is working through your answers with a practitioner who can give you real feedback.