Scrum Master interview questions
100 real questions with model answers and explanations for Scrum Practitioner candidates.
See a Scrum Master resume example →Practice with flashcards
Spaced repetition · Hunter Pass
Questions
I would explain that the Product Owner is accountable for maximizing product value through effective Product Backlog management, not for supervising daily work.
- I would put one accountability map in Confluence showing the Product Owner owns the Product Goal, backlog ordering, and backlog transparency.
- I would note that the Product Owner may delegate backlog-item writing, but remains accountable for the resulting Product Backlog.
- I would confirm understanding by asking all 7 team members to place three sample decisions under Product Owner, Developers, or Scrum Master.
Why interviewers ask this: The interviewer checks whether you distinguish Product Owner accountability from ticket writing and people management.
I would decline to assign work and help the Developers create their own plan for meeting the Sprint Goal.
- I would tell the manager that Developers are accountable for the Sprint Backlog and decide who does what as work unfolds.
- I would facilitate a 20-minute planning conversation around skills, dependencies, and pairing instead of distributing 6 tickets myself.
- I would consider the onboarding complete when the Developers can update ownership without waiting for Scrum Master approval.
Why interviewers ask this: A strong answer protects Developer self-management and does not turn the Scrum Master into a task dispatcher.
I would show that the Scrum Master is accountable for establishing Scrum and improving the team's effectiveness, not merely scheduling meetings.
- I would create a one-page onboarding plan covering Scrum theory, each event's purpose, and the three accountabilities.
- I would observe one Sprint event and give the team one specific coaching point rather than taking over its decisions.
- I would use a Friday check-in where all 6 members can name one way I helped remove an impediment or improve self-management.
Why interviewers ask this: The interviewer is evaluating whether you understand the Scrum Master's service and coaching accountability.
I would help the Product Owner make the Product Goal visible and connect the ordered Product Backlog to it.
- I would schedule a 45-minute session for the Product Owner to state one measurable future product state, such as reducing checkout abandonment by 10 percent.
- I would add that Product Goal to the top of the Product Backlog page and link the first 10 ordered items to it.
- I would finish when the team can explain why the top 3 items are the next best steps toward that goal.
Why interviewers ask this: This tests the relationship between the Product Backlog artifact and its Product Goal commitment.
I would explain that the Sprint Backlog contains the Sprint Goal, selected Product Backlog items, and the Developers' actionable delivery plan.
- I would ask the whole Scrum Team to draft one Sprint Goal that states the valuable outcome for the 2-week Sprint.
- I would have the Developers break the selected items into enough visible work to start, without requiring a complete day-one task inventory.
- I would check that all 9 members can point to the goal, selected items, and current plan on one board.
Why interviewers ask this: The interviewer checks whether you know the full Sprint Backlog and its Sprint Goal commitment.
I would say those stories are not part of the Increment until they meet the Definition of Done and are usable.
- I would compare each of the 5 stories with the shared checklist and return unmet work to a visible not-done state.
- I would ask the Developers to complete the required tests and integrate the work before counting it in the Increment.
- I would mark onboarding complete when the board and Increment show the same number of items meeting every quality criterion.
Why interviewers ask this: A strong answer connects the Increment artifact to the Definition of Done without weakening quality.
I would restore transparency first because inspection and adaptation are unreliable when the board does not reflect reality.
- I would ask the Developers to update all 7 items before the next Daily Scrum and flag the blocked item visibly.
- I would agree on one board rule: change an item's state when the work state changes, not at the end of the week.
- I would verify completion by matching the board to the team's verbal account for 2 consecutive working days.
Why interviewers ask this: The interviewer is looking for a practical understanding of transparency as the basis for empiricism.
I would help the Developers inspect progress toward the Sprint Goal rather than inspect individual performance.
- I would point them to the Sprint Goal and ask what the API evidence changes in today's plan.
- I would keep the discussion focused on the Sprint Backlog, with the dependency recorded on the affected item.
- I would know the lesson landed when the Developers identify one concrete plan adjustment within the 15-minute event.
Why interviewers ask this: This checks whether inspection is tied to progress and artifacts rather than employee monitoring.
I would support the Developers in adapting the Sprint Backlog while preserving the Sprint Goal.
- I would ask them to update the plan with an available test approach, pairing option, or reordered work within the same day.
- I would involve the Product Owner if the new evidence requires clarifying or renegotiating the selected scope without lowering quality.
- I would use a visible revised plan and confirmation that the Sprint Goal remains achievable as the completion signal.
Why interviewers ask this: The interviewer checks whether adaptation follows evidence and respects the Sprint Goal and Definition of Done.
I would coach the member to raise the evidence now, using courage and openness to protect transparency.
- I would provide a simple risk entry with impact, evidence, affected backlog item, and the time it was raised.
- I would bring the relevant Developers and Product Owner together within one working day to inspect the effect on the Sprint Goal.
- I would consider it resolved when the risk has an owner and a visible decision rather than remaining private until the Review.
Why interviewers ask this: A strong answer turns Scrum values and empiricism into observable onboarding behavior.
I would extend the session enough to create a sound Sprint plan while explaining that Scrum sets an 8-hour maximum only for a one-month Sprint.
- I would reserve up to 4 hours for this team's 2-week Planning as a local working limit, not as a Scrum-mandated number.
- I would publish an agenda covering why the Sprint is valuable, what can be done, and how the work will get done.
- I would close early when the Sprint Goal, selected items, and initial delivery plan are visible and understood by all 7 members.
Why interviewers ask this: The interviewer checks exact Scrum timebox knowledge and whether you scale the working session sensibly for a shorter Sprint.
I would steer Planning through the missing why and how topics before treating the selection as a Sprint plan.
- I would ask the Product Owner to explain the value and ordering behind the 9 candidate items.
- I would guide the whole Scrum Team to define one Sprint Goal, then leave the Developers to create the actionable delivery plan.
- I would finish when the Sprint Backlog shows the goal, selected items, and enough planned work to begin on day one.
Why interviewers ask this: A strong answer covers all three Sprint Planning topics and preserves the Developers' planning authority.
I would help the team express the outcome those tickets create instead of repeating a task list.
- I would ask what user or business change unites tickets 31 to 38, such as letting customers reset passwords without support.
- I would record one concise outcome statement as the Sprint Goal and keep the ticket list as selected backlog items.
- I would test the goal by asking whether the Developers could change one item while still achieving the same outcome.
Why interviewers ask this: The interviewer evaluates whether you understand a Sprint Goal as a coherent objective that provides flexibility.
I would use past velocity only as a local planning signal and let the Developers forecast work around capacity and the Sprint Goal.
- I would show the 3-Sprint range of 24 to 27 points without turning the average into a productivity target.
- I would ask the Developers to account for one holiday and current technical uncertainty before selecting items.
- I would complete Planning with a Developer-owned forecast and Sprint Goal, not a Scrum Master promise of 35 points.
Why interviewers ask this: This tests safe velocity use and the distinction between a forecast and a productivity commitment.
I would explain that the Daily Scrum is a 15-minute event for the Developers, who choose how to inspect progress toward the Sprint Goal.
- I would reserve the same 15-minute time and place every working day to reduce coordination overhead.
- I would ask the Developers to use the Sprint Goal and current Sprint Backlog rather than report status to me.
- I would step back once they can finish in 15 minutes with a concrete plan for the next working day.
Why interviewers ask this: The interviewer checks Daily Scrum ownership, purpose, and exact timebox.
I would redirect the conversation to the Developers and stop acting as status collector or task assigner.
- I would stand beside the board rather than at its head and open with the current Sprint Goal.
- I would ask the Developers what plan adjustment they need, then let them choose speakers and coordinate the work.
- I would count the change successful when all follow-up actions are owned by Developers before the 15-minute timebox ends.
Why interviewers ask this: A strong answer restores the Daily Scrum as a Developer event for self-management.
I would create a longer working session for inspection and adaptation, noting that the official maximum is 4 hours for a one-month Sprint.
- I would reserve up to 2 hours locally for this 2-week Sprint and invite the Product Owner's relevant stakeholders.
- I would structure the session around the Sprint Goal, the usable Increment, current product conditions, and likely Product Backlog changes.
- I would close when feedback and resulting backlog adaptations are recorded, even if the session ends before 2 hours.
Why interviewers ask this: The interviewer checks that a Sprint Review is a collaborative working session, not a rushed demo.
I would clarify that the Sprint Review is not a release gate and a usable Increment may be released before it.
- I would verify the feature meets every Definition of Done criterion and the Product Owner's release decision process.
- I would separate the release record from the Review agenda so stakeholder feedback can still shape future Product Backlog ordering.
- I would consider the misunderstanding fixed when the team can describe release timing without requiring Review approval.
Why interviewers ask this: A strong answer accurately separates Increment usability, release decisions, and the purpose of Sprint Review.
I would give the team enough time to inspect and plan an improvement, while noting the Scrum maximum is 3 hours for a one-month Sprint.
- I would reserve up to 90 minutes locally for this 2-week Sprint and publish a focused agenda before Friday.
- I would cover people, interactions, processes, tools, and the Definition of Done using evidence from the Sprint.
- I would end when the team has selected at least one specific improvement with an owner or clear team ownership.
Why interviewers ask this: This tests exact Retrospective timebox knowledge and focus on actionable improvement.
I would use the final 10 minutes to select one high-value improvement rather than leave with an unranked note pile.
- I would cluster the 18 notes, run a quick vote, and discuss the highest-ranked theme.
- I would write one action with an owner, due point, and completion signal on the Retrospective page.
- I would add the action to the next Sprint Backlog when appropriate and review its result at the next Retrospective.
Why interviewers ask this: The interviewer evaluates whether your facilitation turns reflection into a concrete improvement plan.
Locked questions
- 21
A 6-person team asks whether its weekly 60-minute refinement session is an official Scrum event with a required timebox. How would you answer?
agilesessions - 22
Two days before Planning, a 7-person team has 5 top backlog items with unclear acceptance details, and a new Scrum Master wants to block them with a mandatory Definition of Ready. What would you do?
agilebacklog - 23
A newly formed 8-person team has separate ideas of Done: coding complete, QA approved, or deployed to staging. How would you create a usable Definition of Done before the first Sprint?
agiledeploymentdod - 24
The organization requires every product Increment to pass a security scan, an accessibility check, and an audit-log test. A new 7-person Scrum Team wants to omit accessibility from its Definition of Done to move faster. How would you respond?
agilea11ydod - 25
A department proposes one 14-person Scrum Team split into frontend, backend, and QA subteams, each led by a senior specialist. What structure would you recommend?
agile - 26
A 7-person team's new Jira board has 11 workflow states, including Open, Selected, Ready, In Dev, Dev Done, QA Ready, and QA Done. What basic hygiene would you propose before Monday?
- 27
Three business leads form a Product Owner committee and each changes the order of the same 30-item Product Backlog. Developers receive conflicting priorities before Planning. How would you correct this?
backlogformsagile - 28
On day three of a 2-week Sprint, a 6-person team's Jira board still shows the original task breakdown although the Developers changed their implementation plan yesterday. Who updates it and how?
agile - 29
A 9-person team has three Confluence pages with different Sprint Goal wording 24 hours after Planning. What would you clean up?
agile - 30
Ten minutes before a remote Retrospective for 7 people, the Miro board still contains last Sprint's votes and named sticky notes. What would you do?
agile - 31
On day five of a 10-day Sprint, a 7-person team's burndown has been flat for three days while 6 items remain in progress. What basic interpretation would you offer?
agile - 32
During a 2-week Sprint, an 8-person team's burnup shows 20 completed points but the scope line rose from 24 to 32. How would you explain the chart to the team?
agilescope-management - 33
A Developer on a 6-person team has waited 5 hours for test credentials, but the Jira item still appears normally In Progress. How would you make the blocker visible?
communication - 34
A 7-person team has 9 items in progress on day four and wants a simple Kanban practice to reduce task switching. What would you try?
agile - 35
After three Sprints, a new 8-person team asks whether its velocity of 26 should become a productivity score on the Confluence dashboard. What would you recommend?
agiledelivery-metrics - 36
You are facilitating a 4-hour Sprint Planning for an 8-person team, and the first topic has consumed 90 minutes without a decision. How would you protect the remaining time?
agile - 37
Twenty minutes into a 60-minute refinement with 7 people, a database naming debate is consuming the session although 4 upcoming items still need clarification. What would you do?
databasesessions - 38
In a 45-minute Retrospective for a 6-person team, only two people have spoken after the first 15 minutes. How would you invite the quieter participants?
agile - 39
During a 30-minute Sprint Goal workshop for 8 people, the first two speakers fill 12 minutes while four participants have not contributed. What facilitation move would you use?
agile - 40
A remote Daily Scrum for a 7-person team starts in 10 minutes, and two Developers report that the video link fails while the Jira board is accessible. How would you set up continuity?
agile - 41
For a hybrid Sprint Review with 9 team members, 4 stakeholders are remote and the room has one shared laptop. What setup would you arrange by Thursday's deadline?
agilecommunicationestimation - 42
At the end of a 50-minute refinement, a 6-person team verbally chooses option B for an API contract, but the Miro board still shows three options. What would you record?
api - 43
A 7-person team has 15 minutes to choose one of three Retrospective actions, and all three have supporters. How would you facilitate the decision?
agile - 44
Five minutes into a 60-minute Sprint Review for an 8-person team, attendees start discussing detailed estimates for next month's backlog. How would you reset the session?
agileestimationsessions - 45
A 45-minute workshop for a 6-person team reaches its timebox with two viable monitoring tools and no final choice. What would you do instead of silently extending it?
monitoring - 46
In week one with a 7-person team, you discover blockers are mentioned in chat but nowhere tracked, and the next Sprint starts in four days. What simple impediment log would you create?
agilecommunication - 47
A Developer in a 6-person team finds a failing unit test two hours before the Daily Scrum and asks you to take ownership because you keep the impediment log. What would you do?
agileunitownership - 48
A 7-person team needs a staging account by Wednesday noon, and the service desk lists the requester, team lead, then platform manager as its escalation route. How would you manage it?
escalation - 49
An external test-data request for an 8-person team has had no response for one working day, and testing must start by 10 a.m. tomorrow. When and how would you escalate?
escalationtesting - 50
A firewall blocker for a 9-person team is marked resolved in the impediment log, but no Developer has tested the connection and Planning starts in two hours. What would you do?
communicationnetworking - 51
A 7-person team has carried 5 of 14 selected items into each of its last 3 two-week Sprints. How would you respond?
agile - 52
A 6-person team's velocity falls from 32 to 22 to 18 points across 3 Sprints after support duty begins. How would you use that data?
agiledelivery-metrics - 53
An 8-person team has used vague Sprint Goals such as improve checkout for 3 Sprints, and stakeholders cannot tell whether each goal was met. What would you change?
agilestakeholder-managementcommunication - 54
A 7-person team selects a 13-point account-migration story even though its largest completed item in the last 4 Sprints was 5 points. What would you do?
agilemigrations - 55
During a two-week Sprint, an 8-person team discovers 26 hours of compliance meetings and maintenance work that were absent from its plan. How would you handle the hidden work?
agile - 56
Two production incidents consume 3 Developer-days from a 6-person team during the first week of a two-week Sprint. What would you do first?
agileincidents - 57
By day 6 of a 10-day Sprint, unplanned support has used 40% of a 7-person team's capacity and 3 planned items remain untouched. How would you correct the forecast?
agilecapacity-planningcapacity - 58
A stable support workflow averaged 12 items in progress and a throughput of 3 items per week over the same 8 weeks. What average cycle time does Little's Law suggest, and what would you verify first?
throughput - 59
Before refinement, a Product Owner assigns 3, 8, or 13 points across 5 Product Backlog items and asks the Scrum Master to approve the numbers. Who should size the items, and how should the Product Owner help?
agilebacklog - 60
On day 7 of a 10-day Sprint, a 6-person team can finish either 2 optional stories or the 1 remaining item essential to its Sprint Goal. What would you facilitate?
agile - 61
Company policy allows a 7-person Scrum Team to hear user feedback only through a monthly steering committee, so Review questions wait up to 4 weeks for answers. How would you serve the organization?
agilefeedbackgovernance - 62
A Product Owner becomes unavailable for 3 days while a 6-person team has 5 questions that affect item order and acceptance criteria. What would you do?
specs - 63
A 7-person team needs an external security approval by day 7, but the reviewing group has not replied for 3 days. How would you manage the dependency?
dependenciescode-review - 64
Four stakeholders send a 7-person team 6 direct requests during the first 2 days of a Sprint. How would you handle the interruptions?
agilestakeholder-managementcommunication - 65
Only 1 of 5 invited stakeholders attends 2 consecutive Sprint Reviews for an 8-person team. What would you try next?
agilestakeholder-managementcommunication - 66
During a 60-minute Sprint Retrospective, 2 Developers spend 12 minutes blaming each other for 4 escaped defects. How would you facilitate the conflict?
agiledefects - 67
A shared test environment fails 4 times in one Sprint and costs a 6-person team 18 hours. What would you do beyond restarting it?
agiletest-environments - 68
A new 7-person team reports 3 impediments, but each remains ownerless for at least 4 days. How would you improve follow-through?
- 69
A database specialist outside a 6-person team misses 2 promised review dates, putting 1 Sprint Goal item at risk on day 5. What would you do?
agilerisk-managementdatabase - 70
On day 4 of a 10-day Sprint, a 7-person team has 3 simultaneous blockers affecting 1, 2, and 4 items. How would you decide where to help first?
agilecommunication - 71
A new Scrum Master asks all 8 team members for percent-complete updates twice a day and messages anyone whose item has not moved for 4 hours. What would you change?
agile - 72
Three Scrum Teams build one marketplace product, but each has a separate Product Goal, Product Backlog, and Product Owner for its component. What would you change?
agilecomponentsbacklog - 73
On day 3 of a 10-day Sprint, a director pressures a 6-person team to replace 2 planned items with 3 newly urgent requests. What would you do?
agile - 74
A manager sets a target of 8 story points per Developer for each of 7 people in the next Sprint. How would you challenge it?
agile - 75
A Retrospective finds that 5 accessibility defects escaped in one Sprint because keyboard and screen-reader checks are absent from the team's Definition of Done. How would you adapt it?
agiledefectsdod - 76
The Scrum Master is sick on day 4, and a manager tells 6 Developers to cancel the Daily Scrum unless the Product Owner can run it. What should the team do?
agile - 77
A Product Owner and Scrum Master each code on Sprint Backlog items 2 days per week, but they lead every Daily Scrum even on days when they do no development work. When should they participate?
agilebacklog - 78
At Sprint Review, evidence shows that the Product Goal of reducing checkout time by 30% has been fulfilled. A sales director wants to add a new expansion goal while leaving the old goal active. What should happen?
agile - 79
On day 6, a manager tells the Scrum Master to cancel a 10-day Sprint because 2 of 9 selected items will not finish. What should happen?
agile - 80
A 7-person team wants to extend a two-week Sprint by 3 days so its final 2 items can reach Done. How would you respond?
agile - 81
During a Retrospective, one Developer says a reviewer ignored 6 merge requests, while the reviewer says all 6 arrived in the final hour and threatens to stop reviewing. Their voices rise. How would you mediate?
agilecode-review - 82
Six of 7 team members want to cancel all future Retrospectives after 3 sessions produced no visible change. How would you respond?
agilesessions - 83
An anonymous pulse from a 6-person team scores psychological safety at 2 out of 5, and no one raised any risk in the last 3 Sprints. What would you do?
agilerisk-management - 84
An 8-person Scrum Team spans UTC-8 and UTC+5. Daily Scrums are sometimes skipped, and Planning, Review, and Retrospective always run late for the same 4 people. How would you schedule the events?
agile - 85
A 7-person team records 11 interruptions and 4 missed handoffs in one Sprint because nobody agrees on response times or focus hours. How would you build a working agreement?
agile - 86
A 6-person team asks the Scrum Master to assign every new item because 3 Developers fear choosing the wrong work. How would you support self-management?
agile - 87
Before Sprint Planning, a 7-person Scrum Team lacks encryption knowledge for 3 candidate items. The Product Owner wants an external security architect to choose the Sprint work and assign tasks. What would you do?
agileencryption - 88
Five of 7 Developers resist pairing on a 9-day-old blocked item because they believe individual ownership is faster. How would you coach them?
ownership - 89
After a Product Owner criticizes one Developer by name in front of 8 people, the team reports 0 new risks for the next 6 working days. What would you do?
- 90
A 7-person team has run its Daily Scrum and resolved coordination issues without prompting for 15 working days. How should a new Scrum Master step back?
agile - 91
A 6-person Scrumban team replenishes its Ready queue only after it becomes empty, then Developers pick whichever request arrived last. Two high-value items have waited 12 days. What explicit policy would you introduce?
agiledata-structures - 92
A 7-person Scrumban team receives 4 urgent requests in 5 days, and every requester demands immediate service. How would you design an urgent-work lane?
agiledesign - 93
A 6-person team's board shows blocked items aged 1, 3, and 6 days, but its daily discussion only covers new work. What would you change?
- 94
A 7-person team's median cycle time rises from 3 to 8 days over 4 weeks while throughput falls from 6 to 3 items per week. How would you investigate?
throughput - 95
Unplanned support consumes about 30% of a 6-person Scrum Team's time across 4 Sprints. How could basic Scrumban practices improve its forecast?
agile - 96
A new Scrum Master tries a silent digital Retrospective with an 8-person team, but only 2 people contribute and no action is selected after 45 minutes. How would you recover?
agile - 97
A new Scrum Master moves 3 items out of a 7-person team's Sprint Backlog without consulting the Developers, causing 2 hours of rework. How should they repair the mistake?
agileownershipbacklog - 98
Over 10 working days, a 6-person team's cumulative flow diagram shows its in-progress band growing from 4 to 11 items while Done barely changes. What would you do?
- 99
A 7-person team expects 85% of standard items to finish within 5 days, but 2 active items are already 9 days old. How would you use work item age?
- 100
A 6-person Scrumban team completed 24 comparable items in total over 6 weeks, but the report does not show each week's count. A stakeholder asks for a probability range for next week and a promise of 8 items. How would you respond?
agilestakeholder-managementpromises