Scrum Master Responsibilities | GitScrum Tooling Support
Scrum Master responsibilities include facilitation, coaching, and impediment removal. GitScrum provides blocker tracking and sprint health dashboards.
10 min read
A Scrum Master is a facilitator, coach, and impediment remover. GitScrum provides the visibility and tools Scrum Masters need to support their teams effectively.
Core Responsibilities
The Scrum Master Role
SCRUM MASTER RESPONSIBILITIES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ FACILITATOR: │
│ • Run sprint ceremonies effectively │
│ • Keep meetings focused and time-boxed │
│ • Ensure everyone's voice is heard │
│ • Drive decisions without making them │
│ │
│ COACH: │
│ • Teach agile principles and practices │
│ • Help team improve continuously │
│ • Guide self-organization │
│ • Model the values │
│ │
│ IMPEDIMENT REMOVER: │
│ • Identify blockers quickly │
│ • Escalate when needed │
│ • Clear the path for the team │
│ • Follow up until resolved │
│ │
│ SHIELD: │
│ • Protect team from distractions │
│ • Manage stakeholder expectations │
│ • Maintain sustainable pace │
│ • Guard sprint commitments │
│ │
│ SERVANT LEADER: │
│ • Put team needs first │
│ • Enable rather than direct │
│ • Lead by example │
│ • Grow team capability │
└─────────────────────────────────────────────────────────────┘
What a Scrum Master Is NOT
SCRUM MASTER ANTI-PATTERNS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ ❌ NOT A PROJECT MANAGER: │
│ • Doesn't assign tasks to people │
│ • Doesn't manage schedule and resources │
│ • Doesn't report status to management │
│ │
│ ❌ NOT A TEAM LEAD: │
│ • Doesn't make technical decisions │
│ • Doesn't have authority over team members │
│ • Doesn't evaluate performance │
│ │
│ ❌ NOT A SECRETARY: │
│ • Doesn't just schedule meetings │
│ • Doesn't just take notes │
│ • Doesn't just update tools │
│ │
│ ❌ NOT A POLICE OFFICER: │
│ • Doesn't enforce rules rigidly │
│ • Doesn't punish "violations" │
│ • Doesn't report team to management │
│ │
│ IF YOU'RE DOING THESE, YOU'RE NOT A SCRUM MASTER: │
│ • "I'll assign that task to Alex" │
│ • "The team needs to work harder" │
│ • "Let me tell management why we're late" │
│ • "You can't do it that way, it's not Scrum" │
│ │
│ INSTEAD: │
│ • "How would the team like to approach this?" │
│ • "What's preventing sustainable delivery?" │
│ • "What can I do to help?" │
│ • "What would work better for our context?" │
└─────────────────────────────────────────────────────────────┘
Ceremony Facilitation
Sprint Planning
FACILITATING SPRINT PLANNING:
┌─────────────────────────────────────────────────────────────┐
│ │
│ BEFORE PLANNING: │
│ ☐ Backlog is refined and prioritized (with PO) │
│ ☐ Team capacity known (PTO, holidays, etc.) │
│ ☐ Previous sprint metrics reviewed │
│ ☐ Room/tools ready │
│ │
│ DURING PLANNING: │
│ │
│ Part 1: What (30 min) │
│ • PO presents sprint goal │
│ • Team asks clarifying questions │
│ • SM facilitates discussion │
│ │
│ Part 2: How (1-2 hours) │
│ • Team selects items from backlog │
│ • Team breaks down into tasks │
│ • SM ensures everyone participates │
│ • SM watches for over-commitment │
│ │
│ SM FACILITATION TIPS: │
│ │
│ • "Does everyone understand this story?" │
│ • "Is this estimate reasonable given our history?" │
│ • "Are we over capacity? What can we defer?" │
│ • "What dependencies should we flag?" │
│ • "Does everyone commit to this sprint goal?" │
│ │
│ OUTPUT: │
│ ✓ Sprint goal │
│ ✓ Sprint backlog │
│ ✓ Team commitment │
└─────────────────────────────────────────────────────────────┘
Daily Standup
FACILITATING STANDUPS:
┌─────────────────────────────────────────────────────────────┐
│ │
│ SM ROLE IN STANDUP: │
│ • Start on time (even if people missing) │
│ • Keep it to 15 minutes │
│ • Ensure focus on sprint goals │
│ • Note blockers for follow-up │
│ • Park detailed discussions │
│ │
│ FACILITATION MOVES: │
│ │
│ If going long: │
│ "Let's take this offline after standup" │
│ │
│ If status report mode: │
│ "What's blocking you from sprint goal progress?" │
│ │
│ If same update multiple days: │
│ "That sounds blocked - what help do you need?" │
│ │
│ If someone quiet: │
│ "Jordan, anything the team should know?" │
│ │
│ If blocker identified: │
│ "I'll work on that right after standup. Who else needed?" │
│ │
│ AFTER STANDUP: │
│ • Address blockers immediately │
│ • Facilitate parking lot discussions │
│ • Update blocker tracking │
│ • Follow up on action items │
└─────────────────────────────────────────────────────────────┘
Retrospective
FACILITATING RETROSPECTIVES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ BEFORE RETRO: │
│ ☐ Choose format (rotate to keep fresh) │
│ ☐ Prepare materials/board │
│ ☐ Review action items from last retro │
│ ☐ Set aside 60-90 minutes │
│ │
│ FORMAT OPTIONS: │
│ │
│ CLASSIC: │
│ What went well? What didn't? What to try? │
│ │
│ STARFISH: │
│ Keep doing | Do more | Start | Stop | Do less │
│ │
│ 4Ls: │
│ Liked | Learned | Lacked | Longed for │
│ │
│ SAILBOAT: │
│ Wind (helps) | Anchor (slows) | Rocks (risks) │
│ │
│ FACILITATION TIPS: │
│ │
│ • Create psychological safety │
│ • Silent brainstorming first │
│ • Everyone speaks │
│ • Focus on actions, not venting │
│ • Limit to 2-3 action items │
│ • Assign owners and due dates │
│ │
│ FOLLOW THROUGH: │
│ • Track retro actions in GitScrum │
│ • Review at next retro │
│ • Celebrate improvements │
└─────────────────────────────────────────────────────────────┘
Impediment Removal
Tracking Blockers
BLOCKER MANAGEMENT:
┌─────────────────────────────────────────────────────────────┐
│ │
│ GITSCRUM BLOCKER VIEW: │
│ ┌─────────────────────────────────────────────────────────┐│
│ │ Current Blockers ││
│ │ ││
│ │ 🔴 Waiting on external API credentials (Day 3) ││
│ │ Story: Payment integration ││
│ │ Blocked: Alex, Jordan ││
│ │ Action: SM escalated to DevOps lead ││
│ │ → Expected resolution: Tomorrow ││
│ │ ││
│ │ 🟡 Design review needed (Day 1) ││
│ │ Story: Checkout redesign ││
│ │ Blocked: Maria ││
│ │ Action: Meeting scheduled 2pm today ││
│ │ ││
│ │ 🟢 Resolved: Environment access (was Day 2) ││
│ │ Resolved by: SM requested emergency access ││
│ └─────────────────────────────────────────────────────────┘│
│ │
│ SM BLOCKER PROTOCOL: │
│ │
│ Day 0: Identified in standup → Immediate follow-up │
│ Day 1: Still blocked → Escalate one level │
│ Day 2: Still blocked → Senior escalation │
│ Day 3: Still blocked → Find workaround or de-scope │
│ │
│ RESOLUTION: │
│ • Document what resolved it │
│ • Pattern? Add to retro │
│ • Could prevent recurrence? Create action item │
└─────────────────────────────────────────────────────────────┘
Common Impediments
TYPICAL SM IMPEDIMENTS TO CLEAR:
┌─────────────────────────────────────────────────────────────┐
│ │
│ TECHNICAL: │
│ • Environment access │
│ • Tool licenses │
│ • External system dependencies │
│ → Action: Expedite through proper channels │
│ │
│ ORGANIZATIONAL: │
│ • Waiting on other teams │
│ • Approval bottlenecks │
│ • Resource conflicts │
│ → Action: Facilitate cross-team communication │
│ │
│ PROCESS: │
│ • Unclear requirements │
│ • Missing decisions │
│ • Conflicting priorities │
│ → Action: Bring PO and stakeholders together │
│ │
│ PEOPLE: │
│ • Team conflicts │
│ • Unclear roles │
│ • Skill gaps │
│ → Action: Coach, facilitate, escalate to management │
│ │
│ DISTRACTIONS: │
│ • Too many meetings │
│ • Stakeholder interruptions │
│ • Context switching │
│ → Action: Shield team, negotiate protected time │
│ │
│ SM DOESN'T FIX EVERYTHING: │
│ • Technical problems → Team solves │
│ • Product decisions → PO decides │
│ • Management issues → Manager handles │
│ SM clears the path, doesn't do the work │
└─────────────────────────────────────────────────────────────┘
Coaching the Team
Coaching Areas
SM COACHING RESPONSIBILITIES:
┌─────────────────────────────────────────────────────────────┐
│ │
│ SELF-ORGANIZATION: │
│ "How does the team want to handle this?" │
│ • Resist solving problems for them │
│ • Ask questions instead of giving answers │
│ • Let team experience consequences and learn │
│ │
│ AGILE PRACTICES: │
│ "Would smaller stories help with flow?" │
│ • Teach why behind the practices │
│ • Adapt practices to context │
│ • Don't enforce rigidly │
│ │
│ COLLABORATION: │
│ "Have you talked to Jordan about this?" │
│ • Encourage direct communication │
│ • Model healthy conflict │
│ • Build psychological safety │
│ │
│ CONTINUOUS IMPROVEMENT: │
│ "What could we do differently next time?" │
│ • Make improvement a habit │
│ • Follow through on retro actions │
│ • Celebrate progress │
│ │
│ OWNERSHIP: │
│ "What do you think we should do?" │
│ • Push decisions to the team │
│ • Build capability, not dependence │
│ • Trust the team │
│ │
│ GOAL: Work yourself out of a job │
│ Team should need less SM intervention over time │
└─────────────────────────────────────────────────────────────┘
Health Indicators
Team Health Metrics
SM HEALTH MONITORING:
┌─────────────────────────────────────────────────────────────┐
│ │
│ GITSCRUM HEALTH DASHBOARD: │
│ │
│ VELOCITY: │
│ Sprint 22: ████████████ 42 pts │
│ Sprint 23: ████████████ 44 pts │
│ Sprint 24: ██████████░░ 38 pts ⚠️ │
│ │
│ → Declining velocity - investigate in retro │
│ │
│ FLOW: │
│ Average cycle time: 3.2 days ✅ │
│ Items blocked: 2 items ⚠️ │
│ Carryover: 1 story (was 0) │
│ │
│ → Blockers increasing - prioritize removal │
│ │
│ SPRINT GOALS: │
│ Last 5 sprints: ✅ ✅ ✅ ⚠️ ❌ │
│ │
│ → Missed last sprint - over-committed? │
│ │
│ RETRO ACTIONS: │
│ Last sprint: 3 actions, 2 completed ✅ │
│ Open actions: 4 total │
│ │
│ → Good follow-through, keep it up │
│ │
│ USE THESE TO: │
│ • Identify coaching opportunities │
│ • Spot systemic issues │
│ • Track improvement │
│ • NOT to judge or punish team │
└─────────────────────────────────────────────────────────────┘