Overview

This article presents a comprehensive interview framework created for evaluating ScrumMaster candidates. The author notes that "a well versed, seasoned ScrumMaster would intuitively know the answer to most of the questions," though feedback on the approach is welcomed.

Scrum Master Interview Questions

Experience – General

The interview begins with introductions and covers foundational Agile concepts:

  • Definition of Agile and a concise elevator pitch
  • Distinction between Agile and Scrum frameworks
  • Gaps in Scrum and complementary development practices
  • Value proposition of daily standups and techniques for improvement
  • Sprint planning approaches when requirements aren't finalized
  • Scrum of Scrums concept and benefits
  • Key characteristics and roles of ScrumMasters

Prioritization and User Story Techniques:

Candidates should demonstrate knowledge of multiple prioritization methods including MoSCoW, Noriaki Kano's technique, numerical prioritization, relative weighting, theme screening, and Karl Wieger's benefit scale. User story creation frameworks like Bill Wake's INVEST and Ron Jeffries' 3 C's are also covered.

Additional topics include why estimation focuses on size rather than duration, professional development habits, and current reading materials.

Experience – Agile Specific

This section explores practical experience:

  • Describing work "without using Agile buzzwords" to demonstrate value-add
  • Organizational transformation roles
  • Challenges faced and solutions implemented
  • Significant mistakes and lessons learned
  • Team process maturation examples
  • Enterprise-scale product ownership approaches
  • Complementary development techniques

Exercises

Candidates analyze burndown charts, outline retrospectives, create story cards, address waterfall regression scenarios, and demonstrate theme-to-task breakdown hierarchies.

Mock Demonstrations

Three facilitated exercises assess practical skills:

Sprint Planning: Candidates facilitate planning for a "parking lot snow removal" scenario, demonstrating requirement breakdown, estimation, and stakeholder management.

Daily Scrum: Facilitating a standup addressing typical blockers and team dynamics.

Sprint Retrospective: Managing discussion around tool unavailability, scope creep, team absences, and communication interruptions while generating actionable improvements.

The author invites readers to suggest additional interview questions in comments.