Scrum Master Interview Questions India 2026: Agile Ceremonies, Team Facilitation, and CSM Certification

Scrum framework:

1. Three Scrum roles: - Product Owner (PO): owns the Product Backlog; defines what to build and in what priority order; represents the business and user needs to the development team; the single voice of the customer. - Scrum Master (SM): servant-leader for the Scrum Team; facilitates Scrum events; coaches the team on Scrum values and practices; removes impediments; protects the team from external interruptions; ensures the team can be self-organising. - Development Team (Devs): the engineers (and designers, QA, etc.) who build the product; self-organising (no tech lead or manager assigns tasks within the team); cross-functional (the team has all the skills needed to deliver a potentially shippable increment).

2. Five Scrum events: - Sprint: a time-boxed iteration (typically 2 weeks; can be 1-4 weeks); fixed length and never shortened or extended. - Sprint Planning: the team selects items from the Product Backlog for the Sprint; creates the Sprint Backlog (the plan for the sprint); defines the Sprint Goal (the single objective for the sprint). - Daily Scrum: 15-minute daily event for the Development Team (not for the PO or SM to report to); each dev answers: what did I do yesterday toward the Sprint Goal? What will I do today? Are there any impediments? - Sprint Review: the team demos completed work to stakeholders; the PO reviews the Sprint and updates the Product Backlog based on feedback. - Sprint Retrospective: the team reflects on how they worked (process, not product); identifies improvements; commits to 1-2 specific improvements for the next sprint.

3. Scrum artifacts: - Product Backlog: an ordered list of everything that might be needed in the product; owned by the PO; never complete; always evolving. - Sprint Backlog: the set of Product Backlog items selected for the Sprint plus the plan for delivering them. - Increment: the sum of all Product Backlog items completed during the Sprint, integrated with all previous increments; must meet the Definition of Done.

Scrum Master interview scenarios:

1. What does a Scrum Master do day-to-day? A Scrum Master's week: Monday: attend Daily Scrum; facilitate Sprint Planning if it is the first day of the sprint. Tuesday-Thursday: attend Daily Scrum; remove impediments identified by the team; 1:1s with team members to understand blockers; coordinate with external dependencies (other teams, the platform team, DevOps); facilitate backlog refinement if scheduled. Friday: attend Daily Scrum; facilitate Sprint Review and Sprint Retrospective at sprint end.

2. Handling a team that does not do retrospectives: If the team says retrospectives are a waste of time: (1) Understand why: are the retrospectives too long? Are action items from previous retros not followed up on? Is the same format boring? (2) Make retrospectives valuable: change the format (use liberating structures: Mad/Sad/Glad, DAKI, Start/Stop/Continue, 5 Whys); shorten to 30-45 minutes; track and immediately act on action items; celebrate when a retro improvement had a measurable impact. (3) Start small: even a 15-minute informal conversation at the end of the sprint is better than skipping.

3. Handling a Product Owner who is unavailable or disconnected: A PO who attends Sprint Planning but never answers questions during the sprint creates ambiguity and rework. As SM: (1) Make the cost of unavailability visible (track the number of decisions deferred because the PO was unavailable; stories that had to be re-worked due to late clarification). (2) Coach the PO on their responsibilities under Scrum. (3) Establish a reliable availability contract (e.g., the PO will respond to questions within 2 hours during business hours). (4) Escalate to the PO's manager if the pattern does not change after coaching.

4. Handling a team that skips the Daily Scrum: A Daily Scrum that is not happening means the team is not synchronising daily. Options: (1) Investigate why: is it too early? Is it too long? Is it not useful for the team? (2) Restructure: move the time; shorten to 10 minutes; try a walking standup or a virtual standup tool. (3) Coach: explain the value (the Daily Scrum is for the team to inspect their progress toward the Sprint Goal, not a status meeting for the SM or PO).

Scrum Master clarity:

1. Scrum Master vs Project Manager: Project Manager: owns the project plan; assigns tasks to individuals; monitors individual performance; reports status to senior management; manages the budget and timeline contractually. Scrum Master: does not own the project; does not assign tasks (the self-organising team does); does not manage people's performance (that is the EM's responsibility); facilitates; coaches; removes impediments. The Scrum Master serves the team, not the other way around.

2. Common Scrum misconceptions: - 'The Scrum Master must have technical knowledge': a SM does not need to be a coder, but technical context helps to identify and remove technical impediments. For software teams, a SM with some technical background is more effective. - 'The Daily Scrum is a status report to the Scrum Master': the Daily Scrum is for the Development Team to synchronise and plan the next 24 hours. The SM facilitates but does not drive. - 'Stories not completed in a Sprint are failed Sprints': incomplete stories are moved back to the Product Backlog; the Sprint is not a failure if the Sprint Goal was met. - 'Velocity must increase every sprint': velocity is a forecasting tool, not a performance metric. Pushing for higher velocity every sprint leads to quality problems and burnout. - 'The Scrum Master decides what goes into the Sprint': the Development Team decides how much work they can take on; the PO decides the priority.

3. Scaling Scrum: For large programs with multiple Scrum teams: SAFe (Scaled Agile Framework): the most commonly used scaling framework in Indian enterprises; adds Program Increments (PI Planning, 8-12 week planning cycles), Agile Release Trains (groups of 5-12 Scrum teams). LeSS (Large-Scale Scrum): simpler; extends the Scrum framework with minimal additional roles and events.

CSM and Scrum Master career path:

1. CSM (Certified Scrum Master) certification: The CSM is offered by Scrum Alliance. Requirements: attend a 2-day in-person or online CSM training course from a Certified Scrum Trainer (CST); pass the online CSM assessment (50 questions, 60 minutes, 74% passing score; open book). The training is mandatory before taking the assessment. Cost: Rs 15,000-40,000 for training + exam (varies by trainer and format).

2. PSM I (Professional Scrum Master I): Offered by Scrum.org. No mandatory training; self-study + assessment. 80 questions, 60 minutes, 85% passing score (harder than CSM). Cost: approximately Rs 4,500 for the assessment. The PSM I is considered more technically rigorous than the CSM because there is no training to guide you; you must understand Scrum deeply to pass. Many experienced Scrum practitioners prefer PSM I for its credibility.

3. Scrum Master career and salary in India: Junior Scrum Master (0-2 years, CSM or PSM I, IT services company): 8-18 LPA. Scrum Master (2-4 years, leading 1-2 teams, Agile coaching): 18-35 LPA. Senior Scrum Master / Agile Coach (5+ years, leading programmes, coaching multiple teams, SAFe certifications): 30-70 LPA. Companies with strong SM/Agile coach demand: TCS, Infosys, Wipro, Accenture, Capgemini (large enterprise Agile transformation programmes), Flipkart, Myntra, and large BFSI companies running SAFe programmes.

4. Preparing for Scrum Master interviews: Read: Scrum Guide (scrumguides.org, free) — the primary source of truth for all things Scrum. Prepare STAR stories for: a time you removed a significant impediment, a time you coached a team through a difficult retrospective, a time you handled a conflict between the PO and the development team, and a time you helped a non-Agile stakeholder understand the Scrum process. Practice explaining Scrum to a non-practitioner: interviews often include role-play where you explain Scrum to a 'new team member' or a 'sceptical executive'.