LeSS (Large-Scale Scrum): Scale Scrum without complexity

When a single Scrum team operates successfully, the organization might be tempted to 'copy and paste' and suddenly have multiple teams working. But how do you keep it simple and safeguard the principles of self-organization and rapid feedback? LeSS (Large-Scale Scrum) is a framework designed to support large-scale Agile initiatives without losing the essence of Scrum. At Spark Academy, we find that LeSS offers a fresh, simplifying perspective on scaling.

‍

What is LeSS?

LeSS (Large-Scale Scrum) is an approach for multiple Scrum teams to work together on a single product, while retaining the core elements of Scrum. The framework enables you to coordinate and synchronize at a higher level, without falling into extensive roles, rules, and ceremonies. Instead, LeSS aims to stay as close as possible to 'regular' Scrum:

• One Product Owner: LeSS believes in one clear person responsible for the product, even if there are multiple teams.
• One Product Backlog: All items for all teams go into a single Backlog, ensuring maximum transparency.
• Close collaboration between teams: Feedback loops and synchronization between teams are central, for example, in shared Reviews or Retrospectives.

‍

Core Principles of LeSS

1. Less is More: Instead of various extra layers and roles, the foundation is: stay close to Scrum and minimize complexity.
2. Transparency: With one Product Backlog and shared definitions of 'Done' and Ready, you prevent teams from having their own guidelines.
3. Customer Focus: LeSS emphasizes that every team should have direct contact with customers and users to keep the feedback loop short.
4. Continuous Improvement: Similar to Scrum, progress is made in small steps, but across multiple teams.

‍

Differences from other Scaling Frameworks

LeSS differs from, for example, SAFe (Scaled Agile Framework) by deliberately adding fewer roles, ceremonies, and artifacts. While SAFe provides an extensive description of how to implement Agile enterprise-wide, LeSS keeps it modest and believes more in principles and continuous learning. This 'less is more' approach makes LeSS attractive to organizations that want to remain flexible and avoid excessive overhead.

‍

Role of the Scrum Master in LeSS

In LeSS, the Scrum Master is not only focused on their (own) teams but can coach multiple teams. This can involve:

• Facilitating cross-team alignment: For example, by assisting with shared Retrospectives or monitoring dependencies between teams.
• Coaching the bigger picture: The Scrum Master can guide management and stakeholders through the Agile transition, helping them better understand how to support teams.
• Upholding the principles: By pointing out redundant processes or roles, the Scrum Master helps keep the organization 'lean'.

‍

Pitfalls of LeSS

• Lack of discipline: Without clear additional roles, it can happen that no one takes the initiative to promote integration or collaboration.
• Insufficient alignment: If teams rarely meet, they can still work in silos. Regular alignment and transparency are a must.
• Scaling by habit: If the organization is accustomed to hierarchy, it can be challenging to truly stick to the basic principles of Scrum.

‍

LeSS (Large-Scale Scrum) offers a way to scale Scrum while maintaining simplicity and agility. By using a single Product Owner, one Backlog, and as many shared events and definitions as possible, LeSS keeps communication lines short and collaboration open. For organizations that want to scale but don't want to get bogged down in complex structures, LeSS is a breath of fresh air: it keeps you close to the core of what makes Scrum so powerful.

‍