Large-Scale Scrum (LeSS)
An agile method for scaling Scrum in large projects or organizations.
Classification
- ComplexityMedium
- Impact areaOrganizational
- Decision typeOrganizational
- Organizational maturityAdvanced
Technical context
Principles & goals
Use cases & scenarios
Compromises
- Misunderstandings in Team Collaboration
- Overload of Team Members
- Insufficient Experience with the Method
- Regular retrospectives
- Define clear roles
- Encourage continuous improvement
I/O & resources
- List of all stakeholders
- Kick-off meeting materials
- Scrum training materials
- Completed Sprints
- Traceable change logs
- Completed team retrospectives
Description
Large-Scale Scrum (LeSS) is a structured approach to implement Scrum across multiple teams within large organizations. It promotes collaboration and maximizes value through agile practices on both social and technical levels.
✔Benefits
- Increased Flexibility
- Better Quality
- Efficient Resource Utilization
✖Limitations
- Complexity in Implementation
- Higher Requirements on Team Coordination
- Possible Resistance within the Organization
Trade-offs
Metrics
- Team Performance
Measurement of team productivity and efficiency.
- Quality of Final Product
Assessment of product quality and customer satisfaction.
- Time to Market
Time taken to bring a new product to market.
Examples & implementations
Example of Successful LeSS Implementation
A company implemented LeSS and synchronized the product development teams to maximize value.
Improvement of Team Collaboration
A case study example where LeSS improved collaboration among multiple teams.
Successful Product Release with LeSS
An example where the introduction of LeSS led to significant improvements in quality and satisfaction.
Implementation steps
Training the teams in LeSS
Conducting kick-off meetings
Setting up Scrum-of-scrum meetings
⚠️ Technical debt & bottlenecks
Technical debt
- High level of technical dependencies
- Outdated software tools
- Lack of integration between systems
Known bottlenecks
Misuse examples
- Disregarding Agile Principles
- Neglecting Feedback
- Insufficient Coordination
Typical traps
- Unclear Responsibilities
- Excessive Bureaucracy
- Insufficient Stakeholder Engagement
Required skills
Architectural drivers
Constraints
- • Need for Regular Meetings
- • Need for Qualified Facilitators
- • Adjustment of Existing Hierarchies