Certified Scrum Master (CSM)
The most widely held Scrum certification — validates foundational knowledge of the Scrum framework and is commonly required for Scrum Master and Agile roles.
The Certified ScrumMaster (CSM) credential, awarded by Scrum Alliance, is the most recognized entry-level Scrum certification. It demonstrates knowledge of the Scrum framework — roles, events, artifacts, and values — and is commonly listed as a preferred or required qualification for Scrum Master, Agile Coach, and project manager roles at organizations that run Scrum. The CSM is earned by attending a two-day in-person or live online course taught by a Certified Scrum Trainer (CST), followed by a 50-question online exam. The Professional Scrum Master (PSM I) from Scrum.org is an alternative credential that requires no training and is respected as more rigorous by many practitioners.
Typical time to job-readiness: ~2 weeks.
Learning Certified Scrum Master (CSM)
Beginner
Read the Scrum Guide (scrumguides.org) — it's 13 pages and the authoritative definition of Scrum. Understand the three roles (Product Owner, Scrum Master, Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Retrospective), and three artifacts (Product Backlog, Sprint Backlog, Increment). This is everything the CSM exam covers.
Intermediate
For the CSM: register for a two-day course with a Scrum Alliance Certified Scrum Trainer — the course is required and includes the exam attempt. For PSM I (Scrum.org): no course required, just pass the 80-question exam with 85%+ in 60 minutes. Many practitioners prefer PSM I because it can be earned without the training fee and is considered harder.
Advanced
The CSM/PSM I is a starting point. Advanced Scrum credentials — A-CSM, CSP-SM (Scrum Alliance) or PSM II/III (Scrum.org) — require demonstrated facilitation experience and deeper coaching competency. SAFe certification is the path for scaling Agile across large organizations. Real Scrum Master effectiveness is measured by team outcomes, not certifications.
Key concepts
- Scrum roles: Product Owner (what to build), Scrum Master (how to work), Developers (build it)
- Sprint: time-boxed iteration of 1-4 weeks; the team commits to a Sprint Goal at planning
- Five events: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective, and the Sprint itself
- Three artifacts: Product Backlog (all work), Sprint Backlog (work in current sprint), Increment (done product)
- Definition of Done: the shared standard for what 'complete' means — prevents technical debt accumulation
- The Scrum Master serves the team, not manages it — facilitates and removes impediments rather than directing
Common interview topics
- Explain the three Scrum roles and what each is responsible for
- How does a Sprint Retrospective differ from a Sprint Review
- How would you handle a team member who consistently misses their Sprint commitments
- What is the Scrum Master's role when the team has a conflict with stakeholders
- How do you measure whether Scrum is working well for a team