Agent skill
scrum-master
Facilitate Scrum framework implementation, coach Agile teams, remove impediments, and drive continuous improvement. Use for: leading Scrum ceremonies, coaching teams on Agile practices, removing blockers, facilitating sprint planning and retrospectives, supporting Product Owners, promoting self-organization, and ensuring Scrum adherence.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/scrum-master-jh9282026-manus
SKILL.md
Scrum Master
Serve as servant-leader and facilitator for Agile Scrum teams, ensuring effective implementation of Scrum framework and continuous improvement.
Overview
The Scrum Master is a crucial role in Agile project management, acting as a servant leader, facilitator, and coach for the Scrum team, Product Owner, and organization. This skill covers facilitating Scrum ceremonies, removing impediments, coaching on Agile values, supporting the Product Owner, and promoting team self-organization and continuous improvement.
Core Responsibilities
1. Facilitate Scrum Ceremonies
Daily Standup (15 minutes):
- Ensure meeting happens at same time/place daily
- Keep timeboxed to 15 minutes
- Help team focus on Sprint Goal progress
- Note impediments for follow-up
- Prevent problem-solving during standup
Sprint Planning (8 hours for 1-month sprint):
- Prepare agenda and materials
- Facilitate team discussion
- Ensure Sprint Goal is clear
- Help team commit to realistic work
- Document Sprint Backlog
Sprint Review (4 hours for 1-month sprint):
- Coordinate with Product Owner on agenda
- Invite stakeholders
- Facilitate demonstration
- Capture feedback
- Update Product Backlog based on feedback
Sprint Retrospective (3 hours for 1-month sprint):
- Create safe environment for honest feedback
- Facilitate using various formats
- Ensure actionable improvements identified
- Follow up on previous actions
- Document and track improvements
2. Remove Impediments
Impediment Types:
- Team-level: Technical blockers, skill gaps, conflicts
- Organizational: Process barriers, resource constraints, policy issues
- External: Vendor delays, dependency on other teams, stakeholder availability
Impediment Resolution Process:
- Identify: Make visible (impediment board, standup)
- Categorize: Team can solve vs. requires escalation
- Act: Remove directly or escalate appropriately
- Track: Monitor until resolved
- Prevent: Address root causes
Escalation Path:
- Team-level → Scrum Master resolves
- Cross-team → Scrum of Scrums or RTE
- Organizational → Management or leadership
- External → Stakeholder engagement
3. Coach the Team
Self-Organization:
- Encourage team to make decisions
- Avoid dictating solutions
- Ask powerful questions
- Support experimentation
- Celebrate team ownership
Cross-Functionality:
- Identify skill gaps
- Facilitate knowledge sharing
- Encourage pairing and mentoring
- Support training and development
- Reduce specialization silos
Agile Values and Principles:
- Model Scrum values (commitment, focus, openness, respect, courage)
- Teach Agile principles
- Connect practices to values
- Address anti-patterns
- Reinforce desired behaviors
4. Support the Product Owner
Backlog Management:
- Techniques for effective backlog refinement
- Story writing and acceptance criteria
- Prioritization methods (WSJF, MoSCoW)
- Backlog health metrics
- Refinement meeting facilitation
Stakeholder Management:
- Facilitate stakeholder communication
- Help manage expectations
- Support Sprint Review preparation
- Gather and incorporate feedback
- Balance competing demands
Product Vision:
- Ensure team understands vision
- Connect work to business goals
- Facilitate vision workshops
- Make vision visible
- Align Sprint Goals with vision
5. Shield the Team
Protect Focus:
- Prevent mid-sprint scope changes
- Manage interruptions
- Decline non-sprint work
- Enforce Sprint commitment
- Create focused work environment
Manage External Pressure:
- Buffer unrealistic demands
- Educate stakeholders on Scrum
- Negotiate sustainable pace
- Communicate team capacity
- Push back on overtime expectations
Scrum Master Skills
Facilitation Skills
Meeting Facilitation:
- Prepare agenda and materials
- Keep discussions on track
- Ensure all voices heard
- Manage time effectively
- Drive to decisions and actions
Conflict Resolution:
- Identify conflicts early
- Create safe space for discussion
- Facilitate win-win solutions
- Address root causes
- Follow up on resolution
Decision-Making Facilitation:
- Fist of five voting
- Dot voting for prioritization
- Consensus building
- Delegation poker
- Decision matrices
Coaching Skills
Powerful Questions:
- "What's preventing you from...?"
- "What have you tried?"
- "What would success look like?"
- "What's the smallest step you could take?"
- "What support do you need?"
Active Listening:
- Full attention
- Reflect back what you hear
- Ask clarifying questions
- Observe body language
- Suspend judgment
Feedback Delivery:
- Timely and specific
- Focus on behavior, not person
- Balance positive and constructive
- Actionable suggestions
- Follow up on progress
Leadership Skills
Servant Leadership:
- Serve the team's needs
- Remove obstacles
- Enable team success
- Lead by example
- Empower, don't control
Influence Without Authority:
- Build relationships
- Demonstrate value
- Use data and evidence
- Appeal to shared goals
- Persistent and patient
Change Management:
- Understand resistance
- Communicate benefits
- Start small, build momentum
- Celebrate wins
- Adapt approach based on feedback
Metrics and Measurement
Team Performance Metrics
Velocity:
- Track trend over time
- Use for planning
- Identify anomalies
- Discuss in retrospectives
Sprint Goal Achievement:
- Percentage of sprints where goal met
- More important than velocity
- Indicates planning effectiveness
Cycle Time:
- Time from start to done
- Identify bottlenecks
- Optimize flow
- Set improvement goals
Defect Rate:
- Bugs per sprint
- Escaped defects to production
- Track trend
- Address quality issues
Team Health Metrics
Team Happiness:
- Regular pulse surveys
- Simple 1-5 scale
- Track trend
- Discuss in retrospectives
Retrospective Action Completion:
- Percentage of actions completed
- Indicates commitment to improvement
- Follow up each retrospective
Team Stability:
- Percentage of team unchanged
- Goal: >80% stability
- Changes impact velocity
Common Challenges
| Challenge | Solution |
|---|---|
| Team not self-organizing | Ask questions, don't provide answers; step back gradually |
| Product Owner unavailable | Educate on importance; escalate to leadership |
| Pressure for unrealistic commitments | Use data (velocity); educate on sustainable pace |
| Skipping ceremonies | Demonstrate value; make engaging; timebox strictly |
| Resistance to change | Start small; show quick wins; address concerns |
| Distributed team | Over-communicate; use video; overlap hours; digital tools |
| Technical debt accumulation | Make visible; allocate capacity; track trend |
Scrum Master Anti-Patterns
What NOT to Do:
- Acting as Project Manager: Don't assign tasks, manage timeline, control team
- Making Decisions for Team: Don't solve problems, let team find solutions
- Being Administrative Assistant: Don't just schedule meetings and take notes
- Protecting Team from All Interaction: Don't isolate team from stakeholders
- Not Addressing Dysfunction: Don't ignore conflicts, poor practices, or violations
- Micromanaging: Don't hover, check status constantly, or control work
- Taking Credit: Don't claim team's success; celebrate team achievements
Tools and Techniques
Retrospective Formats
Start-Stop-Continue:
- What should we start doing?
- What should we stop doing?
- What should we continue doing?
4 Ls:
- Liked
- Learned
- Lacked
- Longed for
Sailboat:
- Wind (helping us)
- Anchor (slowing us)
- Rocks (risks ahead)
- Island (our goal)
Mad-Sad-Glad:
- What made you mad?
- What made you sad?
- What made you glad?
Facilitation Techniques
Timeboxing:
- Set clear time limits
- Use timer visible to all
- Warn when time running out
- Strictly enforce limits
Parking Lot:
- Capture off-topic items
- Revisit at end if time
- Schedule follow-up if needed
- Keeps meeting focused
Silent Brainstorming:
- Write ideas on sticky notes
- No discussion during writing
- Affinity grouping
- Discuss grouped ideas
Dot Voting:
- Each person gets 3-5 dots
- Vote on most important items
- Prioritize based on votes
- Democratic and quick
Career Development
Scrum Master Levels
Entry Level (0-2 years):
- Facilitate ceremonies
- Track basic metrics
- Remove simple impediments
- Learn Scrum framework
Intermediate (2-5 years):
- Coach team effectively
- Handle complex impediments
- Improve team performance
- Mentor new Scrum Masters
Senior (5+ years):
- Coach multiple teams
- Drive organizational change
- Resolve systemic issues
- Thought leadership
Agile Coach (8+ years):
- Coach leaders and executives
- Design transformation strategy
- Establish Agile practices
- Organizational impact
Certifications
Certified ScrumMaster (CSM) - Scrum Alliance:
- Entry-level certification
- 2-day training required
- Widely recognized
- Good foundation
Professional Scrum Master (PSM) - Scrum.org:
- No training required
- Rigorous exam
- Three levels (PSM I, II, III)
- Demonstrates deep knowledge
SAFe Scrum Master (SSM) - Scaled Agile:
- For scaled environments
- 2-day training
- SAFe-specific practices
- Enterprise focus
Advanced Certified ScrumMaster (A-CSM) - Scrum Alliance:
- Requires CSM and experience
- Advanced facilitation and coaching
- Next step after CSM
Using the Reference Files
When to Read Each Reference
/references/facilitation-techniques.md — Read when preparing for ceremonies, handling difficult meetings, or improving facilitation skills.
/references/coaching-guide.md — Read when coaching team members, addressing performance issues, or developing coaching capabilities.
/references/impediment-resolution.md — Read when facing complex blockers, escalating issues, or establishing impediment management processes.
/references/team-dynamics.md — Read when addressing conflicts, improving collaboration, or understanding team development stages.
/references/metrics-tracking.md — Read when establishing metrics, creating dashboards, or analyzing team performance data.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?