EXIN Agile Scrum Master study guide
EXIN Agile Scrum Master · Work through your exam, one topic at a time.
The EXIN Agile Scrum Master (ASM) credential is a vendor-neutral certification offered by EXIN, an independent certification body. It is aimed at Scrum Masters, aspiring Scrum Masters, project managers moving into Agile delivery, team leads and consultants who facilitate Scrum teams and want to demonstrate that they can apply Scrum in practice rather than merely recite definitions. The EXIN Agile Scrum Master study guide has 5 sections and about 2,495 words.
01Agile and Scrum Fundamentals: Empiricism, the Manifesto and Fitness for Purpose
The fundamentals domain checks whether you understand why Scrum is shaped the way it is, not just what its parts are called. Questions probe the Agile Manifesto values and principles, empirical process control, the five Scrum values and - most often - whether Scrum is the right fit for a given piece of work.
521 words, about 3 min02Scrum Roles and Responsibilities: Product Owner, Scrum Master and Developers
This domain tests whether you can separate accountability from job title. Expect scenario questions where someone is behaving like a project manager, a proxy Product Owner or a task allocator, and you must name the correct accountability and the correct intervention.
498 words, about 2 min03Scrum Artefacts and Events: Commitments, Timeboxes and Purpose
This domain tests precise knowledge of the three artefacts, the three commitments attached to them, and the five events - what each is for, who attends, and how long it may run. Vague answers such as "the review is where we demo" cost marks because they miss the inspection-and-adaptation purpose.
511 words, about 3 min04Facilitation, Coaching and Servant Leadership in the Scrum Master Role
This domain tests behaviour, not definitions. Questions present a team situation - a silent retrospective, a dominating stakeholder, a recurring impediment - and ask what the Scrum Master does.
494 words, about 2 min05Scaling, Adoption and Continuous Improvement in the Agile Organisation
This domain tests whether you can reason about Scrum beyond a single team: how frameworks coordinate multiple teams, what makes adoption succeed or stall, and how improvement is evidenced rather than asserted. Scrum itself says nothing about scaling; scaling frameworks add coordination structure on top of it.
471 words, about 2 min