In LeSS, the Scrum Master is a dedicated full-time role serving 1–3 teams. Their focus extends beyond individual teams to the overall organizational system — coaching teams, the PO, management, and the organization toward a well-working LeSS adoption.
System Focus
Coaches the whole organization, not just one team
Multi-Team
Serves 1–3 teams with balanced attention
Change Agent
Drives organizational simplification and descaling
Technical Coach
Supports engineering excellence as structural enabler
Dedicated Role
Full-time, not combined with other responsibilities
Whole-System Focus
In LeSS, a Scrum Master doesn’t focus on just one team — they focus on the overall organizational system. Their coaching scope extends to teams, the Product Owner, the organization, and development practices.
Key Activities
Focus on the overall product development system, not just individual team effectiveness
Coach the organization on LeSS adoption — structural changes, feature teams, and removing waste
Work with management to shift their role from controlling work to improving the system
Identify systemic impediments that cross team boundaries and drive organizational resolution
Help the organization understand why fewer roles, fewer processes, and fewer artifacts create more value
Click to expand
Multi-Team Coaching
One Scrum Master serves 1–3 teams in LeSS. They coach teams toward true self-management and cross-functional capability, ensuring each team can deliver end-to-end customer features independently.
Key Activities
Coach 1–3 teams simultaneously — balancing attention across teams based on maturity and need
Help teams become true feature teams: cross-functional, cross-component, and able to deliver end-to-end value
Foster self-management — teams decide who works on what, how to plan, and how to improve
Coach teams to coordinate directly with each other rather than through intermediaries
Develop facilitation and conflict-resolution skills within each team over time
Click to expand
LeSS Event Facilitation
The SM facilitates LeSS-specific events — Sprint Planning Part 1 (multi-team), the shared Sprint Review, and the Overall Retrospective — ensuring cross-team alignment and whole-product thinking.
Key Activities
Facilitate Sprint Planning Part 1 with all teams and the PO — ensuring effective self-selection of work
Support teams during Sprint Planning Part 2 — available for coaching but letting teams drive their own planning
Facilitate the shared Sprint Review with real customers and stakeholders
Run the Overall Retrospective with team representatives, PO, and managers to address systemic issues
Coach teams to facilitate their own team-level Daily Scrums and Retrospectives independently
Click to expand
Systemic Impediment Removal
The LeSS SM distinguishes between team-level impediments (which teams should resolve) and systemic impediments (which require organizational change). Their focus is on the systemic ones.
Key Activities
Identify patterns across teams that signal systemic issues rather than one-off team problems
Escalate organizational impediments to management with data, impact analysis, and proposed experiments
Work with management on structural changes: removing component teams, eliminating handoff roles, simplifying processes
Track systemic impediment resolution — stale organizational impediments signal leadership disengagement
Use the Overall Retrospective to surface and commit to addressing cross-team systemic issues
Click to expand
Technical Practice Coaching
LeSS places heavy emphasis on technical excellence. The SM coaches teams in adopting practices like continuous integration, TDD, shared code ownership, and clean code — these are structural enablers, not optional extras.
Key Activities
Coach teams toward continuous integration — all teams integrating into one shared codebase continuously
Encourage adoption of test-driven development at unit and acceptance test levels
Promote shared code ownership — any team can modify any part of the codebase
Support teams in establishing and evolving a rigorous Definition of Done
Connect teams with technical communities of practice for cross-team learning on engineering practices
Click to expand
Organizational Change Agent
The LeSS SM is an active change agent — working to descale the organization by removing unnecessary roles, processes, and structures that prevent teams from delivering value directly to customers.
Key Activities
Advocate for feature teams over component teams — the single most important organizational change in LeSS
Help the organization adopt Go See, Stop & Fix, and experiments-over-conformance management practices
Challenge the existence of intermediary roles that create distance between teams and customers
Support management in shifting from controlling work to improving the product development system
Practice and teach systems thinking — helping the organization see how local optimizations create global problems
Click to expand
The LeSS Scrum Master is fundamentally different from a single-team SM. Their scope includes the organizational system itself — they are as much organizational change agents as they are team coaches. The role is deliberately full-time because systemic improvement requires sustained, dedicated attention.